LinkedIn capabilities
Syft brings LinkedIn activity into the same account and contact views as your website, CRM, and other go-to-market signals. You can use it to:
- Track public posts from selected people and company pages and identify people who react or comment.
- Collect private signals from a connected team member's account, such as profile viewers, connections, and conversation history, when that person chooses to share them.
- Sync LinkedIn Ads impressions and clicks at the account level.
- Trigger alerts, CRM updates, and motions from LinkedIn activity.
- Run reviewed or automatic LinkedIn outreach sequences from connected sender accounts.
What you need to connect
LinkedIn uses two different connections because public, advertising, and personal account data have different requirements.
| Capability | Required connection |
|---|---|
| Public posts and post engagement | Add the person or company page under LinkedIn settings. Current workspaces collect this public data server-side. |
| LinkedIn Ads impressions and clicks | Connect a LinkedIn Ads account from Integrations. |
| Connection graph, conversations, profile viewers, and LinkedIn outreach | Each participating person must install the Syft Chrome extension, connect their own LinkedIn account, and keep the extension active. |
Tracking posts and engagement
Whose posts can Syft track?
Syft can track the public posts of any LinkedIn personal profile or company page you add. The profile does not have to belong to your organization, and you do not have to administer or be connected to it. For example, you can track posts from your founders, teammates, industry experts, customers, partners, competitors' executives, or a competitor's company page.
To add a profile:
- Open LinkedIn settings, or ask the Syft assistant to track a LinkedIn profile.
- Add a personal profile URL or handle, such as
linkedin.com/in/janedoe, or a company page, such aslinkedin.com/company/acme. - Save the profile. New public posts and their engagement will appear in LinkedIn Activity.
What is synced from a tracked post?
For a public tracked post, Syft stores the post URL and ID, author, text, publish time, available image or video thumbnail, and LinkedIn's total reaction, comment, and share counts. It also collects identifiable people who reacted or left a top-level comment, including their LinkedIn profile, reaction type, and up to 300 characters of comment text.
Each reactor or commenter can become a LinkedIn signal associated with the matching contact and company. You can filter by engagement on any tracked post, a specific post, or posts from a specific tracked author.
Reply comments are not currently returned as separate engagement records or included in Syft's comment count. A post with comment replies can therefore show a lower comment total in Syft than it does on LinkedIn.
Sync cadence
For server-side public tracking, Syft looks for new posts approximately every 30 minutes. Engagement polling is scheduled hourly but becomes less frequent as a post ages. Engagement polling stops after 30 days.
These are expected intervals, not delivery guarantees. Provider availability and queueing can add latency.
LinkedIn outreach and sequences
Syft motions can use a connected LinkedIn account to send a connection request, wait for acceptance, send one or more DMs, follow a profile, or react to a post. A typical multi-step sequence sends a connection request, waits for acceptance, and then spaces follow-up DMs over business days.
For a prospect who is not already connected, Syft sends a connection request before a DM. The connection step waits for acceptance for up to seven days; follow-up DMs do not run if the prospect never accepts. For an existing first-degree connection, a motion can begin with a DM.
Sender accounts and sending capacity
Choose one or more connected LinkedIn accounts as senders when you configure the motion. Each sender must have outreach enabled and an active Chrome extension.
The default connection-request limit is 10 requests per sender in a rolling 24-hour period. An organization can configure a different per-sender limit. Capacity is not pooled: adding a sender adds that sender's own budget but does not increase another sender's limit. This Syft limit applies to connection requests, not DMs; LinkedIn can still throttle either action independently.
When a sender reaches the limit, remaining requests stay scheduled or rate-limited and are retried after capacity becomes available. If no selected sender is active, the motion reports that no active LinkedIn profile is available and the actions remain unsent. LinkedIn can also apply its own account limits independently of Syft.
Sequence guardrails
- A sequence stops when the contact replies.
- A contact who is already in an active sequence is skipped.
- By default, use the Exclude Existing Connections of Sender qualification filter for cold outreach. Remove that filter when the intended audience is existing connections, such as an event invitation or job-change follow-up.
- DMs are sent only to first-degree connections. Non-connections must accept the request first.
- Connection notes, sender status, and daily capacity are validated before an action is sent.
Human review and auto-send
Human review is enabled by default. Syft drafts a plan for each prospect and holds it in the motion's Needs Approval tab. You can review, edit, approve, or reject it before anything is sent. Confirming the motion setup only saves the motion; it does not approve the individual messages.
Turning off Enable Human Review enables auto-send, sometimes called yolo mode. Valid plans then proceed without a per-prospect approval step. Sender, note-length, sequencing, and daily-limit guardrails still apply.
Why the Chrome extension must stay active
Syft uses the connected sender's browser session for outreach and personal signals. If the extension is inactive, these actions pause; public-post and LinkedIn Ads syncing can continue.
LinkedIn signals in Syft and your CRM
| Signal | What Syft captures | Where it appears |
|---|---|---|
| Public post engagement | New posts, reactions, and top-level comments from tracked profiles and company pages | LinkedIn Activity, contact and company timelines, LinkedIn filters, alerts, and motions |
| Profile viewers | People LinkedIn shows as viewing a connected user's personal profile | Contact timelines and the Viewed profile of filter; eligible for CRM sync when the owner shares this stream |
| Connection graph | Connections, sent and received requests, accepted requests, and new followers for a connected user | Warm-path and Connection of filters, contact activity, and motions when the owner shares this stream |
| Conversations and outreach | Sent and received DMs and their conversation activity | Contact timelines, Sent message to and Received message from filters, motion reply detection, and connected CRM activity when the owner shares this stream |
| LinkedIn Ads | Account-level impressions and clicks, including rolling 7-, 30-, and 90-day metrics | Company/account records, LinkedIn Ads filters, scoring, alerts, and CRM fields |
Signals can trigger Slack alerts, CRM create/update actions, webhook or spreadsheet actions, and LinkedIn outreach motions. A LinkedIn signal is only a trigger when you select it; seeing LinkedIn activity does not send outreach automatically.
LinkedIn properties available to CRM destinations
The original LinkedIn-to-CRM integration is included here rather than maintained as a separate page. The available field set depends on the destination and the motion you configure.
Company fields
Contact fields
Connecting LinkedIn Ads
You can sync LinkedIn ad engagement data through Syft's native LinkedIn integration.
- Open Integrations and click Connect for LinkedIn Ads.
- Sign in to LinkedIn if required and grant the requested permissions.
- Choose which LinkedIn Ad Manager accounts to sync. Syft initially imports campaign data from the previous 30 days.
Beta: The LinkedIn metrics sync feature is currently in Beta. Please contact the Syft team to turn it on for your account.
LinkedIn Ads metrics are written to company records daily. You can use the latest exposure data to score accounts, build lists, and trigger motions. The integration provides account-level advertising signals; it does not identify every individual LinkedIn member behind an impression or click.
Personal LinkedIn data sharing
Each connected person controls whether personal LinkedIn data from their account is visible to the organization in Syft. Open LinkedIn settings and use the three controls under Personal LinkedIn data sharing:
- Share my network connections — identifies warm relationship paths into target companies.
- Share my LinkedIn conversations — shows outreach history and activity in Syft and connected CRMs.
- Share my profile viewers — shows prospects viewing the user's profile in Syft and connected CRMs.
All three controls are off by default for new connections. Only the person who owns the LinkedIn account can turn them on. An administrator or teammate cannot enable another user's personal streams.
When a stream is off, Syft does not make its activity visible in timelines or filters, use it to trigger motions, or push it to CRM or Slack. Connections and other minimum account state may still sync privately when the user is selected as a sender; the sharing control governs team visibility and activation, not the private state required to operate that sender account.
These controls apply to personal data from a connected user's account. Public posts and public post engagement that the organization explicitly tracks are handled separately.
There is no longer a personal Sync Posts toggle. Add or remove public profiles from the organization's tracked-profile list instead.
FAQ and unsupported capabilities
Can Syft track someone who does not work at my company?
Yes. You can track public posts from any personal profile or company page, including a competitor. Public tracking does not grant access to private or restricted LinkedIn content.
Is there a limit on how many profiles I can track?
It depends on how your organization collects public LinkedIn activity:
- Server-side tracking (the default for newer organizations): there is no fixed cap. Add as many profiles, including competitor profiles, as you need.
- Browser-extension tracking: each team member who has installed the Syft extension adds capacity for 2 tracked profiles. If you try to add more profiles than your team's capacity allows, Syft shows a warning. To increase capacity, have more team members install the Syft browser extension.
Can Syft tell me who viewed a LinkedIn company page?
No. LinkedIn does not provide real-time, person-level visitor events for company pages. Syft can collect personal profile viewers when that profile owner enables sharing, and it can track people who follow or engage with a company page's public posts.
Does Syft include replies in a post's comment count?
No. Syft currently captures top-level comments. Comment replies, including the post author's replies, are not included, so the count can be lower than LinkedIn's displayed total.
Will Syft shorten a connection note that is too long?
No. The limit is 200 characters for a standard sender and 300 for a premium sender. An over-limit plan is rejected or marked invalid so it can be edited; Syft does not truncate the note or silently remove it.
What happens after a sender reaches the daily limit?
The remaining connection requests stay scheduled and retry when that sender's rolling 24-hour capacity opens. Switching on another sender does not transfer unused capacity between accounts. The default Syft limit is 10 connection requests per sender, though your organization can configure it.
What does Syft deliberately not automate?
Syft's supported action surface is connection requests, first-degree DMs, follows, and reactions to a post. It does not automate:
- Publishing LinkedIn posts or articles.
- Writing comments or comment replies.
- InMail, Sales Navigator workflows, group messages, endorsements, recommendations, or event invitations.
- Withdrawing old pending connection requests.
- Access to private posts, private company-page visitors, or another person's private connection graph.
- Sock-puppet accounts or third-party sequencer integrations such as HeyReach, Lemlist, or Waalaxy.
Why is a sender shown as inactive?
A sender can be inactive because the extension was disabled or uninstalled, Chrome has not run it recently, the LinkedIn session expired, or the extension is outdated. Verify the extension is enabled, update it, sign in to LinkedIn in the same Chrome profile, and open the extension to reconnect. Syft treats an extension that has not checked in for three days as inactive.