> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getswan.com/llms.txt
> Use this file to discover all available pages before exploring further.

# LinkedIn engagement

> Fire a trigger when someone posts, comments, or reacts on a tracked LinkedIn profile or company page.

A LinkedIn engagement trigger watches specific LinkedIn profiles or company pages and fires whenever someone posts, comments, or reacts on them. It's a way to turn people showing up in your prospects' or customers' LinkedIn activity into leads a playbook can act on — Swan cannot post, comment, or react on LinkedIn on your behalf, only monitor engagement and act on what it sees. Create one from [Triggers](https://agent.getswan.com/triggers) → New trigger → LinkedIn Tracking (or go straight to [agent.getswan.com/triggers/new?type=LINKEDIN\_ENGAGEMENT](https://agent.getswan.com/triggers/new?type=LINKEDIN_ENGAGEMENT)).

## What you track

For each entity you add (a person's profile or a company page URL), you choose independently — add and manage tracked entities from the trigger's Configuration tab, using **Add Another Profile** for each new one:

* Whether to track new **posts** from that entity.
* Whether to track **comments** on those posts.
* Whether to track **reactions** (likes and other reactions) on those posts.

You can also set "only posts" mode for an entity, which fires the trigger the moment a new post goes up rather than waiting on its engagement — useful if you just want to react to what an account publishes, not who engages with it.

## Polling

Swan checks tracked entities for new posts every hour. For any post published in the last 5 days, it also checks for new comments every hour. Reaction counts are captured once, shortly before a post ages out of that 5-day tracking window, rather than every hour — reactions tend to level off, so one snapshot near the end of the window is enough. There's no notification sent when a polling cycle finds nothing new — this is an event-driven trigger, it only fires when there's something to act on.

Fetching posts and engagement primarily uses public LinkedIn data. If that isn't available for a particular profile, Swan falls back to pulling it through your organization's connected LinkedIn sender accounts, rotating across whichever account was used least recently so the load is spread out rather than hitting the same account repeatedly.

## Caps and filters

For the trigger, you can set:

* **Max comments / max reactions to pull per post** — defaults to 1,000 comments and 200 reactions if you don't set a lower cap.
* **Headline include or exclude keywords** — only engagers whose LinkedIn headline contains (or doesn't contain) specific keywords count as a match. It's one or the other: the trigger can filter by an include list or an exclude list, not both at once. This applies to commenters and reactors, not to the tracked entity itself.
* **A topic filter** — for posts, Swan can check whether a post's content is actually relevant to a topic you describe, and skip it if it isn't.

Pausing works per post, not per profile: you can stop monitoring a specific post (and resume it later) without deleting the trigger or the tracked profile it came from.

## Requirements

You need at least one connected LinkedIn [sender](../outreach/senders-and-connected-accounts) in your organization to create this trigger — even though most engagement data comes from public sources, a connected account is needed as the fallback path when public data isn't available. Connect one at [agent.getswan.com/outreach/sequences/senders](https://agent.getswan.com/outreach/sequences/senders).

## Cost

Each qualifying engagement event (a new post, comment, or reaction, depending on what the entity is tracking) costs 1 credit to fire the trigger, on top of whatever the resulting run does. See [credits](../administration/credits).

## Common questions

**Can I track a LinkedIn company page instead of a person?**
Yes — add the company page URL as a tracked entity the same way you would a personal profile.

**Can Swan post, comment, or react on LinkedIn for me?**
No. This trigger only monitors activity; sending outreach in response is a separate step your trigger's instructions or a [sequence](../outreach/how-sequences-work) can take.

**How fresh is the engagement data?**
Posts and comments are checked hourly. A brand-new comment can take up to an hour to be picked up.

**Does it track who visited a profile, or only who posted/commented/reacted?**
Only posts, comments, and reactions. Swan does not have visibility into who viewed a profile.

**Will I get a "nothing found" notification if a check comes back empty?**
No — this trigger only fires on new activity, so quiet periods produce no notifications at all.