LinkedIn prospect alerts: how to get told when an ICP-matched prospect is active, and what to do next
Get alerted when an ICP-matched prospect is active on LinkedIn: Slack, webhook and daily brief alerts, routes per rep, repeat engagement and what to do next.

TL;DR: traxy alerts your sales reps when an ICP-matched prospect is active on LinkedIn. When someone with a 50%+ match to your ICP engages with posts about the problem you solve, or with the people, posts and company pages you track, traxy makes them a lead and can post an alert with the post or comment behind it to a rep's Slack channel, send it to a webhook, or include it in a daily brief. When a lead you already have engages again, traxy can post a repeat-engagement event. The rep then sends a one-off LinkedIn message or email, or the lead goes into a LinkedIn and email campaign you approve before it runs.
We make traxy, so read this as the vendor's guide for an in-house sales team. Every traxy step below comes from the traxy docs pages linked in each section: Slack, routes, webhook, daily brief, Tracking and team work, checked November 15, 2026. If you are an agency sending a client's leads to the client's own team, the client Slack lead alerts guide covers that setup.
How can sales reps get alerted when an ICP-matched prospect is active on LinkedIn?
Use a tool that does three things in order: watches the LinkedIn activity that matters to you, checks each person who engages against your ICP, and sends only the people who fit to the place your reps already work. In traxy that is five steps:
Tell traxy who you sell to and what to watch. Give traxy your website. It drafts your ICP and a Signal Brief (the topics and activity worth watching), and you fix anything that's off under Targeting.
Add the sources you care about. Under Targeting, track the people (competitors, creators, teammates, investors), single posts and company pages whose engagers you want to know about. You can also switch on Profile views under Targeting > Signals > LinkedIn activity.
Let traxy qualify who shows up. A person becomes a lead only with a 50%+ match to your ICP. Each lead shows the post, comment, like or repost that put them on your list, with a Warm, Related, Activity or ICP match label.
Send the leads to each rep. Save a shared view of the leads each rep owns, and add a route from that view to the rep's Slack channel or to a webhook. Turn on repeat-engagement events, and a daily brief if the rep wants one summary.
Act on the alert. The rep opens the lead, reads the post or comment behind it, assigns it to themselves, and sends a one-off message or puts the lead in a campaign.
That covers the first half of the job. traxy runs your entire LinkedIn GTM end to end, from finding high intent leads from social intent to enriching and researching each one, to running relevant, personalized LinkedIn and email outreach to them on autopilot. The autopilot part starts only after you approve it: you test a campaign on sample leads with nothing sent, review who joins and who is skipped, and approve the launch, then it runs on its own from your own connected sender accounts. Or you approve every message in a review queue. Replies, unsubscribes and hard bounces stop the sequence.
Which LinkedIn activity can traxy alert on?
traxy alerts on two things: a new qualified lead, and new activity from a lead who already qualified (a repeat engagement). Both come only from the sources your workspace watches, and only for people who pass your ICP check. traxy does not alert on every action of every LinkedIn user.
The activity that can turn someone into a lead:
Post engagement on your topics. People who like, comment on or write posts about the problem you solve, based on your Signal Brief.
Tracked people. traxy watches a tracked profile's posts and qualifies the people who engage. Each profile gets a relationship tag: competitor, teammate, influencer, investor or custom. For an active profile, ongoing monitoring follows the five most recent posts published after you added it. Older posts need their own post request (Tracking docs).
Tracked single posts. Paste any LinkedIn post URL (yours, a competitor's, a creator's) and traxy finds the engagers who fit your ICP.
Tracked company pages. Add a company by domain or LinkedIn company page and traxy reads its page posts for engagers who fit. This finds people engaging with the page's posts, not every employee at that company.
Your own and your team's posts. Track your own LinkedIn profile, or your teammates' profiles, and engagement on those posts becomes qualified leads.
Profile views. Switch on Profile views under Targeting > Signals > LinkedIn activity, and traxy picks up profile views of the sender accounts you connect. LinkedIn does not reveal viewers in private mode, so those never appear. More in how to turn LinkedIn profile views into leads.
There is one more way to find people that is not an alert: social intent search. You describe the person and the need in plain English and search 71M+ scanned LinkedIn likes, posts and comments. It answers "who has talked about this?" when you ask, and each person comes with the post or comment behind them.
Signals outside LinkedIn, such as hiring, funding or job changes, come from the research a campaign runs on each lead. They are facts traxy looks up when you ask, not a live event feed, so plan your alerts around LinkedIn activity.
Where do the alerts go: Slack, a webhook or the daily brief?
Most sales teams send alerts to Slack, use a webhook when the CRM or another system should act on them, and add the daily brief for one summary a day. You can use all three at once.
Destination | What it carries | Where you set it up | Fits when |
|---|---|---|---|
Slack | Lead alerts, lead-reply notifications, repeat-engagement events and a daily summary | Integrations > Slack: authorize, set the default channel, Test trigger, add routes | Reps live in Slack and want each lead where they already talk |
Webhook | Signed lead events: first delivery and repeat engagement, to any HTTPS endpoint | Integrations > Webhook: name and URL, Send test payload, add routes | Your CRM, a sheet or your own code should create the task or record |
Clay, Zapier or n8n | Lead events into a table, a Zap or a workflow | Integrations > pick the tool: endpoint, test, routes | You already run a workflow that should pick up new leads |
Daily brief | A scheduled brief from trax, the traxy agent | Settings > Agent > daily brief: turn it on, pick the channel and the time | A rep or manager wants one look a day instead of a stream |
A few things to know about each:
Slack. Lead routes can post to their own channels. The default channel gets the notifications and tests set to use it; lead routes and lead-reply notifications can use other channels. If the traxy app is missing from a private channel's picker, invite it to that channel. A successful Test trigger shows the test request worked; it does not promise every later delivery, so check the channel in the first days (Slack docs).
Webhook. Each request carries the
X-Traxy-SignatureandX-Traxy-Timestampheaders, so your receiver can check it came from traxy. First-delivery and repeat-engagement events do different jobs, so map them separately. Delivery can retry after a temporary failure, so your receiver should handle the same event twice without creating two tasks (webhook docs).Daily brief. It is delivered in traxy or in Slack at the time you choose. For Slack, connect the workspace and channel first. If a brief doesn't arrive, check that it is turned on and that the Slack connection works before you change your targeting (daily brief docs).
How do routes send each rep their own leads?
A route connects one lead view to one destination, such as a rep's Slack channel or a webhook endpoint, with Auto or Manual delivery and an ICP match threshold. Give each rep a shared view and a route, and each rep gets only the leads in their view.
Build the rep's view. In Leads, add the filters that describe the rep's patch: territory, segment, signal, or a tag for their named accounts. Save it as a new view and share it. Campaigns and routes use shared views, and a personal view becomes shared when you save a route that uses it.
Add the route. Open the integration's Routes tab, add a route, pick the rep's view and their channel or endpoint.
Choose Auto or Manual. Auto delivers leads as they enter the view. Manual means a rep or manager sends selected leads from Leads > Send to.
Set the ICP match threshold. For an automatic route, the threshold decides which leads that route delivers. You might set a higher threshold for a rep's channel than for the webhook that feeds your CRM. It does not change who qualifies as a lead.
Send the leads already in the view. Automatic routes don't backfill. Only leads that enter the view after you save the route are sent on their own, so send the existing ones with Leads > Send to.
Two habits keep this clean. First, make sure the views don't overlap: if a lead fits two reps' views and both have automatic routes, both reps get it. Second, add a catch-all route from All leads to a shared team channel so a lead that fits nobody's view still reaches someone. A route can pause itself after repeated failures; fix the connection before you resume it (routes docs). For territory, segment and account-owner rules in more detail, see how to route LinkedIn leads to the right sales rep.
What happens when a lead you already know engages again?
traxy can post a repeat-engagement event: new activity from a lead who already qualified. It is not counted as a new lead, so the person does not show up twice as a fresh lead, and your rep sees that someone they already know is active again.
Turn it on in the Slack settings, next to the daily summary. On a webhook, repeat engagement arrives as its own event type, separate from first delivery, so your CRM can update the existing record instead of creating a new one.
What a rep should check when a repeat-engagement event arrives:
Is the lead already in a campaign? If a sequence is running, let it run. A second message from a different rep is how buyers end up annoyed.
Who owns it? If the lead is assigned to someone else, leave it to them, or add a shared note with what you saw.
What did they engage with this time? Open the lead's Signals tab and read the new post or comment and its date. A second comment on a competitor's post about the same problem is a better reason to write than a single like.
Did they already reply? If traxy runs your outreach, the reply is in the one inbox, and the sequence stopped when they replied.
If the lead is not in a campaign and nobody owns it, the repeat engagement is often the moment to reach out, with the new activity as the reason.
For prospects who went cold and deals you lost, how to re-engage cold leads and lost deals when they show new activity on LinkedIn covers tracking lost accounts and writing the comeback message.
Who owns the alert, so two reps don't work the same lead?
The rep who acts on an alert assigns the lead first. In traxy, open the lead and choose Assign to pick a workspace member or Assign to me. You can also assign a group of leads at once from a selection. Assignment shows who is working the lead; it does not change its qualification or its source (team work docs).
Shared notes. Notes on a lead are visible to everyone in the workspace, so "commented on a competitor's pricing post, sent a connection request" travels with the lead.
Tags. Use tags to mark a stage in your team's process or a named account list.
A personal queue. Filter Leads by assignment, tags, notes and status and save it, for example "active leads assigned to me that still need review."
When several reps share one channel, agree on a simple rule: whoever assigns the lead owns it. More on this in how to stop two reps contacting the same LinkedIn lead.
What should a rep do after an alert?
Read the signal first, then pick one of three next steps: a one-off message, a campaign, or the same actions from your AI chat through the traxy MCP. An alert is a reason to look at the person, not a reason to pitch.
Read the signal before you write
Open the lead and check the post or comment behind it and its date. A comment or a question gives the clearest opening: answer the problem they raised. A like gives you a topic, not an endorsement, so mention the topic and not the like. A person who fits your ICP but has a weak signal gets a plain, role-based introduction.
Send a one-off message
For a single lead, open it and choose Message. Check the To, From and channel, then send a LinkedIn message, a connection request or an email to that one lead. It goes from your own connected sender account.
Put the lead in a campaign
When the same kind of alert keeps coming, a campaign does the follow-up for the whole group:
Create a campaign under Outbound > Campaigns, or ask trax, and pick the shared view of those leads as the audience.
Describe the research you want on each lead. The campaign looks up those facts before any message is prepared.
traxy groups the leads by signal and prepares a personalized LinkedIn and email message variant for each group, using the evidence behind each lead.
Test it on sample leads. You read the research and the drafts, and nothing is sent.
Review the launch: who joins, who is skipped because another unfinished campaign already holds them, and who a finished campaign contacted before. Confirm the senders and the delivery mode.
Launch. Either approve every message in the review queue, or let the approved campaign send on its own. Replies, unsubscribes and hard bounces stop the sequence, and replies land in one inbox.
You can run many campaigns at once on different signals, for example one for competitor engagers and one for people who viewed the profiles of your reps' connected sender accounts. See LinkedIn outbound with traxy for the sending side.
Do it from your AI chat through the traxy MCP
Connect the traxy MCP to Claude, ChatGPT, Codex, Cursor or Grok, and a rep can ask in plain English: "show me today's qualified leads from competitor posts," "what did this lead comment on?" or "send this lead a short LinkedIn message about their comment." From the chat you can list and read leads and the posts behind them, preview and send a one-off message, read and change the Slack settings, routes and daily brief, and draft, test and launch campaigns. The AI shows what it will do and waits for your yes before anything sends or launches.
Reply from Slack
When traxy runs your outreach and you turn on Post lead replies and Reply from Slack, the lead-reply notification in Slack includes a reply box with a Send on LinkedIn or Send email button. Check the recipient and channel before you send, or choose View conversation to open it in traxy.
A setup for a small in-house sales team
Here is one way a B2B team with a few reps and a manager might set this up in one session. Change the views to match how your team splits accounts.
Targeting. One ICP for the whole team. Track your main competitors, two or three creators your buyers follow, your own company page and each rep's own profile. Switch on Profile views.
Views. One shared view per rep, split by territory or segment so they don't overlap, plus All leads for the catch-all.
Routes. One automatic route per rep view to that rep's Slack channel, a catch-all route to a team channel, and a webhook route on All leads to your CRM flow, with a lower threshold than the rep channels.
Slack settings. Repeat-engagement events on. Lead-reply notifications on if traxy runs your outreach.
Daily brief. On for the manager, in Slack, at the start of the working day.
Team rule. Assign before you write. Add a note after every touch.
Campaigns. One campaign per signal you see often, each tested on sample leads and approved before it runs.
Then send the leads already in each view with Leads > Send to, because the automatic routes only cover leads that arrive after you save them.
Limits to know before you rely on alerts
No timing promise. traxy does not promise how soon after someone engages an alert arrives. Treat alerts as a steady feed of reasons to reach out, not a stopwatch.
Only qualified leads and the sources you watch. People below a 50%+ ICP match don't become leads, and activity outside your signals and tracked sources isn't watched.
Tracked profiles cover recent posts. Ongoing monitoring follows the five most recent posts published after the profile was added. Request older posts by URL.
No backfill on new routes. Send the leads already in a view by hand.
Queued is not delivered. A queued result means the request was accepted. Check results for delivered or failed.
A test is not a guarantee. A successful Slack test or webhook test shows that one request worked.
Account-level alerts are not in the docs. traxy shows the company on every lead and groups leads by company, but the docs don't describe an alert for when several people from one account engage. If you need that rule, build it in your webhook flow.
No private-mode profile viewers. LinkedIn doesn't reveal them.
Sending needs connected sender accounts. One-off messages and campaigns go out from the LinkedIn accounts and mailboxes you connect.
If you are comparing alert tools, our LinkedIn monitoring tools comparison puts traxy next to the other tools that send LinkedIn alerts and says where each one fits better.
FAQ
Can traxy alert me when a prospect in my ICP engages on LinkedIn?
Yes. When a person with a 50%+ ICP match engages with posts on your topics or with the people, posts and company pages you track, traxy makes them a lead and a route can send an alert with the post or comment behind it to Slack or a webhook.
Does traxy alert on every LinkedIn activity of my prospects?
No. It alerts on new qualified leads and repeat engagement from existing leads, from the signals and sources your workspace watches. It is not a feed of everything a person does on LinkedIn.
What is a repeat-engagement event?
New activity from a lead who already qualified. It is not counted as a new lead. You can turn it on in the Slack settings, and webhooks receive it as a separate event type.
Can each rep get alerts in their own Slack channel?
Yes. Save a shared view for each rep and add one route per view to that rep's channel. Each route sends one view to one destination.
Can alerts go to our CRM instead of Slack?
Yes, through a webhook, Clay, Zapier or n8n. A webhook sends signed lead events, first delivery and repeat engagement, to any HTTPS endpoint, and your flow writes them to the CRM.
What is in the daily brief?
The daily brief is a scheduled brief from trax, the traxy agent, delivered in traxy or Slack at the time you pick under Settings > Agent. Use it when a rep or manager wants one summary a day.
How fast do alerts arrive?
traxy doesn't make a timing promise. Leads arrive as traxy finds and qualifies them from the sources you watch, and routes send them on from there.
Can a rep reach out straight from the alert?
Yes. Open the lead in traxy and send a one-off LinkedIn message, connection request or email from your connected sender account, or put the lead in a LinkedIn and email campaign that you test and approve before it runs. Replies to your outreach can be answered from Slack when Reply from Slack is on.
Can I do this from Claude or ChatGPT?
Yes. Through the traxy MCP you can list and read leads, preview and send one-off messages, change the Slack settings, routes and daily brief, and run campaigns. The AI waits for your yes before anything sends.
Do alerts show people who viewed my profile in private mode?
No. LinkedIn doesn't reveal private-mode viewers. With Profile views switched on, traxy picks up the profile views of the sender accounts you connect that LinkedIn does show.


