Connect a LinkedIn company Page to Sift to pull comments and mentions on Page posts into the inbox, so your social team handles them alongside everything else.
At a glance
| Inbound: Comments on company-Page posts | ✅ |
| Inbound: Replies to comments (full thread) | ✅ |
| Inbound: Mentions of the Page | ✅ |
| Inbound: Page messages / inbox | ❌ LinkedIn doesn't expose Page messaging to third parties |
| Outbound: Reply to a comment | ✅ |
| Outbound: Publish or schedule a Page post | ❌ |
| Multi-page per workspace | ✅ |
| Auto-reply bots | ✅ |
| LinkedIn Groups | ❌ |
Set it up
Go to Settings → Integrations → LinkedIn and sign in as a Page admin of the company Page you want to connect. Authorize the Sift app - that's the whole flow.
If your company has multiple Pages (e.g. brand + regional + acquired-company), each can be connected separately and routed to its own queue.
What you can do
Reply to any inbound comment from the inbox - Sift posts back to LinkedIn as the connected Page.
Trigger workflows off comment signal (sentiment, keyword, author). Route to the right team automatically. Apply auto-reply bots for FAQ patterns.
LinkedIn's API surface for third-party tools is narrow by design: Pages only, comments + mentions only, reply-only outbound. Sift uses what's available; what isn't, isn't.
What Sift ingests
Once a Page is connected, Sift ingests every comment + reply on every post the Page has published, plus mentions of the Page from anywhere on LinkedIn. Each comment carries the author profile, the post it's on, and the timestamp - usable for filtering, routing, and bot triggers.
Not supported today
- Page messages / inbox: LinkedIn doesn't expose Page messaging to third-party apps. Handle DMs in LinkedIn directly.
- Personal profile activity: LinkedIn's API is Pages-only for moderation tools.
- LinkedIn Groups: not part of the Pages API.
- Publishing or scheduling Page posts: Sift handles conversation, not content scheduling. Pair Sift with a dedicated scheduler if you need that.
- Sales Navigator / Recruiter surfaces: separate LinkedIn products, separate APIs.