A Head of Growth at a 200-person company signs up for your trial on Tuesday. She connects one integration, clicks around for ten minutes, and leaves. Your onboarding sequence sends her the "Welcome aboard" email, then "Have you tried feature X?", then "Your trial ends in 3 days." She opens one of them.
Two days later she posts on Linkedin about how her team is drowning in manual reporting. That's the exact problem your product solves, and it's the best opening you'll get all month. Nobody on your team sees it.
I work on MultiFollow, which sends you an alert when specific Linkedin and X accounts post, comment, or like something. This post walks through a small workflow for product-led teams: when a promising person signs up, we start watching their public activity automatically, and we stop when the trial ends.
Most PLG teams already score trials on product usage. Did they invite a teammate? Did they connect data? That's useful, but it only tells you what someone did inside your app. It says nothing about why they signed up or what's going on in their week.
Public activity fills that gap. A trial user who comments on a thread about switching tools is shopping. One who likes a competitor's pricing announcement is comparing. One who posts that they just took over a new team is probably rebuilding their stack. None of that shows up in your product analytics.
The other benefit is timing. Your nurture emails go out on day 1, 3, and 7 because that's what the sequence says. A Linkedin post goes out when the person is thinking about the problem, which is a much better moment to show up.
You don't want to track every signup. Watching students, competitors poking around, and people using a Gmail address burns tracker slots and fills Slack with noise.
I'd only add someone when the signup looks like a real buying opportunity. A work email from a company in your target size range, a job title close to the buyer, or a high-intent action like booking a demo are all good filters. If you already score leads in Clay or your CRM, use that score and pick a threshold.
The size of the watchlist matters too, because a trial usually lasts a week or two and the slot frees up when it ends. The table below shows what each plan covers.
| Plan | Price | Linkedin profiles | X accounts | REST API, Slack, and API webhooks |
|---|---|---|---|---|
| Free | $0 | 1 | 2 | No |
| Essential | $19/month | 5 | 10 | No |
| Business | $79/month | 25 | 50 | Yes |
| Enterprise | $199/month | 100 | 200 | Yes |
The automated setup below needs the REST API, so it starts at Business. With 25 Linkedin slots and two-week trials, that's room for around 50 qualified trials a month if you remove each tracker when the trial ends. Enterprise takes that to around 200. If your product gets thousands of signups a week, keep this for the top slice of the funnel.
The flow has four parts. A signup comes in, you find the person's Linkedin and X profiles, you create a tracker through our API, and the alerts land where your team already works.
Trigger on the event your app already sends, whether that's a webhook from your auth provider, a new row in your database, or a new contact in your CRM. Zapier and n8n can both start a workflow from any of those. Run your qualification filter here so only good signups move on.
MultiFollow needs a profile URL, and it doesn't look one up from an email address. Most teams already have an enrichment step for this (Clay is a common pick) that returns the person's Linkedin URL. X handles are harder to find, so treat X as a bonus when you have one.
Send a POST request to our API with the profile URL. For a Linkedin profile, the request looks like this:
curl -X POST "https://api.multifollow.io/api/v1/trackers/linkedin" \
-H "Authorization: Bearer your-api-key-here" \
-H "Content-Type: application/json" \
-d '{
"url": "https://www.linkedin.com/in/example-signup/",
"track_posts": true,
"track_comments": true,
"track_likes": true,
"slack_webhook_url": "https://hooks.slack.com/services/...",
"enabled": true
}'
Two fields are worth a closer look. enabled defaults to false, so set it to true or the tracker won't run. And slack_webhook_url sends this tracker's alerts to a specific channel, like #trial-signals, instead of your account's default. There's an api_webhook_url field that works the same way if you'd rather send alerts to Clay, n8n, or your CRM. Save the tracker ID from the response, because you'll need it in step 5.
If the person posts a lot, add up to 10 keywords in message_included_keywords (your category, a competitor, the pain you solve) and we'll only alert on activity that mentions one of them.
When a tracked signup posts, comments, or likes something, the alert shows the platform, the profile, the time, the link, the text, and the activity type. In Slack it reads something like this:
New Linkedin post from Priya Natarajan (Head of Growth, Example Logistics)
"Our weekly reporting takes two people a full day. There has to be
a better way to pull this together..."
https://www.linkedin.com/feed/update/...
(The person and company above are example data.)
The useful part is putting that next to what she's done in the trial. If she signed up, connected nothing, and then posts about reporting pain, she probably hasn't found the feature that solves it. That's a short, specific message from whoever owns the account.
When the trial converts, expires, or the person goes cold, call the Delete Tracker endpoint with the ID you saved. That frees the slot for the next signup. If a trial turns into a sales conversation, keep the tracker running, since that person is now part of a deal. Our post on routing alerts to Slack, Clay, n8n, and Zapier covers the delivery side in more detail.
If you use an AI agent like Claude or Cursor, you can also do all of this through our MCP server, which creates, updates, and deletes trackers with the same API key.
The worst follow-up is "I saw your post, want to upgrade?" She signed up for a trial, not a sales call, and that message tells her she's being watched.
It works better to talk about the problem she described. Something like "Saw you're spending a day a week on reporting. The scheduled reports feature in your trial does that in about five minutes, want me to set one up with you?" She gets something useful whether or not she buys. If you have a real point to add, a thoughtful comment on her post works too, and it's lower pressure than a DM.
It's the same habit as prepping for a sales call with someone's activity, just pointed at people who came to you first.
If you also want to hear when anyone (not just signups) mentions your product or category on Reddit, X, or Hacker News, that's what our sibling product KWatch.io does.
Before automating anything, pick the most promising trial signup from the last few days and add them by hand on the free plan, which covers one Linkedin profile and two X accounts. If you see something worth replying to before their trial ends, you'll know the workflow is worth building.
Julien, Product Manager at MultiFollow