Integrations

How to use a LinkedIn intent tool with the LinkedIn automation tool you already use

Keep your LinkedIn automation tool and feed it high intent leads from traxy by CSV, webhook, Zapier or n8n, or move sending into traxy. Step by step.

By the traxy teamPublished Nov 13, 202615 min read

TL;DR: Yes. Use traxy as the lead source and keep your LinkedIn automation tool as the sender. traxy finds high intent leads from LinkedIn social intent (posts, comments, likes, profile views and engagers with the profiles, posts and company pages you track), keeps only people with a 50%+ match to your ICP, and shows the post or comment behind every lead. You hand those leads to your current tool by CSV export, or by a route to a webhook, Zapier or n8n. If you would rather drop the handoff, traxy campaigns research each lead and run LinkedIn and email outreach from your own connected accounts after you approve the launch. traxy wrote this guide; we make the product.

Last checked: November 13, 2026, against traxy's exports, routes, Webhook, Zapier, n8n, saved views, review and launch and Do not contact docs. Third-party automation tools are described generically; check your own tool's import, webhook or Zapier options in its help center before you build.

Can I use a LinkedIn intent tool alongside the LinkedIn automation tool I already use?

Yes. The intent tool decides who to contact and why, and the automation tool you already pay for keeps doing the sending, so you connect the two with a CSV export or a webhook, Zapier or n8n route and leave your campaigns, templates and sender setup where they are.

This is one of the most common questions on sales calls. One buyer put it plainly: "What I'm trying to figure out is, does this thing fit in my stack." Teams that already run a LinkedIn automation tool usually want a better list, not a second sender. That is a fair way to start with traxy.

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. Autopilot here means you test a campaign on sample leads and approve the launch once, then it sends on its own from your connected accounts, or you approve every message in a review queue. You don't have to use the second half. You can start with the first half only and feed your existing tool.

The whole setup, in order:

Set who fits. Enter your website, and traxy drafts your lead criteria (ICP) and the signals to watch. Fix anything that is off.
Let traxy find the people. It qualifies people who post, comment on or like posts about the problem you solve, people who engage with the profiles, posts and company pages you track, and your profile viewers.
Save the audience. Filter the leads you want to hand off and save them as a shared view.
Hand it off. Export the view as a CSV, or add a route from the view to a webhook, Zapier or n8n.
Keep one sender per lead. Decide which leads your tool contacts and which stay in traxy, so nobody hears from both.

Each step is covered below, with what you set up, what traxy does and the limits the docs spell out.

Lead source vs sender: which job each tool does

A lead source answers "who should we contact, and why now?" A sender answers "how do we reach them, and when?" Most LinkedIn automation tools are senders: they work through a list you bring, such as a search export, a CSV or the people who reacted to a post. traxy is a lead source first, and it can also be the sender.

Job	traxy as the lead source	Your current automation tool
Who to contact	Finds people from LinkedIn social intent and from search over 71M+ scanned LinkedIn likes, posts and comments	Works from the list you import or build in it
Why now	Every lead shows the post, comment, like or repost that put them on the list, with a Warm, Related or Activity label	Usually whatever columns you import
Fit check	Only people with a 50%+ ICP match become leads	Depends on the tool and the filters you set
Contact data	Email and phone lookup per lead, plus Auto-Enrich for new leads	Depends on the tool
Sending	Optional: LinkedIn and email campaigns from your own connected accounts	Your existing sequences, templates and accounts
Replies	One inbox across LinkedIn and email for traxy campaigns	Your tool's own inbox

Where the leads come from matters for the handoff, because the reason someone is on the list is what makes the first message worth sending. traxy has three sources:

Signals. You describe the problems, topics and situations that make someone relevant, and traxy qualifies people who post, comment on or like posts about them.
Tracking. Follow people (competitors, creators, your own team, investors), single posts by URL and company pages by domain, and traxy qualifies whoever engages. There are no tracking limits on profiles, posts or company pages. Profile views can also become leads: a Profile views switch sits in Targeting > Signals.
Social intent search. Describe the person and the need in plain English and search 71M+ scanned LinkedIn likes, posts and comments.

Fit is checked when a person is found, not after they reach your sender. For a closer look at why that order matters, see LinkedIn automation tools that only contact people who fit your ICP.

Getting traxy leads into your tool: export, webhook, Zapier or n8n

Save the leads you want as a shared view, then either export it as a CSV and import the file into your tool, or add a route that sends each new lead in the view to a webhook, Zapier or n8n automatically. The CSV is the quickest test. A route keeps new leads flowing without anyone exporting by hand.

Step 1: Save the audience as a shared view

Open Leads, add the filters for the people, companies, signals or workflow state you want, review the matches, then choose Save as new view and pick its sharing setting (saved views). A view built from table filters updates as matching leads and their data change. Campaigns and routes use shared views, and picking a personal view for a route shares it when you save the route.

One detail to know: when you ask trax to save a search that depends on text, topics or a custom ICP score range, it saves a fixed audience of the leads matched at that time, and new matching people don't join it. For an ongoing handoff, build the view from table filters.

Option A: CSV export

In Leads, open the view and apply any extra filters.
Select the leads. Use the option to select all matching leads when you want the whole filtered result, then check the selected count.
Choose the columns and any enrichment options.
Confirm the export, then download the file when it is ready. Settings > Exports keeps the history.

Before you import, check which column your automation tool matches people on. Many tools need the LinkedIn profile URL, so include that column. Exporting does not move leads to Done unless you choose that option, which matters for the double-outreach section below (exports). A CSV is a snapshot: people who qualify tomorrow are not in today's file.

Option B: Webhook route

If your automation tool, CRM or own system accepts an HTTPS webhook or has an API you can call from a small receiver, use traxy's Webhook integration. Open Integrations > Webhook, enter a name and the HTTPS endpoint, add an authentication header if the receiver needs one, then use Send test payload and check that it arrived (Webhook).

traxy sends signed lead events with X-Traxy-Signature and X-Traxy-Timestamp headers. There are two kinds: a first-delivery event when a qualified lead first reaches the destination, and a repeat-engagement event when a known lead engages again. Treat them differently. A repeat event belongs on the existing contact as new activity, not as a new person in a sequence.

Option C: Zapier

If your automation tool has a Zapier app with an action that adds a person to a campaign or list, Zapier is the shortest path. Create a Zap that starts with a Webhooks by Zapier trigger, paste its URL into Integrations > Zapier, send a test payload, then map the fields to your tool's action (Zapier). The full walkthrough is in how to send qualified LinkedIn leads to other apps with Zapier.

Option D: n8n

If you self-host or want branching (for example, one path for Warm leads and another for Related leads), connect traxy's n8n integration to an n8n Webhook node. In the workflow, verify the signature, de-duplicate, branch on the event type and call your automation tool's API or webhook (n8n). See the n8n LinkedIn lead workflow for node-by-node steps.

Step 2: Add the route

A connection alone sends nothing. A route connects one audience to one destination (routes):

Open the connection's Routes tab and select Add route.
Choose All leads or a saved view.
Select the destination endpoint.
Choose Auto or Manual delivery. For Auto, review the ICP match threshold.
Review and save.

The route threshold controls what reaches that destination; it doesn't change which people qualify as leads. Automatic routes apply to leads entering the view from that point onward, so saving a route does not send the leads already in the view. To send those, select them in Leads, open Send to and choose the route.

Step 3: Test with a few leads first

Start with a Manual route. Send three leads with Send to, open them in your automation tool and check that the name, profile URL, company and the signal fields landed where your templates expect them. A queued result means traxy accepted the request for delivery, so check the delivery result too. Switch the route to Auto once the mapping is right. If a route fails repeatedly it can pause; fix the receiving side before you resume it.

You can also do this from your AI chat. Through the traxy MCP in Claude, ChatGPT, Cursor, Codex or Grok, you can create a Webhook, Clay, n8n or Zapier destination and queue a selected lead for delivery.

Keeping the research and the signal with each lead

The signal can travel with the lead: map the engagement fields from the payload (or the matching CSV columns) into your tool's custom fields, so every message can mention what the person posted or commented on. Research on each lead runs inside traxy campaigns, so if the research is what makes the message work, prepare the message in traxy too.

Here's what each lead carries and how to keep it:

The source activity. Each lead shows the post, comment, like or repost that put them on your list, on its Signals tab. Webhook, Zapier and n8n events include lead, company, contact and engagement fields; use the payload sample under Payload & help to see the exact field names in your workspace rather than guessing them.
The label and the fit. Leads are labeled Warm, Related, Activity or ICP match by how strong the evidence is, and each has an ICP match score. Bring these across if your tool lets you split a list, so Warm leads get the most specific opener.
Contact details. traxy can look up a verified work email and a phone number for a lead, and Auto-Enrich looks up contact data for newly qualified leads (it doesn't backfill old ones). If your current tool also sends email, export or map those fields.
Research on each lead. A traxy campaign researches each lead for the facts you ask for before any message is prepared. A research-only campaign records findings without sending anything. When a required fact isn't found, the lead stays in traxy, and in the campaign you can choose to skip it.

Check whether the research findings you want appear among your export columns or payload fields before you plan around them. If they don't, that is a sign the message belongs in traxy, where the research, the grouping by signal and the draft sit on the same lead.

In your automation tool, write the template around the signal fields. A plain structure works: mention the post or topic the person engaged with, say why it connects to what you do, and ask one easy question. A message that names the post gives the reader a reason to answer; a message that only uses their first name reads like any bought list.

When to move sending into traxy

Move sending into traxy when the research on each lead is the reason you are qualifying them, when you want LinkedIn and email in one sequence with one inbox, or when the handoff between two tools is the part that keeps breaking. Keep your current tool when your team's campaigns, templates, seats and reporting already live there and the list was the only gap.

Sending from traxy looks like this (LinkedIn outbound with traxy):

Connect your senders. Add your LinkedIn accounts and mailboxes under Outbound > Sender accounts, with limits, active hours, ramp-up and email signatures. Sending needs connected sender accounts.
Create a campaign on a shared view. In Outbound > Campaigns, or by asking trax, give the audience, the offer and the research you need on each lead.
Let traxy group and prepare. Leads are grouped by signal, and each group gets its own personalized message variant built from the evidence. traxy prepares the drafts; LinkedIn and email can run in one campaign.
Test on sample leads. The test runs the plan on a few leads so you can check the research and drafts. Nothing is sent.
Review the launch. Before launch you see who joins, who is skipped because another campaign holds them or a completed campaign contacted them before, the sender, the steps and the delivery mode (review and launch).
Pick the delivery mode. Approve every message in a review queue, or let the approved campaign send on its own. That second choice is the autopilot: it runs because you approved it.
Work the replies. Replies, unsubscribes and hard bounces stop the sequence. The inbox keeps one conversation per lead across LinkedIn and email, and you can pause a lead's sequence to take over.

You can run many campaigns at once on different signals. Campaigns run in priority order, so one lead never gets two traxy campaigns at once. You can run all of this by hand in the app, through trax, or from Claude, ChatGPT, Codex, Cursor or Grok through the traxy MCP, where the AI asks for your yes in chat before anything sends or launches.

You don't have to switch everything at once. A common middle path is to keep your existing tool on the lists it already runs and start one traxy campaign on one signal, such as people engaging with a competitor's posts. If you want a fair read, send the same message to a list from each source and compare replies. For a tool-specific version of this decision, see traxy + Waalaxy agency workflows, and for every comparison we have published, traxy alternatives and comparisons.

Avoiding double outreach across two tools

Give every lead one sender. Split your leads by view so one audience goes to your automation tool and a different one stays in traxy, and tell traxy who your other tool has already contacted with a Do not contact upload. traxy's own checks only see traxy's campaigns, so the split is your job.

Split by view. Route one shared view to your automation tool and use a different view for traxy campaigns. Don't point both at the same audience. A simple split is by signal (for example, Warm leads in traxy with research, Related leads in your tool) or by owner.
Mark what you hand off. When you export, choose the option to move the exported leads to Done, so they drop out of active views. Assign owners, tags and notes so teammates don't double up.
Upload your other tool's contacted list. Under Settings > Do not contact, upload a CSV with kind,value columns (EMAIL or LINKEDIN) for people your current tool is already messaging. That stops traxy outreach to them (Do not contact).
Keep existing customers out. Add their domains to the Blocklist so they never come back as leads.
Read the launch review. It lists leads held by another unfinished traxy campaign and people a completed traxy campaign contacted before. It doesn't know what your other tool sent, which is why step 3 matters.
De-duplicate on the receiving side. Delivery can retry temporary failures and known leads send repeat-engagement events, so match on the LinkedIn profile URL or email before adding anyone to a sequence.
Watch shared LinkedIn accounts. If both tools send from the same LinkedIn account, traxy's sender limits only cover what traxy sends. Set the other tool's limits so the combined daily activity stays where you want it.
Close the loop on replies. A reply in traxy stops the traxy sequence. If someone replies to your other tool, add them to Do not contact in traxy, or mark them Done, so they don't get a second first message.

FAQ

Do I have to replace my LinkedIn automation tool to use traxy?

No. You can use traxy only as the lead source and hand qualified leads to your current tool by CSV export or a webhook, Zapier or n8n route. You can move sending into traxy later, one campaign at a time, or never.

How do traxy leads get into my automation tool?

Two ways. Export a saved view as a CSV and import it, or add a route from the view to a webhook, Zapier or n8n endpoint, which sends each new lead entering the view as a signed event. traxy can also send leads to Clay and Slack. Which of these your tool can receive depends on its own import, webhook and Zapier options.

Will leads already in my view be sent when I add a route?

No. Automatic routes apply to leads that enter the view after you save the route. To send the leads already there, select them in Leads, open Send to and choose the route.

Can my automation tool see why each lead was picked?

Yes, if you map it. Each lead carries the post, comment, like or repost behind it, and the events include engagement fields. Map them into your tool's custom fields and use them in the template. Research on each lead runs in traxy campaigns, so check which findings your export or payload includes.

Which leads does traxy pass on?

Only qualified leads: people found from LinkedIn social intent with a 50%+ ICP match. A route can set its own, higher ICP match threshold for one destination, which narrows what that tool receives without changing who qualifies.

Can traxy send the outreach itself?

Yes. traxy campaigns run LinkedIn and email outreach from your own connected accounts, with optional research on each lead, a test on sample leads with nothing sent and a launch review. You approve every message, or approve the campaign once and it sends on its own. See LinkedIn outbound.

How do I stop the same person hearing from both tools?

Use different views for each tool, move exported leads to Done, and upload your other tool's contacted list to traxy's Do not contact as a CSV. Then de-duplicate on the LinkedIn profile URL wherever leads arrive.

Can I set this up from Claude or ChatGPT?

Yes. With the traxy MCP connected, you can create a Webhook, Clay, n8n or Zapier destination and queue a lead for delivery from your AI chat. You can also run traxy campaigns from there, and the AI waits for your yes before anything sends or launches.

Back to all articles