Attio Integrations (2026): What Connects and What to Use
•
Attio connects to the rest of your stack through four layers: close to 200 native apps in its App Store, middleware like Zapier and Make, data pipelines like Segment and Hightouch, and a developer platform with a REST API, webhooks, and an MCP server. API and webhook access is included on every plan, including Free.
So coverage is not your problem. Order is. The teams that call me with a broken Attio setup almost never lack a connector; they wired integrations ad hoc, tool by tool, and ended up with a Zap graveyard, duplicate records, and automations nobody trusts. Every good build I have shipped follows the same sequence, so this guide is written as that sequence: five stages, from killing manual data entry to putting revenue signal on records, with the best Attio integrations for each job and the routes I use to wire them. If you are still evaluating the CRM itself, start with the complete Attio guide.
The four layers of Attio integrations
Every Attio integration falls into one of four layers. Learn the layers and you can wire almost anything.
Layer | What it is | Use it when |
|---|---|---|
Native apps | ~200 apps in the Attio App Store, installed in a few clicks | An app exists for your tool and covers the fields you need |
Middleware | Zapier, Make, n8n, Relay.app, Pipedream | No native app, or you need logic between tools |
Data pipelines | Segment, Hightouch, Polytomic, Fivetran Activations | Product usage or warehouse data needs to land on records |
Developer platform | REST API, webhooks, MCP server, App SDK | High volume, custom objects, or logic middleware cannot express |
Two platform facts shape everything below. First, Attio's pricing page lists integrations, API and webhook access, the App SDK, and the MCP server on all four plans, so you never pay a gate fee just to connect something. Second, Attio's native Workflows run on every plan too, and since the June 2026 engine rebuild, logic and lookup blocks are free; what credits meter is AI usage, billed by actual token consumption against each plan's allowance (250 workspace credits on Free, 1,500 on Plus, 10,000 on Pro, add-on packs from $70 per month). I break down the credit math in Attio pricing explained.
The stages below tell you what to wire at each layer, and in what order. The rule underneath all of them: decide the data model first. Every integration failure I get called in to fix traces back to records, lists, and attributes that were never designed for the data being pushed into them. Integrations amplify whatever structure they land on.
Here is the whole build order at a glance. The rest of the guide walks each stage.
Stage | The job | Wire first |
|---|---|---|
1 | Make logging automatic | Email and calendar sync (built in), a notetaker (Granola, Fireflies), Aircall |
2 | Capture every lead | Typeform or Fillout, Calendly via Zapier, webhook triggers |
3 | Enrich, qualify, route | Built-in enrichment, Clay or Apollo, Slack, sequences |
4 | Revenue and product signal | Stripe, Segment, Hightouch or Polytomic, Fin |
5 | Sync outward | Mailchimp, Customer.io, HubSpot coexistence or Import2 |
Stage 1: Make logging automatic
Nothing else works until the CRM tells the truth on its own, so this stage comes before any automation. Every downstream workflow assumes the record is current; if reps are logging activity by hand, it is not.
Connect | How | What lands on records |
|---|---|---|
Email and calendar | Built into Attio, every plan | Emails and meetings, synced automatically |
Meeting notes | Granola, Fireflies, Circleback, or MeetGeek | AI notes, transcripts, action items |
Calls | Aircall, RingCentral (first-party), or Quo | Dials and recordings |
Browsing | Attio's Chrome extension | Leads captured from Gmail, X, Google Meet |
Email and calendar is not an integration project at all: you connect your Google or Microsoft account inside Attio itself, sync is core platform on every plan, and plans differ only in how many accounts each user can connect. The notetaker category is unusually deep because these vendors know Attio from the inside: Granola runs its own GTM on Attio, and its app sends AI meeting notes straight to the right person, company, or deal record.
Stage 1 is done when you open any record from last week's pipeline and the emails, meetings, and notes are already there. Everything you build next stands on that.
Stage 2: Capture every lead at the source
The second stage is making sure nothing enters your funnel without landing in Attio, deduplicated and attributed. One pattern covers every source: create-or-update keyed on email (so re-submissions update instead of duplicate), into an intake list, with a source attribute set at the point of entry. Skip the source attribute and you will be guessing at attribution forever.
Lead source | Route into Attio |
|---|---|
Forms | Typeform (native workflow block), Fillout, Tally |
Scheduling | Calendly and Cal.com via Zapier; RevenueHero for routing plus booking |
Website visitors | Snitcher or Albacross visitor identification |
Custom forms and internal systems | The workflow Webhook received trigger, no middleware needed |
Groovin for conversations; LinkedIn Ads lead forms via Zapier | |
Outbound replies | lemlist (first-party); Instantly via Zapier or OutboundSync |
Two of these deserve detail.
LinkedIn, because everyone asks, and the answer is the same for every CRM: LinkedIn's API does not permit a native inbox sync, so anything promising one is an unofficial browser extension. Groovin is the bridge that works: it logs LinkedIn messages, InMails, and connection requests onto records as notes and structured attributes (last message received, last invite sent) you can trigger workflows from. OutboundSync logs outreach activity from tools like HeyReach, Fibbler matches LinkedIn Ads engagement to accounts, and the profile-capture extensions listed in the App Store work but carry no LinkedIn endorsement, so vet before standardizing on one.
Outbound replies, because they are the most commonly forgotten capture source. Route Instantly and lemlist replies into the same intake pattern as everything else, so a positive reply becomes a routed lead, not a row in someone's outbox.
Stage 2 is done when every form, booking, reply, and LinkedIn conversation shows up in one intake list with a source attribute, and re-submissions update records instead of duplicating them.
Stage 3: Enrich, qualify, and route
Once leads land automatically, make them decision-ready before a human touches them.
Job | Use |
|---|---|
Baseline firmographics | Attio's built-in enrichment, every plan |
Deep enrichment waterfalls | Clay, bidirectional with records and lists |
Contact and account data | Apollo first-party app, feeding agent blocks |
Scoring, routing, alerts | An Attio workflow ending in the native Slack block |
The routing workflow is where Attio's own automation earns its keep: a record enters the intake list, an agent block checks ICP fit against the enriched fields, the workflow assigns an owner, enrolls the record in a sequence (Pro plan and above), and posts to the owner's Slack channel. Five apps get native workflow blocks like this (Slack, Typeform, Outreach, Mixmax, and Mailchimp, per Attio's automations apps documentation); newer apps like Stripe and Apollo instead expose tools to agent blocks, Attio's AI workflow steps. The engine behind all of this, including custom agents, the JavaScript code block, and building by describing the automation to Ask Attio, is its own topic; I cover it in the Attio Workflows guide.
Stage 3 is done when a new lead gets enriched, scored, assigned, and sequenced without anyone opening a tab.
Stage 4: Put revenue and product signal on records
This is the stage most teams never reach, and it is where Attio stops being a rolodex and starts being a system of intelligence. Three kinds of signal matter, and each has a clean route in.
Signal | Read it live | Write it onto records |
|---|---|---|
Billing | Stripe first-party app, in agent blocks | Stripe webhooks via middleware, or a warehouse pipe |
Product usage | Segment first-party app | Hightouch, Polytomic, or Fivetran Activations from the warehouse |
Support | Fin reads Attio for support context | Zapier events, or Stacksync two-way |
Billing signal: Stripe
The first-party Stripe app is read-first: agent blocks get live access to your Stripe account, so a workflow step can look up a customer, invoice, or subscription mid-run. Ideal for plays like checking subscription status before renewal outreach.
It does not write MRR onto company records on a schedule. For that, point a Stripe webhook at middleware and update the record on events like customer.subscription.updated and invoice.payment_failed, or route Stripe data through your warehouse, covered next.
The recipe clients love most: payment failure fires a webhook, middleware matches the customer to the company, sets a payment status attribute, and an Attio workflow posts a Slack alert to the account owner with a task attached. Churn saves start with that alert.
Product signal: Segment or your warehouse
The first-party Segment app creates and updates records from event data, the fastest route to usage-aware sales. Teams with a warehouse skip straight to Hightouch or Polytomic, both in the App Store, or reverse ETL through Fivetran Activations(formerly Census); Attio's help center documents these warehouse pipelines. Each syncs modeled data (adoption scores, usage tiers, health flags) onto standard and custom objects on a schedule.
This is the architecture behind the usage-based motions in Attio's published customer stories, like Railway's metered-billing setup, and it is the whole subject of Attio for product-led growth.
Support signal: Intercom
Intercom's Fin app in the App Store gives the Fin AI agent live access to your Attio data, so support answers reflect plan, owner, and deal context. Conversations flow back into Attio through Zapier (new or closed conversation triggers a note, task, or attribute update) or through Stacksync's continuous two-way sync of people, companies, conversations, and tickets.
Teams that want support health as a first-class revenue signal model a Tickets object in Attio (Pro plan, since custom objects start there), fed by Intercom webhooks through n8n. The highest-leverage recipe: when a conversation arrives from a company with an open deal above a threshold, alert the AE in Slack. Sales walking into a demo blind to an angry support thread is a solved problem.
Stage 4 is done when an account's MRR, usage trend, and open support threads are visible on the record, next to the pipeline they explain.
Stage 5: Sync outward to marketing and the rest of GTM
The last stage pushes Attio's now-trustworthy data out to the tools that act on it.
Email and lifecycle marketing
Flow | How |
|---|---|
Attio to Mailchimp | The native Add Member to Audience block in workflows |
Mailchimp to Attio | Zapier: unsubscribes write an opt-out attribute back |
Lifecycle messaging | Customer.io connects natively, syncing campaign activity onto records |
Treat Attio as the source of truth for segmentation: build a Newsletter list, let workflows enroll records when they hit your criteria, and push each entry into the right audience with merge fields mapped. Then close the loop the other way, so sequences and future syncs respect every unsubscribe. Skipping that suppression loop is the most common compliance mistake I see in audits.
Running Attio next to HubSpot
If marketing still runs on HubSpot, you have a coexistence question, not an integration gap. There is no native HubSpot app in Attio's App Store, and that is deliberate: most teams connecting the two are mid-migration or splitting the stack.
Situation | Route |
|---|---|
Marketing in HubSpot, sales in Attio | Zapier: HubSpot form and contact triggers, create-or-update keyed on email |
Continuous two-way sync | Stacksync, Polytomic, or Outfunnel with field-level mapping |
Leaving HubSpot | Import2 from the App Store, one click, free on paid Attio plans |
Event-based Zaps drift at scale, which is when the purpose-built sync platforms earn their subscription. The migration playbook is in how to migrate from HubSpot to Attio, and the decision itself is covered in Attio vs HubSpot.
Documents, files, and the product loop
Round out this stage with the quieter first-party apps that remove friction: PandaDoc for documents, Google Drive, Box, and OneDrive for files on records, and Linear and Productboard to push customer feedback into the product loop.
Stage 5 is done when segmentation and suppression flow both ways with your marketing tools and nothing is double-entered between systems.
The plumbing: middleware, webhooks, and the API
Before reaching for middleware at all, check whether Attio's native Workflows can do the job, because since the June 2026 rebuild they cover more of it than most teams assume: custom AI agents with tool and web access, a sandboxed JavaScript block for deterministic logic, schedules, incoming webhooks, and multiple triggers per workflow, with logic and lookup blocks free on every plan. Work that starts and ends on Attio records belongs there, next to the data, where every run is logged and rerunnable. Middleware earns its place when the work is app-to-app rather than record-centric: the other tool has no Attio app, the flow orchestrates two external systems with Attio as one stop among several, or the volume and cost math favors running it outside.
The difference is context. An external tool sees whatever fields an API call returns; an Attio workflow agent sees the emails, call transcripts, and notes on the record, plus every related record. Keep judgment where the context lives, and use middleware for transport. When you do go outside, here is how the three platforms compare. Zapier is the only one with a first-party app in Attio's App Store; Make's verified Attio app lives on Make's own platform, and n8n connects through Attio's API.
Platform | Attio support | Best for |
|---|---|---|
Zapier | 7 triggers, 13 actions, connects Attio to 9,000+ apps | Speed and reach; most SaaS tools have a Zapier app |
Make | 20 Attio modules: 1 trigger, 16 actions, 3 searches | Multi-step visual scenarios at lower per-task cost |
n8n | Connects through Attio's REST API and webhooks with native HTTP and Webhook nodes | Self-hosted control and complex transformation logic |
Zapier's Attio triggers cover records and list entries (created, updated, deleted) plus tasks, and its most useful action is create-or-update, which deduplicates by a unique attribute like email. It is the fastest path for form intake, enrichment handoffs, and pushing CRM events into ops tools, and because Attio's Zapier integration is powered by Attio webhooks under the hood, triggers fire in near real time rather than on polling delays.
Make suits heavier multi-app scenarios with visual data mapping, and it runs deeper into configuration: it can create attributes and select options programmatically, which Zapier cannot.
n8n has no official Attio node, so production builds talk to the REST API and webhooks directly through n8n's native HTTP and Webhook nodes, which stay current with the API instead of depending on a community package. Self-hosting removes per-task pricing, and it is what we deploy when a client needs orchestration they own end to end.
The pattern: prototype in Zapier, ship volume in Make or n8n, and move anything that runs thousands of times a month onto webhooks plus the API.
Attio's webhooks run in both directions on every plan. Outbound, Attio fires HTTP POSTs to your endpoint on events like record.created and record.updated. You create them in Workspace settings under Developers, or via the API, which also unlocks filtering so you only receive the events you care about. Payloads are signed with an HMAC SHA256 Attio-Signature header, delivery is at-least-once with an idempotency key, failed deliveries retry up to 10 times over roughly three days, and delivery is rate-limited to 25 requests per second per target URL. Targets must be HTTPS. Inbound, the Webhook received workflow trigger from Stage 2 accepts events from any system that can send an HTTP request.
The developer platform wraps all of it: the REST API for everything programmatic, the App SDK for building apps that live inside Attio's interface, a SQL interface for querying workspace data, and the MCP server, which lets Claude, ChatGPT, or any MCP client search and update your workspace in natural language. The first-party ChatGPT and Claude apps in the App Store are this server productized, and the full setup, from connecting Claude to running agent frameworks against your workspace, is in my Attio MCP guide.
The full App Store map
For reference, the Attio App Store holds just under 200 apps across 11 categories as of July 2026. Around 30 are first-party apps built by Attio; the rest come from an App Partner ecosystem building on the App SDK. The table below is the map, with the apps I actually see deployed at seed to Series B teams.
Category | First-party (By Attio) | Notable third-party |
|---|---|---|
Email and calendar | Gmail, Outlook | Slashy |
Communication | Slack (notifications + Ask Attio) | Salesmsg, Scribeless |
Meetings and calling | Zoom, Google Meet, Microsoft Teams, Aircall, RingCentral | Granola, Fireflies, Circleback, MeetGeek, Quo, Claap, JustCall |
Data and enrichment | Apollo, Segment, Hightouch, Notion, Airtable | Clay, Polytomic, Customer.io, Wiza, Harmonic, Specter, Snitcher, Albacross |
Outbound and email marketing | lemlist, Outreach, Mixmax, Mailchimp | Salesforge, OutboundSync, Outfunnel |
Billing and documents | Stripe, PandaDoc | Sequence, Hyperline |
Forms and scheduling | Typeform | Fillout, Tally, RevenueHero, Default |
Product and support | Linear, Productboard | Fin by Intercom, Plain, Productlane |
Automation platforms | Zapier | Make (via Make's platform), Pipedream, Relay.app, Composio, Integrately |
AI assistants | ChatGPT, Claude | Klavis AI, Arcade.dev |
Files and admin | Google Drive, Box, OneDrive, Okta (SCIM) | Import2 |
Where Attio integrations fall short
An honest map includes the gaps.
No native two-way sync apps for other CRMs. HubSpot and Salesforce connections always route through middleware or a sync platform, which is an extra subscription during any co-existence period.
The first-party Stripe app reads more than it writes. Putting MRR on records still takes middleware or a warehouse pipe, as covered in Stage 4.
LinkedIn depth depends on unofficial extensions. Profile capture and message sync exist only as browser extensions from small vendors, none endorsed by LinkedIn. That is true for every CRM, but vet before you standardize on one.
Marketing automation connects shallowly. The Mailchimp block adds members to audiences; it does not sync campaign engagement back onto records natively. Full-suite marketing teams will lean on Customer.io, Outfunnel, or a data pipeline.
Much of the App Store is young. Many partner apps are early-stage products from small vendors. Before wiring one into a revenue-critical flow, check what happens on failure and whether the vendor publishes a changelog.
Agent-heavy workflows are real money at volume. Logic and lookup blocks are free on the new Workflows engine, but AI blocks bill by token usage against your plan's credit allowance, so model the burn before you put an agent in the path of thousands of monthly events. High-volume, low-logic syncs often belong on webhooks and the API instead, where nothing is credit-metered.
Frequently asked questions
Does Attio integrate with HubSpot?
Not natively. There is no HubSpot app in Attio's App Store. Teams migrating use Import2, which is free for Attio customers on paid plans. Teams running both tools sync them through Zapier for event-based pushes, or through a two-way sync platform like Stacksync, Polytomic, or Outfunnel.
How do I connect LinkedIn to Attio?
Not through a native sync, because LinkedIn's API blocks that for every CRM vendor. Groovin, a Chrome extension bridge, syncs LinkedIn messages and invites onto Attio records as workflow-ready attributes. Outreach activity from tools like HeyReach syncs through OutboundSync or Zapier, and LinkedIn Ads lead forms arrive through Zapier.
Do Attio integrations cost extra?
Installing apps is free, and API and webhook access is included on every Attio plan. Real costs come from workflow credits past your plan's monthly allowance (250 on Free up to 10,000 on Pro, with add-on packs from $70 per month), middleware task fees, and third-party app subscriptions.
Does Attio have webhooks?
Yes, in both directions. Outbound webhooks fire on events like record.created and record.updated with HMAC-signed payloads and automatic retries. Inbound, any workflow can start from a Webhook received trigger that gives you a URL, so external systems can start Attio automations directly without any middleware in between.
Does Attio work with Instantly?
Yes, through connectors rather than a native app. Zapier's Instantly integration triggers on campaign events like replies, opens, and bounces and writes them to Attio records. OutboundSync, built by its own vendor and listed in Attio's App Store, logs Instantly sends, opens, replies, and bounces onto people and companies.
Is there an Attio Intercom integration?
Partly. Intercom's Fin app in the Attio App Store gives the Fin AI agent live access to your Attio CRM data for support context. Syncing the other way takes Zapier for conversation-triggered notes and tasks, or a two-way platform like Stacksync to keep people, companies, and tickets aligned.
Sparsh Gupta, Founder of Automation Jinn and an Official Attio Expert Partner, helps seed to Series B B2B SaaS teams design AI-native GTM systems on Attio, from the data model to the integrations and agents on top. If you want your stack wired into one working system instead of a pile of Zaps, book a discovery call.
