Skip to content
CRM

Attio to Close integration — real-time, two-way sync

Keep Attio and Close in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Attio and Close

Run Attio and Close side by side with the same accounts and contacts in both, whether they serve different teams or one is replacing the other.

Two CRMs in one company is more common than anyone plans for: an acquisition brings its own system, regions or business units standardize differently, or a migration is under way and both are live. In every case, some of the same companies and people exist in both systems, and every day of manual double entry pushes the copies further apart.

Stacksync syncs Custom objects, People, Companies, Users in Attio with Custom Activities, Custom Fields, Users, Smart Views in Close in real time and in both directions, with field-level mapping and matching on identifiers you choose. Update a record in either CRM and the other reflects it within seconds.

Common use cases

  • 01 Keep Attio aligned with a billing system or ERP on customer records and plan status.
  • 02 Mirror lists and list entries into a database for pipeline reporting beyond the in-app views.
  • 03 Two-way sync between Close and a billing or ERP system so closed-won opportunities create customers and invoices automatically.
  • 04 Keep Close contacts aligned with a marketing automation platform so outreach lists stay current.

Common sync patterns

Divisional or regional split

Where each CRM serves a different team or region, sync just the shared accounts and contacts so handoffs and cross-sell work.

Where both track pipeline: deal visibility across systems

Deal stage and value on shared accounts stay visible from either CRM.

Post-acquisition consolidation

Keep both CRMs accurate while the merged team decides on a target system, instead of freezing one and losing months of updates.

What you can sync between Attio and Close

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Attio objects Close objects How this pairing syncs
Users Synced with incremental and full sync per the Stacksync docs. Users Sales reps referenced as owners on leads, opportunities, and activities. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Workspaces Synced with incremental and full sync per the Stacksync docs. Opportunities Deal records with value, confidence, and status; commonly synced to reporting and billing systems. Workspaces is specific to Attio and Opportunities to Close — each maps to any object or custom field on the other side.
Custom objects Workspace-defined objects that behave like standard ones in the API. Activities Calls, emails, SMS, notes, and meetings logged against a lead; the source for engagement analytics. Custom objects is specific to Attio and Activities to Close — each maps to any object or custom field on the other side.
People Standard person object; synced with marketing tools and warehouse person tables. Tasks Follow-up items assigned to users; synced for workload and SLA reporting. People is specific to Attio and Tasks to Close — each maps to any object or custom field on the other side.
Companies Standard company object; matched to billing and product accounts in two-way syncs. Custom Activities User-defined activity types with their own custom fields, mapped like standard activities. Companies is specific to Attio and Custom Activities to Close — each maps to any object or custom field on the other side.
Deals Pipeline records; read out for revenue reporting and written to from automation. Custom Fields Org-specific fields on leads, contacts, and opportunities; addressed by stable field ids in syncs. Deals is specific to Attio and Custom Fields to Close — each maps to any object or custom field on the other side.

How changes propagate between Attio and Close

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Attio Close Sub-second propagation

DetectionAttio notifies Stacksync of record changes through webhook events. Webhooks on record and list-entry events, with polling as a fallback.

DeliveryEach detected change is written to Close through its API, with automatic retries and rate-limit backoff.

Close Attio Sub-second propagation

DetectionClose notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling on date_updated fields for backfills.

DeliveryEach detected change is written to Attio through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Attio: Subject to the platform's published API rate limits.
  • Close: Subject to per-endpoint rate limits communicated in response headers.
What ships with Attio ⇄ Close

Connect Attio and Close for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Attio–Close connection.

Real-time

Two-way sync

Changes in Attio or Close instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Attio or Close data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Attio or Close record.

Observability

Monitoring

Track your Attio ⇄ Close sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Attio and Close.

How the Attio and Close connectors work

Attio

Integration surface
REST API
Authentication
Guided in-app connection ("Attio CRM" connection created in a few clicks, "without any coding required"); the docs do not name the underlying auth mechanism (OAuth vs API key)
Change detection
Webhooks on record and list-entry events, with polling as a fallback
Capabilities
read · write · webhooks
Rate limits
Subject to the platform's published API rate limits.
Attio setup guide

Close

Integration surface
REST API
Authentication
API key (sent via HTTP Basic auth)
Change detection
Webhook subscriptions for record events, with polling on date_updated fields for backfills
Capabilities
read · write · webhooks
Rate limits
Subject to per-endpoint rate limits communicated in response headers
How it works

How to connect Attio to Close — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Attio and Close with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Attio connected
    Close connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Attio and Close objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Attio ⇄ Close
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Attio Close
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Attio and Close integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 390 integrations available for Attio and Close.

Popular · 8 of 390
All Attio integrations All Close integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own