--- title: "Send LinkedIn Leads to Attio: Zapier, n8n or Webhook | traxy" description: "How to send qualified LinkedIn leads from traxy to Attio with Zapier, n8n or a webhook: routes, field mapping, matching attributes and no duplicates." canonical: "https://traxy.ai/blog/send-linkedin-leads-to-attio" last_updated: "2026-11-13" --- # Send LinkedIn Leads to Attio: Zapier, n8n or Webhook | traxy > How to send qualified LinkedIn leads from traxy to Attio with Zapier, n8n or a webhook: routes, field mapping, matching attributes and no duplicates. [Home](https://traxy.ai/) [Blog](https://traxy.ai/blog) [LinkedIn Lead Generation](https://traxy.ai/blog/topics/linkedin-lead-generation) Integrations # How to send qualified LinkedIn leads to Attio with Zapier, n8n or a webhook How to send qualified LinkedIn leads from traxy to Attio with Zapier, n8n or a webhook: routes, field mapping, matching attributes and no duplicates. By the traxy teamPublished Nov 13, 202613 min read ![How to send qualified LinkedIn leads to Attio (Zapier, n8n or webhook) — traxy blog](https://traxy.ai/assets/blog-covers/send-linkedin-leads-to-attio.jpg) **In this article**[How do I send qualified LinkedIn leads to Attio?](https://traxy.ai/blog/send-linkedin-leads-to-attio#how-do-i-send-qualified-linkedin-leads-to-attio) [Is there a native Attio integration?](https://traxy.ai/blog/send-linkedin-leads-to-attio#is-there-a-native-attio-integration) [How does it work, from a LinkedIn comment to an Attio record?](https://traxy.ai/blog/send-linkedin-leads-to-attio#how-does-it-work-from-a-linkedin-comment-to-an-attio-record) [Before you start: decide what the Attio record should be](https://traxy.ai/blog/send-linkedin-leads-to-attio#before-you-start-decide-what-the-attio-record-should-be) [Option 1: Zapier](https://traxy.ai/blog/send-linkedin-leads-to-attio#option-1-zapier) [Option 2: n8n or a webhook](https://traxy.ai/blog/send-linkedin-leads-to-attio#option-2-n8n-or-a-webhook) [Which fields to map, and how to avoid duplicates](https://traxy.ai/blog/send-linkedin-leads-to-attio#which-fields-to-map-and-how-to-avoid-duplicates) [Do you still need outreach once the leads are in Attio?](https://traxy.ai/blog/send-linkedin-leads-to-attio#do-you-still-need-outreach-once-leads-are-in-attio) [Common problems](https://traxy.ai/blog/send-linkedin-leads-to-attio#common-problems) [FAQ](https://traxy.ai/blog/send-linkedin-leads-to-attio#faq) [Next step](https://traxy.ai/blog/send-linkedin-leads-to-attio#next-step) [Open product docs](https://docs.traxy.ai/) **TL;DR: traxy has no native Attio integration, so qualified LinkedIn leads reach Attio through Zapier, n8n or a signed webhook. You save a lead view in traxy, connect it to the receiver with a route, and let Attio create or update a person or company record that matches on a unique attribute such as email address or domain.** Last checked: November 13, 2026, against traxy's [integrations overview](https://docs.traxy.ai/integrations/overview) , [webhook](https://docs.traxy.ai/integrations/webhook) , [Zapier](https://docs.traxy.ai/integrations/zapier) , [n8n](https://docs.traxy.ai/integrations/n8n) and [routes](https://docs.traxy.ai/integrations/routes) docs, and Attio's own help pages linked in each section (checked November 2026). ## How do I send qualified LinkedIn leads to Attio? Connect traxy to Attio through Zapier, n8n or a webhook, then add a route from a saved lead view to that connection. Each new qualified lead arrives as a signed event, and an Attio action or workflow block turns it into a record without creating duplicates. The short version, in five steps: 1. **Find and qualify the leads in traxy.** traxy finds high intent leads from LinkedIn social activity: people who post, comment on or like posts about the problem you solve, people who engage with competitors' and creators' posts you track, and people you find by searching 71M+ scanned LinkedIn likes, posts and comments in [social intent search](https://traxy.ai/social-intent-search) . A person only counts as a lead with a 50%+ match to your ICP, and every lead shows the post or comment behind it. 2. **Save the leads you want in Attio as a view.** In **Leads**, add filters and save them as a view. Routes use shared views, and a view updates as leads change. 3. **Set up the receiver.** A Zap with a Webhooks by Zapier trigger, an Attio workflow that starts from a Webhook received trigger, or an active n8n workflow. 4. **Connect it in traxy and send a test.** **Integrations** > Zapier, n8n or Webhook, enter the HTTPS endpoint, save, then use **Send test payload**. 5. **Add the route.** Open **Routes**, connect All leads or the saved view to the destination, and choose Auto or Manual delivery. The rest of this guide covers each step, the fields worth mapping, and how to keep Attio free of duplicates when the same person engages twice. If you are still choosing a CRM, [the best LinkedIn CRM integrations in 2026](https://traxy.ai/blog/best-linkedin-crm-integrations-2026) compares Attio with HubSpot, Salesforce and others. ## Is there a native Attio integration? No. traxy's [integrations overview](https://docs.traxy.ai/integrations/overview) lists connections such as Slack, Webhook, Clay, n8n, Zapier, Google Calendar, Meta Ads, the REST API and AI clients, and no Attio connector. That doesn't block you, because Attio documents two ways to receive outside data that fit traxy's lead events: - **Attio workflows** can start from a **Webhook received** trigger, which "starts a workflow when an external application sends a request to a provided URL" ([Attio workflows block library](https://attio.com/help/reference/automations/workflows/workflows-block-library) , checked November 2026). - **Attio's Zapier app** is listed on Attio's site as an official app built by Attio ([Attio Zapier app](https://attio.com/apps/zapier) , checked November 2026), with actions that create or update records. n8n works too, but the Attio side is less packaged: Attio's [app directory](https://attio.com/apps) lists no n8n app (checked November 2026), so an n8n workflow writes to Attio through Attio's REST API. More on that below. Here is how the three paths compare: What differs Zapier Attio workflow (webhook) n8n Setup No code for the basic flow No code; built inside Attio Low code; you host or use n8n cloud Attio write Create or Update Record action Create or update record block Attio REST API (upsert by a matching attribute) Verifying traxy's signature Possible with Catch Raw Hook and a code step Not described in Attio's block docs In a code node Cost on the Attio or Zapier side Needs a paid Zapier plan: Zapier's [webhook trigger guide](https://help.zapier.com/hc/en-us/articles/8496288690317-Trigger-Zaps-from-webhooks) marks Free as not included and lists Professional, Team and Enterprise (checked November 2026) Each run uses Attio workspace credits Your n8n plan or hosting Best for Small teams, quickest start Teams that live in Attio Custom logic, branching, other tools in the same flow Sources for the table: [Zapier's webhook trigger guide](https://help.zapier.com/hc/en-us/articles/8496288690317-Trigger-Zaps-from-webhooks) and [Attio's overview of workflows](https://attio.com/help/reference/automations/workflows/overview-of-workflows) , both checked November 2026. ## How does it work, from a LinkedIn comment to an Attio record? Every path uses the same traxy side. Knowing it makes the Attio setup much easier to debug. 1. **A lead qualifies.** traxy finds a person through a signal (post engagement, Tracking, profile views or a search), checks them against your lead criteria, and keeps them only at a 50%+ ICP match. Each lead is labeled Warm, Related or Activity and shows the source activity. 2. **The lead enters a view.** If it matches the filters of the view your route uses, it becomes eligible for delivery. 3. **The route decides.** On **Auto**, the route sends leads that enter the view from then on, if they meet the route's ICP match threshold. On **Manual**, nothing goes until you select leads and use **Leads > Send to**. Saving a route does not send the leads already in the view, so send those once by hand ([routes docs](https://docs.traxy.ai/integrations/routes) ). 4. **traxy sends a signed event.** Each request carries **X-Traxy-Signature** and **X-Traxy-Timestamp** headers, and **Payload & help** explains how to verify them with the signing secret. There are first-delivery events for new qualified leads and repeat-engagement events when a known lead engages again ([webhook docs](https://docs.traxy.ai/integrations/webhook) ). 5. **Attio matches, then creates or updates.** Your Zap, workflow or n8n flow looks for an existing record by a unique attribute and only creates one when nothing matches. Two traxy details matter for Attio. Delivery can retry temporary failures, so the Attio step must be safe to run twice for the same lead. And a route can pause after repeated failures; fix the URL, authentication or workflow in Attio before you resume it from the route menu. ## Before you start: decide what the Attio record should be Settle three things before you map a single field: - **People, Companies or both.** Most teams create or update the person and the company, so the account view in Attio shows everyone who engaged from that company. - **The matching attribute.** Attio's Create or Update Record action finds the record "using a matching attribute, which must be a unique attribute", and you must always include a value for it. Attio's own examples are email address for people and domain for companies ([Attio Zapier triggers and actions](https://attio.com/help/reference/apps/zapier-app/popular-zapier-triggers-and-actions) , checked November 2026). - **Where reps will see the lead.** If your team works from an Attio list, plan a second step that adds the record to that list. The matching attribute is the decision that trips people up. A lead found from a LinkedIn comment may not have a work email yet. Attio's docs say to use Create Record for people without email addresses, and that Create Record fails if it conflicts with an existing unique value. You have three ways to handle it: look up the email in traxy first (an email lookup on the lead, or Auto-Enrich for newly qualified leads, which doesn't backfill old ones), match the company by domain and attach a note instead of a new person, or use Attio's Find Records step on another attribute you store before creating anything. ## Option 1: Zapier Zapier is the fastest path if you don't want to touch code. It takes about five steps on the traxy side and two Attio actions. 1. In Zapier, create a Zap with **Webhooks by Zapier** as the trigger. Choose **Catch Hook** for parsed fields, or **Catch Raw Hook** if you plan to verify traxy's signature, because Zapier says the raw option also includes headers. Copy the webhook URL from the **Test** tab ([Zapier webhook trigger guide](https://help.zapier.com/hc/en-us/articles/8496288690317-Trigger-Zaps-from-webhooks) , checked November 2026). 2. In traxy, open **Integrations > Zapier**, enter a connection name and the URL, add an authentication header only if your receiver needs one, and save. 3. Open **Settings** to review the triggers and **Payload & help**, then select **Send test payload**. A test sends one immediate request, so Zapier now has a sample to map from. 4. Connect Attio in Zapier: **App Connections > + Add connection**, select Attio and add an Attio API key. Attio recommends setting all of the key's scopes to Read-write for Zapier ([Connect Attio and Zapier](https://attio.com/help/reference/apps/zapier-app/connect-attio-and-zapier) , checked November 2026). 5. Add Attio's **Create or Update Record** action on People with email address as the matching attribute, or on Companies with domain. It "updates a matching record, or creates a new record if no match exists". 6. Optional: add **Create or Update List Entry by Parent Record** to put the person on a list. It finds the record's entry in the list or creates one, so a person isn't added twice. Add **Create Note** if you want the LinkedIn activity as a note on the record. 7. Turn the Zap on. Back in traxy, open **Routes**, add a route from your saved view to the Zapier connection, and choose Auto or Manual. If a lead may arrive without an email, put a Zapier filter or path before the Attio step, so leads without one go to Find Records or a company-only update instead of failing. For a longer walkthrough of the traxy side of Zapier, including HubSpot, Sheets and Slack examples, see [how to send qualified LinkedIn leads with Zapier](https://traxy.ai/blog/linkedin-leads-zapier) . ## Option 2: n8n or a webhook Use this path when you want the logic inside Attio itself, or when the flow needs branching that a simple Zap makes awkward. ### A webhook into an Attio workflow 1. In Attio, create a workflow that starts with the **Webhook received** trigger and copy its Webhook URL. Attio's docs say requests should set Content-Type: application/json. 2. Add a **Parse JSON** block after the trigger. Attio says to follow the trigger with it "to extract structured data from the request body and use it in later blocks". 3. Add a **Create or update record** block on People or Companies and select the matching attribute. Attio notes that if more than one record matches, the block fails and no record is updated, so clean up existing duplicates first. 4. Optional: add **Add record to list** to drop the record onto your team's list. 5. Publish the workflow so it accepts requests outside a test session. Attio's [overview of workflows](https://attio.com/help/reference/automations/workflows/overview-of-workflows) says workflows are available on all plans and each run uses workspace credits (checked November 2026). 6. In traxy, open **Integrations > Webhook**, enter a connection name and the Attio URL, save, use **Send test payload**, check the run in Attio, then add the route. All of the Attio blocks above are described in the [Attio workflows block library](https://attio.com/help/reference/automations/workflows/workflows-block-library) (checked November 2026). That page doesn't describe signature checks on the webhook trigger. If you need to verify X-Traxy-Signature before anything is written, use Zapier with Catch Raw Hook, n8n, or your own receiver. ### n8n with the Attio REST API 1. In n8n, create a workflow that starts with a webhook receiver and copy its HTTPS URL. traxy sends events to an active n8n workflow, so use a URL that works outside a temporary test session. 2. In traxy, open **Integrations > n8n**, enter the URL, save, and use **Send test payload**. 3. Optionally verify **X-Traxy-Signature** and **X-Traxy-Timestamp** in a code node, using the signing secret from **Payload & help**. 4. Add an HTTP request to Attio's [Upsert a record endpoint](https://docs.attio.com/rest-api/endpoint-reference/records/upsert-a-record) (PUT /v2/objects/{object}/records) with a matching\_attribute query parameter. Attio says a value that matches more than one record is rejected, and the call needs the record\_permission:read-write and object\_configuration:read scopes (checked November 2026). 5. Activate the workflow, then add the route in traxy. The n8n side, with branching by signal and Slack alerts, is covered in [how to build an n8n workflow for LinkedIn leads](https://traxy.ai/blog/n8n-linkedin-lead-workflow) . If you'd rather host your own receiver, [how to send qualified LinkedIn leads to your CRM by webhook](https://traxy.ai/blog/send-linkedin-leads-to-crm-webhook) covers signature checks and repeat events in code. ## Which fields to map, and how to avoid duplicates Take field names from the payload sample in **Payload & help**; map these if your sample includes them: traxy payload area Attio attribute (slug) Notes Work email, if saved Email addresses (email\_addresses) on People Unique, so use it as the matching attribute First and last name Name (name) on People Map as is Title Job title (job\_title) on People Map as is Company domain Domains (domains) on Companies Unique, so use it as the matching attribute Company name Name (name) on Companies Map as is LinkedIn profile URL LinkedIn (linkedin) on People A text attribute, not unique; good for Find Records Signal summary and label A text attribute or a note Why the lead arrived ICP match A number attribute Lets reps sort and filter Event type A select attribute or the note title First delivery vs repeat engagement Attio lists Email addresses as the only unique standard attribute on People and Domains as the only one on Companies ([People](https://docs.attio.com/docs/standard-objects/standard-objects-people) and [Companies](https://docs.attio.com/docs/standard-objects/standard-objects-companies) standard objects, checked November 2026). The signal, ICP match and event type need custom attributes you create, or a note. Keep the signal text. A record with only a name and title looks like any bought list, and the rep has nothing to open with. To keep Attio clean: - **Always upsert, never plain create.** Use Create or Update Record (Zapier), Create or update record (workflow) or the Upsert a record endpoint (API). traxy can retry a delivery, and a plain create step would make a second record. - **Treat repeat engagement as an update.** A repeat-engagement event is the same person engaging again. Add a note or update a "last signal" attribute rather than creating anything new. - **Fix existing duplicates first.** Every Attio path fails when more than one record matches the value. - **Use one route per purpose.** Each route connects one view to one destination, so a view per team, signal or offer keeps different leads going to different Attio lists. ## Do you still need outreach once the leads are in Attio? Only if you want traxy to run it, and most teams that use the Attio route use both. traxy runs your entire LinkedIn GTM end to end: it finds high intent leads from social intent, enriches and researches each one, and runs relevant, personalized [LinkedIn and email outreach](https://traxy.ai/linkedin-outbound) to them on autopilot once you approve the campaign, or you approve every message. The outreach half works from the same shared views your route uses: - **Campaigns** take a shared view as the audience, run research on each lead for the facts you choose, group leads by signal and give each group its own personalized message variant. traxy prepares the drafts; you review them. - **Test before launch.** You test 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 and the steps. - **Your own accounts.** Messages go out from the LinkedIn accounts and mailboxes you connect as senders. Replies, unsubscribes and hard bounces stop the sequence, and replies land in one inbox. So Attio stays your system of record, and traxy does the finding and the outreach. You can run many campaigns at once on different signals, by hand in the app, through trax (the traxy agent), or through the traxy MCP from Claude, ChatGPT, Cursor, Codex or Grok, with a yes in chat before anything sends. ## Common problems - **The test payload never arrives.** The Attio workflow or n8n workflow isn't published or active, or you copied a test URL. traxy's docs ask for a receiver that accepts requests outside a temporary test session. - **The route paused.** Routes can pause after repeated failures. Fix the expired URL, authentication failure or unavailable workflow, then resume from the route menu. - **Old leads didn't show up in Attio.** Auto routes only send leads that enter the view after you save the route. Select the existing leads and use **Send to**. - **The Attio step fails on some leads.** Usually the matching attribute is empty (no email) or matches more than one record. Add a filter before the step and clean up duplicates. - **Too many low-fit records.** Raise the route's ICP match threshold or tighten the view's filters. The threshold only controls delivery to that destination; it doesn't change who qualifies in traxy. ## FAQ ### Does traxy have a native Attio integration? No. traxy's integrations list has no Attio connector. Leads reach Attio through Zapier, n8n or a signed webhook into an Attio workflow. ### Which is easier, Zapier or an Attio workflow? Both are no code. Zapier is quicker if your team already uses it and you want to verify signatures (Catch Raw Hook plus a code step). An Attio workflow keeps everything inside Attio, with each run using Attio workspace credits. ### Can I send only some leads to Attio? Yes. Save a view with the filters you want and route only that view, or use a Manual route and pick leads with **Send to**. You can also set an ICP match threshold on an Auto route. ### Will the same person be created twice? Not if every Attio step upserts on a unique attribute such as email address or domain. traxy can retry deliveries and sends repeat-engagement events, so a plain create step would cause duplicates. ### What if a lead has no email address? Attio's Create or Update Record needs a value for the matching attribute. Look up the email in traxy first, update the company by domain instead, or use Find Records on another attribute before creating the person. ### Can the leads I send to Attio also go into outreach? Yes. Campaigns and routes both use shared views, so the same view can feed Attio and a traxy LinkedIn and email campaign. The campaign sends from your connected sender accounts once you approve it, or you approve every message. ### Does this work the same for HubSpot or Salesforce? The traxy side is identical: a connection, a test payload and a route. The CRM side differs; see [how to send qualified LinkedIn leads into Salesforce](https://traxy.ai/blog/linkedin-leads-to-salesforce) and [where you can send qualified LinkedIn leads from traxy](https://traxy.ai/blog/linkedin-lead-integrations) . ## Next step Pick the path that matches your stack, save one view of the leads you want in Attio, and send a test payload before you turn on an Auto route. When you want traxy to run the outreach too, start with [LinkedIn outbound with traxy](https://traxy.ai/linkedin-outbound) . [Back to all articles](https://traxy.ai/blog) ## Keep reading [All LinkedIn Lead Generation guides](https://traxy.ai/blog/topics/linkedin-lead-generation) [Lead generation12 min read ## LinkedIn Lead Generation (2026): What It Is, Strategy, Tips and Tools for B2B What LinkedIn lead generation is, a 7-step B2B strategy, the 5 main tactics, tips, tools and metrics, plus every LinkedIn lead generation guide we publish. Updated Nov 12, 2026Read article](https://traxy.ai/blog/linkedin-lead-generation-guide-2026) [Lead generation10 min read ## How to extract comments from a LinkedIn post, and keep only the commenters who fit your ICP Four ways to extract comments from a LinkedIn post, what each returns and risks, and how to keep only the commenters who fit your ICP. Updated Nov 14, 2026Read article](https://traxy.ai/blog/extract-linkedin-post-comments) [Outbound14 min read ## How to follow up with people who commented on your LinkedIn lead magnet post Follow up with LinkedIn lead magnet commenters: sort who fits, send the resource, then one relevant second message over LinkedIn and email, with consent care. Updated Nov 14, 2026Read article](https://traxy.ai/blog/follow-up-lead-magnet-post-commenters) The right people are already out there. ## Find your warmest leads. _Send them personalized messages._ From relevant interest to personalized outreach. Put traxy to work. [Start your free trial](https://app.traxy.ai/signup) [Book a demo](https://calendly.com/d/cvj3-p2p-cpv/traxy-demo?utm_source=website&utm_medium=cta&utm_campaign=book-demo&utm_content=footer) 7-day free trial [traxy](https://traxy.ai/) Get the most qualified leads on LinkedIn, in real time. **Product**[Social Intent Search](https://traxy.ai/social-intent-search) [LinkedIn Social Listening](https://traxy.ai/linkedin-social-listening) [Signal-Based Outbound](https://traxy.ai/signal-based-outbound) [MCP Access](https://traxy.ai/linkedin-mcp) [Case Studies](https://traxy.ai/case-studies) [Pricing](https://traxy.ai/pricing) [DFY Outbound](https://traxy.ai/managed) **Resources**[Scoreboard](https://traxy.ai/scoreboard) [FAQ](https://traxy.ai/faq) [Guides](https://traxy.ai/guides) [Docs](https://docs.traxy.ai/) [Blog](https://traxy.ai/blog) [News](https://traxy.ai/news) [Affiliate ProgramNew](https://traxy.ai/affiliates) [Agency Partners](https://traxy.ai/agency) [Creators](https://traxy.ai/creators) [About traxy](https://traxy.ai/about) [Contact](https://traxy.ai/contact) **Legal**[Privacy Policy](https://traxy.ai/privacy-policy) [Terms of Service](https://traxy.ai/terms-of-service) [Cookie Policy](https://traxy.ai/cookie-policy) © 2026 traxy, inc. All rights reserved.