For Admins
Integrations: LinkedIn and Slack - Ambo Docs
Connect Ambo to LinkedIn and Slack to enable content sharing and advocate notifications.
Ambo integrates with LinkedIn for content sharing and Slack for notifications. LinkedIn is required for the core sharing workflow. Slack is optional but recommended for keeping advocates engaged.
How LinkedIn connections work
Each advocate connects their personal LinkedIn account to Ambo via OAuth. Ambo stores the access token and uses it to post on their behalf when they share content. Ambo securely encrypts and stores the access token so it remains protected, even in the unlikely event of a database breach, while enabling advocates to share posts seamlessly.
Ambo can also share as your organization’s LinkedIn company page. This is done through a dedicated admin user who is assigned the LinkedIn admin role assigned from the User dashboard.
OAuth tokens are refreshed automatically in the background. Advocates don’t need to reconnect on a regular basis.
Admin setup
Set your LinkedIn Organization ID Paste your LinkedIn Org ID in Admin -> Settings → LinkedIn Organization ID. This enables company page sharing and org-level LinkedIn analytics. See Organization Settings for how to find your Org ID.
Assign LinkedIn admin access Open a user’s profile and toggle LinkedIn Admin on. This flag grants the user the ability to perform LinkedIn org-level actions within Ambo. It is separate from the Admin role. Not all admins need to have LinkedIn Admin role assigned.
Token expiry and reconnection
If an advocate changes their LinkedIn password, revokes Ambo’s access in LinkedIn settings, or their token expires without a successful refresh, their next share attempt will fail.
To fix this, the advocate goes to Settings → LinkedIn and reconnects their account. Once reconnected, any pending shares can be retried.
Slack
Connecting Slack
Go to Settings → Organization and click Connect Slack. You’ll go through an OAuth flow to authorize the Ambo bot in your workspace. During setup, you’ll select which Slack channel Ambo should use for broadcast notifications.
What Ambo sends to Slack
| Notification | Who receives it |
|---|---|
| New post published | Posted to the designated org channel |
| Share confirmed | Sent as a DM to the advocate who shared |
| Approval request | Sent as a DM to the advocate who needs to approve |
| Weekly sharing reminder | Sent as a DM to advocates who haven’t shared recently |
Advocates receive DMs based on their email IDs, so they must use the same email address in both Slack and Ambo for this to work.
Disconnecting Slack
Go to Settings → Organization and click Disconnect Slack. This removes the bot from your workspace and stops all Slack notifications. Individual advocates keep their Slack user IDs in their settings, but no messages will be sent.
Troubleshooting
| Issue | Cause | Resolution |
|---|---|---|
| Share FAILED | Advocate’s LinkedIn token expired or was revoked | Advocate reconnects LinkedIn in their Settings |
| Company page share fails with permission error | LinkedIn Org ID is wrong, or the CompanyPage user doesn’t have admin access on the LinkedIn page | Verify the Org ID and check the LinkedIn page admin roles |
| Slack notifications stopped | Workspace admin revoked the Ambo bot’s access | Reconnect Slack in Settings → Organization |