Trigify Is Shutting Down: Where to Move Your LinkedIn Signal Workflows

Trigify announced on 23 September 2026 that its team is joining HubSpot and that the standalone platform is winding down: for most customers, access, integrations, API access and signal monitoring end at 11:59pm BST on 22 October 2026. If your go-to-market team ran LinkedIn signal workflows on it, each one maps to a Cargo action or cookbook: post reactions and comments (linkedin.searchPostReactions, linkedin.searchPostComments, 0.05 credits per person returned), profile and company page viewers (0.05 per viewer), keyword post search (linkedin.searchPosts, 0.25 per search) with the social listening cookbook on top, new hires with the new-hire detection cookbook, and job changes in your own contacts with waterfall.detectJobChange (3 credits per contact).

Export first, rebuild second. The steps below use the Cargo CLI, so a coding agent can run them end to end.

What Trigify announced #

From Trigify’s announcement, “The Trigify team is joining HubSpot: Our next chapter”, dated 23 September 2026, on trigify.io:

• “Today, we’re excited to announce that the Trigify team is joining HubSpot (NYSE: HUBS).”
• “As the Trigify team begins its next chapter with HubSpot, we’ll be winding down the standalone Trigify platform.”
• “For most customers, access will remain available until 11:59pm BST on 22 October 2026.” Customers with different contractual notice periods receive their dates directly.
• “Trigify integrations and API access will stop when account access ends at 11:59pm BST on 22 October 2026.” Signal monitoring stops at the same point.
• “Your Trigify account will not be migrated to HubSpot.”
• “Please save any information you want to keep before your account access ends.” The announcement points to the export options in the product and to hugo@trigify.io for help.

Congratulations to the Trigify team. HubSpot is where the team is going, and some of them will bring their signal, data and context expertise into HubSpot, according to the announcement. It does not describe a HubSpot product that replaces the platform, or a date for one, so this article does not guess at either. If your team already runs on HubSpot and can wait, follow HubSpot’s own announcements. If you need the workflows running after 22 October, rebuild them now.

Before 22 October #

1. Export your data from Trigify: the lists of people who engaged, the posts and keywords you tracked, and any signal history you want to keep.
2. List every automation that reads from Trigify (CRM writes, Slack alerts, sequencer enrollments). Each one breaks on 22 October, so each needs a new source.
3. Rebuild each signal with the matching section below, and run it next to the old one until the cut-off.

Map each workflow to Cargo #

Prices are list prices in credits from each action’s definition in Cargo’s code.

Viewer extraction runs on a LinkedIn session: authenticate LinkedIn with the Cargo Chrome extension, then pick that user in identityIds. Company viewers also need that user to be an admin of the page, and the page to be on a Premium tier.

A new account starts with 100 free credits and no card, which covers, for example, 2,000 reactions or 400 post searches.

Run it #

1. Install and sign in

npm install -g @cargo-ai/cli
cargo-ai login --email you@company.com                 # sends a code
cargo-ai login --email you@company.com --code 123456   # creates the account on first use

2. Post engagement: who reacted to and commented on a post

urn takes a LinkedIn post URL or post ID. type filters reactions (ALL, LIKE, EMPATHY, APPRECIATION, INTEREST, PRAISE; default ALL).

cargo-ai orchestration action execute \
  --action '{"kind":"connector","integrationSlug":"linkedin","actionSlug":"searchPostReactions"}' \
  --data '{"urn":"https://www.linkedin.com/feed/update/urn:li:activity:1234567890","type":"ALL"}' \
  --wait-until-finished

cargo-ai orchestration action execute \
  --action '{"kind":"connector","integrationSlug":"linkedin","actionSlug":"searchPostComments"}' \
  --data '{"urn":"https://www.linkedin.com/feed/update/urn:li:activity:1234567890","sortBy":"Most recent"}' \
  --wait-until-finished

Each reaction comes back with reactor.name, reactor.headline, reactor.linkedin_url and the reaction type. Each comment carries commenter.name, commenter.headline, commenter.linkedin_url, the comment permalink and its replies. To watch several posts, pass them as records to cargo-ai orchestration action execute-batch instead.

3. Posts about the problem you solve

cargo-ai orchestration action execute \
  --action '{"kind":"connector","integrationSlug":"linkedin","actionSlug":"searchPosts"}' \
  --data '{"searchKeywords":"\"lead routing\" OR \"speed to lead\"","sortBy":"Latest","datePosted":"Past week"}' \
  --wait-until-finished

Each post returns post_url, text, posted, poster_name, poster_title, poster_linkedin_url, num_likes, num_comments and num_shares. The search also filters by author (fromMemberUrns), company (fromCompanyIds), mentions (mentioningMemberUrns, mentioningCompanyIds), authorIndustry, authorKeyword and contentType.

To run it every week instead of by hand, deploy the social listening cookbook. It syncs the past week’s posts for your keywords every Monday (40 posts by default), has an agent pick at most five worth joining against your ideal customer profile, reads comments on those five only, and posts one digest to a Slack channel you lock. It never likes, comments, connects or messages anyone.

cargo-ai project init my-signals
cd my-signals
cargo-ai project add cookbook/social-listening
# edit searchKeywords in infra/social-listening/models/linkedin-posts.ts and the Slack channelId
cargo-ai project plan
cargo-ai project deploy

4. Profile and company page viewers

cargo-ai orchestration action execute \
  --action '{"kind":"connector","integrationSlug":"linkedin","actionSlug":"extractProfileViewers"}' \
  --data '{"identityIds":"<your LinkedIn user id>","limit":100}' \
  --wait-until-finished

limit defaults to 100 and caps at 1,000 for profile viewers. extractCompanyViewers takes linkedinCompanyUrl, the admin’s identityIds, and a limit up to 10,000. The identityIds value comes from the action’s autocomplete, which lists the LinkedIn users synced through the Chrome extension.

5. Job changes and new hires

For people already in your CRM, waterfall.detectJobChange takes professional_email and company_domain (it also accepts personal_email, contact_linkedin and company_linkedin) and returns job_change_status (moved, left, no_change or unknown) with the person’s current person.company_name, person.company_domain and person.title. At 3 credits a contact, run it on a filtered segment, such as last year’s champions, and pilot 10 to 20 rows first. The track-job-changes skill wraps it for a coding agent.

cargo-ai orchestration action execute-batch \
  --action '{"kind":"connector","integrationSlug":"waterfall","actionSlug":"detectJobChange"}' \
  --records '[{"professional_email":"jane@example.com","company_domain":"example.com"}]' \
  --wait-until-finished

For people outside your CRM who just took a role you sell to, deploy the new-hire detection cookbook (cargo-ai project add cookbook/new-hire-detection). It runs a Sales Navigator search filtered to recent job changes, enriches the company each person joined, has an agent check that company against your ideal customer profile, and posts the ones that fit to a locked Slack channel. It ships with no schedule, because each sync re-buys the search.

Caveats #

• Engagement and viewer data describe people. Use it for business outreach with a lawful basis, check your suppression list, and keep the message relevant to the person’s job.
• Every action above returns data and stops. Nothing is sent to anyone unless you wire a step that does.
• Prices are per item returned, so a post with 2,000 reactions costs 100 credits to pull in full. Filter by reaction type or pick the posts that matter before you run them.

Frequently asked questions #