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 post as your organization’s LinkedIn company pages and showcase pages. Each page posts through the LinkedIn account of the Ambo admin who added it.
OAuth tokens are refreshed automatically in the background. Advocates don’t need to reconnect on a regular basis.
Admin setup
Connect your LinkedIn account as an admin Switch to the Advocate Dashboard, go to Settings, and click Connect LinkedIn. When an Ambo admin connects, Ambo also asks for permission to manage the LinkedIn pages you administer. If you connected before becoming an admin, disconnect and connect again.
Add your company pages Go to Settings → LinkedIn Company Pages, click Add company page, and pick the pages you administer on LinkedIn. You can add several company and showcase pages. Only admins who manage a page on LinkedIn can add it. See LinkedIn Company and Showcase Pages.
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 | The admin who added the page lost admin access on LinkedIn, or disconnected their LinkedIn account | Have an admin who manages the page on LinkedIn add it again in Settings → LinkedIn Company Pages |
| A page is missing when adding company pages | You aren’t an admin of the page on LinkedIn, or connected before becoming an Ambo admin | Check your page role on LinkedIn, then reconnect LinkedIn |
| Slack notifications stopped | Workspace admin revoked the Ambo bot’s access | Reconnect Slack in Settings → Organization |