Trigify Is Shutting Down: How to Move Your Linkedin and X Profile Tracking to MultiFollow
Somewhere in your stack there's a Clay table that fills up on its own. A champion posted about a new budget. A prospect commented on a thread about switching tools. Someone on your target list liked a competitor's launch post. Nobody on the team thinks much about where those rows come from, because they keep arriving.
If they come from Trigify, they'll stop arriving on October 23.
On September 23, Trigify announced that its team is joining HubSpot and that the standalone platform is being retired. For most customers, access ends at 11:59pm BST on October 22, 2026 (6:59pm Eastern). Trigify says accounts won't be migrated to HubSpot, and that integrations, API access, monitoring, and signal collection all stop at that moment. If your contract has a different notice period, Trigify will have sent you your own date.
I work on MultiFollow, so keep that in mind as you read. We built it to do one part of what Trigify did. You give it a list of Linkedin and X (Twitter) accounts, and we alert you within seconds when one of them posts, comments, or (for Linkedin people) likes something. Tracking is anonymous, so the people on your list are never notified.
This post covers how to move your tracked profiles over before the cutoff, which Trigify signals carry across, and which ones you'll need another tool for. If you're still weighing your options, our comparison of Trigify alternatives covers the wider field.
What to save before October 22
Trigify's notice asks customers to save whatever they want to keep, using the export options in the app or by contacting their team. For profile tracking, the thing most worth saving is the list of who you were watching and why. Past signals are nice to keep, but you can't rebuild that list from them.
Start with the people and companies you monitor. Trigify's Social Signals setup let you paste profile URLs or upload a CSV, so the original file may already be sitting in your CRM or a Clay table. If it isn't, copy the profile URLs out of Trigify while you can still see them.
Then write down what each monitor was watching for. Social Signals offers 16 signal types, from "Changed role" to "Liked competitor content," and most of them needed inputs like competitor URLs or topic keywords. Those inputs took your team the longest to tune, and they won't be in any export of past results.
Last, list every place a Trigify workflow sent its output. That might be a CRM, a Clay table, a Google Sheet, Slack, or a Zapier or n8n scenario. Each of those goes quiet on the 23rd, and each one needs a new source.
If you do want the history, Trigify's help center says workflow results download as CSV from the Output tab. The export only covers the rows currently loaded, so page through and download each page.
Which Trigify signals carry over?
With the list saved, the next question is how much of it MultiFollow can run. That depends on which signals you leaned on, and on one difference in how the two tools work.
Trigify checked on a schedule. Social Signals ran daily by default, weekly if you wanted to save credits, and hourly on plans that included it. Its help center also says new posts from monitored profiles could take several hours to appear. We check every second, and alerts usually land within a couple of seconds (up to about a minute during congestion). There are no credits, because plans are priced by how many accounts you track.
The person signals map like this, from the ones we cover to the ones we don't.
Trigify signal
In MultiFollow
New posts from a monitored Linkedin or X profile
Track posts
Commented on tracked content
Track comments (every comment the person makes, narrowed by keywords if you want)
Liked competitor, company, or person content
Track likes on a Linkedin person, then filter by the liked post downstream
Posted about tracked topic
Included keywords on the tracker
Became hiring or posted a job ad
Only when they post about it, using a keyword like hiring
Changed role, changed company
Not tracked
Competitor engagement, engaged with tracked topic
Not tracked
Buying-window and influence signals, AI insights
Not tracked
If most of your Trigify value sat in the top four rows, you'll be fine. If it sat in the bottom three, read the next section before you move anything.
What MultiFollow won't replace
The biggest gap is job changes. We don't track them, and a champion moving to a new company is one of the strongest signals in the Trigify list. You'll only see it if they post about it and your keywords match, so keep a job-change tool or your CRM enrichment for that part.
The second gap is engagement audiences. Trigify could tell you who interacted with a competitor's content, even if you'd never heard of those people. We can't. We only see what the accounts on your list do, so we'll tell you when your prospect likes a competitor's post, but not who else did.
We also don't score anything. Trigify's buying-window signals and AI insights summarized a person's activity into a single read. We send the raw activity, and if you want a score, Clay or your CRM is the place to build it.
Coverage is narrower, too. We track Linkedin people, Linkedin company and showcase pages, and X accounts. Company pages only alert on posts. On X we track posts and replies but not likes, which have been private since 2024. We don't track Youtube channels, Substack, or podcasts.
And if your Trigify setup was mostly keyword searches across Linkedin, Reddit, and X, that's keyword listening, which is what our sister product KWatch.io does.
Moving your watchlist over
Once you know what's coming with you, the move itself takes an afternoon. It's three steps.
1. Pick a plan that fits the list
Count your Linkedin and X profiles separately, because each plan has its own limit for each. These are the limits on our pricing page as of October 2026.
Plan
Price
Linkedin profiles
X profiles
Slack, API webhooks, bulk CSV import
Free
$0
1
2
No
Essential
$19/mo
5
10
No
Business
$79/mo
25
50
Yes
Enterprise
$199/mo
100
200
Yes
Agency
Custom
Custom
Custom
Yes
If your Trigify monitors fed a CRM, Clay, or Slack, Business is the plan to look at, because it's the first one with webhooks, Slack, and bulk import. Linkedin is where you'll hit the limit first. If you tracked 60 Linkedin people, you're on Enterprise, or you trim the list to the accounts in an open deal or a renewal window and rotate the rest.
2. Turn your list into a CSV
Our bulk import needs two columns, platform and profile url (with the space). The platform is linkedin or twitter, and X rows still use twitter. If you're starting from a Trigify or CRM export, keep the column with the profile URLs, rename its header, and add the platform column.
The optional columns are where your Trigify setup gets rebuilt. They set which activity to track, your included and excluded keywords (up to 10 each, comma-separated), and a per-tracker API or Slack webhook. A file for one deal might look like this.
Your "Posted about tracked topic" keywords go straight into the included keywords. The "Commented on tracked content" signal works a little differently here. There's no setting for a specific post, so you'll get every comment the person makes, and you can narrow it by the words in the comment.
Keep likes off for most people. They have no text, so keywords can't filter them, and they'll flood a channel on a long list. Turn them on for the few people whose likes you'd act on, like the champion above.
3. Import it and prove one alert
In the dashboard, open Bulk Import, choose your file, and leave "Override existing alerts" off unless you mean to replace what's there. New trackers start right away. Our bulk import guide covers the formatting mistakes that make a row fail.
Then wait for one real post or comment to land where you expect it before you import the rest.
Reconnecting Clay, n8n, and your CRM
With the trackers running, the last step is pointing the old pipes at the new source. You can set one API webhook for the whole account, or a different one per tracker, and the per-tracker URL wins. That's how competitor alerts end up in one Clay table and prospect alerts in another.
Every alert is a POST request with a small JSON body. This is the example from our API webhooks page.
{
"platform": "linkedin",
"profile_url": "https://www.linkedin.com/in/erikatrautman/",
"query": "URL: https://www.linkedin.com/in/erikatrautman/. Track posts. Track comments. Track likes.",
"datetime": "2025-01-19T05:52:00Z",
"link": "https://www.linkedin.com/posts/erikatrautman_vice-president-strategy-and-business-operations-activity-7272270503808000000-OxBb",
"content": "I've got two more great leadership positions I'm filling! I am so inspired by the vision and the culture here at Sprout. So come join me to transform how companies leverage social media to connect with their customers.",
"activity_type": "post"
}
If your Clay table or n8n flow was built on Trigify's New Post trigger, most fields have a direct match.
Trigify variable
MultiFollow field
text
content
authorUrl
profile_url
postUrl
link
datePosted
datetime
source
platform
Rename those five and the rest of the flow should keep working. We don't send the like and comment counts Trigify included, so drop any step that filtered on them. You'll want a new branch on activity_type, which tells you whether the alert is a post, a comment, or a like.
That branch is also where you rebuild "Liked competitor content." Linkedin post links usually start with the author's handle, like the erikatrautman_ part above, so a filter step can keep likes on posts from your competitors' handles and drop the rest. I'd test that on a handful of real like alerts before you trust it.
Trigify also enriched the people it found. With us, send profile_url into Clay and enrich there. Our guide to routing alerts to Slack, Clay, n8n, and Zapier walks through each destination.
Run both until the cutoff
You've got two weeks, and I'd use them. Trigify's first run looked back 30 days, but we alert on new activity from the moment you add a tracker. Setting it up now means you can run both tools on the same people and compare what each one catches before Trigify goes dark.
Start with the account you'd least like to lose track of. Add its champion on the MultiFollow free plan, which tracks 1 Linkedin and 2 X profiles with email alerts and no card, and wait for a real post or comment to arrive. When it does, move to Business and import the rest of your list.
MultiFollow.io