LinkedIn lead integrations: send traxy leads to Slack, your CRM, Clay, n8n, Zapier, webhooks and Meta

TL;DR: traxy can send qualified LinkedIn leads to a Slack channel, a Clay table, a Zapier Zap, an n8n workflow, any HTTPS webhook, a HeyReach campaign or lead list, and a Meta custom audience file, and your CRM (HubSpot, Salesforce or another) gets them through Zapier, n8n, Clay or a webhook. Each integration connects first, then a route decides which saved lead view goes to which destination, with Auto or Manual delivery. If you would rather pull than push, the REST API reads leads, signals and engagements, and the traxy MCP can send a lead to a destination from Claude or ChatGPT.

Last checked: November 13, 2026, against traxy's integrations overview, routes, Slack, Webhook, HeyReach, Meta Ads, Google Calendar and REST quickstart docs. traxy wrote this guide about its own product.

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. You approve a campaign once and then it runs, or you approve every message. Integrations are for the other half of the question: when the lead should also show up somewhere else, such as your CRM, your team's Slack, a Clay table or an ad audience. This guide lists every destination, explains how delivery works, and says what each one is good for.

Where can I send qualified LinkedIn leads from traxy?

To Slack, Clay, Zapier, n8n, a webhook, HeyReach and a Meta Ads audience export, and from there into your CRM or any other tool. Here is the full list from Settings > Integrations, grouped by what you want to do with the lead:

CSV export is the fallback that works with anything: select leads in Leads, choose export, pick the columns and download the file when it is ready. Past exports are under Settings > Exports.

What travels is a qualified lead. traxy finds people from social intent on LinkedIn: what they post, comment on and like, who views your profile, and who engages with the competitors, creators, single posts and company pages you track. A person only counts as a lead with a 50%+ match to your ICP, and every lead carries the post or comment behind it. The event your CRM receives includes engagement fields, so it can say why the person is there, not only who they are.

How delivery works: connections, routes and saved views

Every lead-delivery integration works in two steps: you connect the tool, then you add a route. A successful connection on its own sends nothing.

Step 1: connect the integration

Open Integrations and pick the tool. Slack uses a Slack authorization and a default channel. Webhook, Clay, n8n and Zapier each take a connection name, an HTTPS endpoint and an optional authentication header. HeyReach takes your HeyReach API key. Then send a test: Test trigger for Slack, Send test payload for the webhook-style connections, and check that it arrived at the other end.

Step 2: save the audience as a view

In Leads, add the filters that describe who should go to this destination, then save them as a view. A view updates as leads change, so new people who match it join it on their own. Campaigns and routes use shared views. If you pick a personal view for a route, traxy shares it with the workspace when the route is saved, and a view a route depends on can't be deleted or made personal until you remove that route.

Step 3: add a route

Open the integration's Routes tab and choose Add route. Pick All leads or a saved view, pick the destination (a Slack channel, a webhook endpoint, or a HeyReach campaign or list), and choose a delivery mode:

• Auto: leads that enter the view after you save the route are sent automatically. You set an ICP match threshold for the route, so a destination can ask for a higher fit than the 50% every lead already has.

• Manual: nothing goes until you send it. Select leads in Leads, open Send to and pick the route.

One route connects one audience to one destination. That makes it easy to run one Slack channel per team or per client, one Zap per CRM object, or one HeyReach list per offer, each fed by its own view.

Step 4: send the leads already in the view

An Auto route covers leads that enter the view after you save it. Saving it doesn't send everyone already there. To backfill, select those leads in Leads and use Send to. Bulk select lets you pick all matching leads, a page or the first N.

Step 5: watch the delivery result

A queued result means traxy accepted the request, not that the receiving tool has the lead. Check the delivery state, which separates queued, delivered and failed, and check the receiver too. Lead delivery retries temporary failures, so build your Zap, workflow or code to handle the same event twice. A route can pause itself after repeated failures; fix the endpoint or connection, then resume it from the route menu. Deleting a route stops future routing and leaves the leads already sent where they are.

Slack: alerts, replies and daily summaries

Slack is where most teams first see traxy leads. traxy sends lead alerts, lead-reply notifications, repeat-engagement events and a daily summary to the Slack channels you choose.

• Lead alerts: connect Slack under Integrations > Slack, set a default channel, use Test trigger, then add a route from a view to a channel. Private channels need the traxy app invited first.

• Lead replies: turn on Post lead replies and choose LinkedIn, email or both. With Reply from Slack on, the notification has a reply box with Send on LinkedIn or Send email, and View conversation opens the thread in traxy.

• Repeat engagement: a qualified lead who engages again triggers its own event, separate from a newly delivered lead.

• Daily summary and daily brief: a daily summary from the Slack integration, and trax's scheduled daily brief, which you can deliver in traxy or Slack under Settings > Agent.

If two reps keep working the same lead, give each rep or territory its own view and its own channel, so a lead lands in one place. Agencies use the same pattern with one channel per client.

CRMs: HubSpot, Salesforce and others through Zapier or a webhook

traxy reaches your CRM through Zapier, n8n, Clay or a webhook; the integrations list has no native HubSpot or Salesforce connector. In practice that means one of two paths:

• No code, through Zapier: a Zap catches traxy's lead event and runs a find-or-create step in HubSpot, Salesforce or another CRM Zapier supports. The setup and field mapping are in send qualified LinkedIn leads to HubSpot, Google Sheets or Slack with Zapier, and the Salesforce version, including whether each person should be a Lead or a Contact, is in how to send qualified LinkedIn leads into Salesforce.

• Your own receiver, through a webhook: point a traxy webhook at a service you host and let it write to your CRM, custom CRM or in-house sales tool. Signature checks and repeat events are covered in how to send qualified LinkedIn leads to your CRM or your own app by webhook.

Whichever path you take, three habits keep the CRM clean. De-duplicate on email or LinkedIn profile URL before you create a record. Write the signal and the ICP match into fields the rep can see, so the record says why the lead arrived. And treat the repeat-engagement event as an update to an existing record, not a new lead.

Automation: Clay, n8n, Zapier and webhooks

Webhook, Clay, n8n and Zapier share one model: signed lead events sent to an HTTPS endpoint, controlled by routes. Each request carries X-Traxy-Signature and X-Traxy-Timestamp headers. Follow Payload & help to verify them with the signing secret. There are two event types: one when a qualified lead first reaches the destination, and another when a known lead engages again. Payload samples in the app show the lead, company, contact and engagement fields you can map.

Pick the one that matches where the rest of your workflow lives:

• Clay: leads land as rows in a Clay table or workflow, ready for your own enrichment and scoring. Step by step: how to send LinkedIn leads to Clay automatically.

• Zapier: the widest app catalog and the quickest no-code start.

• n8n: self-hosting and more complex branching, such as splitting events by type before they reach your CRM or Slack.

• Webhook: your own service receives the events directly.

Make the receiver accept requests outside a temporary test session, because some tools only listen while a test is open. If you rotate the signing secret, update the receiver before you rely on later events.

Can I send leads to HeyReach or another outreach tool?

Yes. traxy can send qualified leads into a HeyReach campaign or lead list. Connect HeyReach with your HeyReach API key, open Routes, choose a view, pick Campaign or Lead list and the destination, and choose Auto or Manual. Set up the sequence and senders in HeyReach first, and note that HeyReach delivery needs each lead's LinkedIn profile URL. Sending a lead to HeyReach is not the same as HeyReach sending a message. For other sequencers, use Zapier, n8n or a webhook.

You don't have to hand the lead off at all. traxy runs the LinkedIn and email outreach itself from your own connected sender accounts. A campaign takes a shared view as its audience, researches each lead for the facts you choose, groups leads by signal and prepares a personalized message variant for each group. You test it on sample leads with nothing sent, then the launch review shows who joins, who is skipped (held by another campaign or contacted before), the sender, the steps and the delivery mode. Approve it once and the campaign sends on autopilot, or approve every message in a review queue. Replies, unsubscribes and hard bounces stop the sequence, and replies come into one inbox. You can do both: traxy runs the outreach and a route copies the same leads into the CRM.

Ads and meetings: Meta audiences and Google Calendar

Meta Ads audience export

Under Integrations > Meta Ads, choose New export. traxy builds a value-based audience CSV from your qualified leads: you review the audience size and ICP match threshold, choose saved contact data or an available enrichment option, start the export and download the CSV when it is ready. You then upload it in Meta as a customer list. Meta matches the file on contact details such as email and phone number, separately from traxy, so a finished export means the file is ready, not that every person matched. Only upload contacts you have permission to use that way.

Google Calendar and meetings

Connect Google Calendar, pick the calendars to use, and traxy matches calendar meetings to traxy leads. Outbound > Meetings lists those meetings, and you can record the outcome on each one: Active opportunity, Already a client or Closed won. An event on a connected calendar is not automatically an attributed meeting; the attendees have to match a lead or company.

AI clients and the REST API

Both read your traxy data from outside the app. They suit different jobs.

The traxy MCP

Connect traxy to Claude, ChatGPT, Codex, Cursor, Grok or another MCP client with a one-time sign-in at https://api.traxy.ai/api/v1/mcp (OAuth, no API key). From chat you can list and research your leads, search social intent, and create a Webhook, Clay, n8n or Zapier destination and queue a selected lead for delivery. You can also run campaigns from chat: draft, test on sample leads, launch, manage sequences and senders, and reply in the inbox, with the AI asking for your yes before anything sends or launches. More on the traxy LinkedIn MCP.

The REST API

Create a key under Integrations > API as a workspace admin, include the scopes you need (leads:read for lead reads, leads:contact_read for saved contacts and LinkedIn profile URLs), and call https://api.traxy.ai/api/v1 with the key as a bearer token. The API reads leads, signals, engagements, tracked profiles, analytics and meetings. It doesn't send messages, so use routes to push leads and traxy campaigns for outreach. A key works for one workspace; create a key per workspace. Endpoints, filters and paging are in the LinkedIn leads API guide.

Choose push or pull by who should decide the timing. With a route, leads that enter the view after you save the route are sent automatically. The API lets your system pull on its own schedule, which suits a data warehouse or a nightly sync.

Limits to know before you rely on an integration

• Connecting a tool sends nothing until a route exists, or until you use Send to.

• Auto routes only cover leads that enter the view after you save the route.

• Queued is not delivered. Check the delivery state and the receiving tool.

• Deliveries can repeat after a retry, so de-duplicate downstream.

• A connected calendar event is not an attributed meeting until it matches a lead.

• A Meta export is a file; matching happens in Meta.

• Connection changes, routes and API keys can need different roles. Ask an admin when an action is missing.

• Disconnecting an integration stops its future deliveries and can stop all its routes. It doesn't delete what the other tool already received.

FAQ

Does traxy connect to HubSpot, Salesforce or Attio?

Through Zapier, n8n, Clay or a webhook, not a native connector. Route a saved view to a Zap, workflow or receiver that creates or updates the record in your CRM.

Is there an API or webhook to push leads into my CRM or my own outreach system?

Yes, both. With a webhook route, leads that enter the view after you save the route are sent automatically to your HTTPS endpoint as signed lead events. The REST API lets your system read leads, signals and engagements when it wants them.

Can different leads go to different places?

Yes. Each route connects one view to one destination, so save a view per team, signal, client or offer and give each its own route.

Do I need an integration to reach out to the leads?

No. traxy runs LinkedIn and email outreach from your own connected sender accounts. You test the campaign on sample leads and approve it, then it runs on autopilot, or you approve every message. Integrations are for when the lead should also land in another tool.

Will old leads be sent when I add a route?

No. An Auto route covers new leads entering the view. Send the ones already there from Leads with Send to.

Can I set up delivery from Claude or ChatGPT?

Yes. With the traxy MCP connected, your AI can create a Webhook, Clay, n8n or Zapier destination and queue a selected lead for it, after you confirm.

What does each lead event include?

The lead, company, contact and engagement fields available for that lead. Contact fields depend on what is saved on the lead; check the payload sample under Payload & help before you build the mapping.

Does the Slack integration replace the traxy inbox?

No. Slack can post lead replies and, with Reply from Slack on, lets you answer on LinkedIn or by email from the notification. The full conversation stays in the traxy inbox, one click away with View conversation.

Next step

Save one view of the leads you care about most, connect the tool where your team already works, add a Manual route and send five leads with Send to. Check how they land, then switch the route to Auto. When you want traxy to run the outreach to the same leads, start a campaign from that view on LinkedIn outbound.