Which Attio records can LeadJourney write to?

Destinations in Send to Attio can write People, Companies and Deals, using the Create, Update or Upsert write mode.

Do I lose my triggers when I re-authorize?

No. Re-authorize and Reconnect keep your triggers and settings. Only Disconnect deletes them.

Connect Attio

Q: Does LeadJourney import my existing Attio records?

No. LeadJourney tracks new Attio events from the moment you connect. Data from before the connection is not imported.

Connect your Attio workspace in minutes, with no API keys and no webhooks to wire by hand. Authorize once, map CRM record events like new people, new deals, new companies and stage changes onto your conversions, and push LeadJourney data back into Attio.

Connecting Attio turns CRM record events – new people, new deals, new companies, stage changes – into LeadJourney conversions, automatically attributed to the campaign, ad set and ad that earned them. You authorize Attio once (no keys to copy, no webhook URLs to paste by hand), then map each Attio event onto one of your conversion types. Mapped events flow through the same postback pipeline as your offline conversions, so they automatically pick up every ad postback you've already configured. The same screen also lets you send LeadJourney clicks, leads and conversions back into Attio as records.

Before you start

Have these ready so the connection works end to end:

An active LeadJourney workspace and an Attio workspace you can sign in to.
Tracking is live – clicks have to be recorded first so records can be matched back to a campaign. See Install the tracking script.
A way to capture the click ID on your Attio records – typically a click_id attribute on your People (or Deals) object (see the callout below).
At least one conversion type to map onto (e.g. WonClient). Set these up first in the Events Manager.

Where to find it

Open Settings → Apps, or go to app.leadjourney.io/settings?slug=apps. Click the Attio card to open the integration (or use ?slug=apps&app=attio). While you're not connected you'll see a “Connect your Attio workspace” card; once connected, the same screen shows your workspace, your triggers and the Send to Attio panel.

Step by step

Authorize LeadJourney from Attio

On the Connect your Attio workspace card, click Connect with Attio. You'll be redirected to Attio to sign in and approve LeadJourney's access.

The grant gives read access to your records (people, deals, companies) and object configuration, plus read/write access for webhook subscriptions (so LeadJourney can subscribe to record changes) – there are no keys to copy and no webhook URLs to paste. After you approve, Attio sends you back and you'll see an “Attio connected” confirmation.

Syncing starts when you connect

LeadJourney tracks new Attio events from the moment you connect. Data from before the connection is not imported.

Check the connection details

Once connected, the header shows a Live pill (or Needs reconnect if something breaks), plus Re-authorize and Disconnect buttons. Below it you'll see the Connection status, your Workspace name and ID, Active triggers (active out of total) and the Connected since date.

Add a trigger

In the Triggers panel (“Each trigger maps an Attio record event to one of your conversions.”) click Add trigger. In the New Attio trigger dialog:

App: Attio (already selected).
LeadJourney Event: pick the conversion type this Attio event should record, e.g. WonClient. (No options? Create one under Settings → Events first.)
Trigger: choose the Attio event that should fire it, such as a new person, a new deal, a new company or a stage change. The object (people, deals or companies) is set by the trigger you pick. Search triggers… narrows a long list.
Attribute changed (optional, on update triggers): pick an attribute and a Target value so the trigger only fires when the attribute changes to that value. Status and select attributes (e.g. a deal stage) show a dropdown of their real options; leave Any value (or the field blank) to fire on any update.

Click Continue.

Receive data and confirm the mapping

The dialog opens a three-tab flow:

Receive Data: click Find latest data to load the 3 most recent records for the event you picked. With a target value set, only records currently at that value are shown. If nothing appears, create a matching record in Attio and check again, then select a record and click Continue with selected record.
Configure Mapping: map the Attio record onto LeadJourney columns. New triggers start with Email, Name, Phone, click_id, Revenue and Currency, pre-filled where LeadJourney finds a likely path. Add custom field adds First name, Last name or one of your workspace's custom fields, or Create new field (type Text, Number or Currency). Select several paths to join them with a space, or use static:value for a literal. On Deal triggers, prefix paths with person. to pull from the associated person. Mapping click_id is recommended but optional (see the callout below).
Filtering (optional): click Add Another Filter and set a path, an operator and a value, e.g. only fire when stage equals Won. Each filter is tested against the record you selected and shows PASS or FAIL, with a summary like “Your trigger would have fired”.

Click Save & Continue to finish (Save changes when editing), or Save and continue later to keep your progress.

How Attio records link to the right campaign

Attio doesn't capture LeadJourney's click ID on its own – you store it on the record and map it here. The usual setup is a click_id attribute on your People (or Deals) object that holds the visitor's click ID. On the Configure Mapping tab, point click_id at that attribute and every record arrives already tied to the click – and therefore the campaign, ad set and ad – that earned it. No click ID? LeadJourney falls back to matching on email or phone.

Managing your triggers

Each trigger appears as a row – Attio event → conversion type – with an Active / Paused pill and a summary of how many fields and filters it uses.

Pause / Resume: use the toggle to stop a trigger temporarily without deleting it.
Edit: change the event, condition, mapping, filters or target conversion. The URL gets a trigger_id parameter, so you can share a link that opens that trigger directly.
Delete: type delete and click Delete trigger. The mapping and filters can't be recovered; other triggers keep running.
Add another: use Add trigger again to map more Attio events (new people, deals, companies, stage changes) onto different conversions.

Send data back to Attio

The Send to Attio panel pushes LeadJourney clicks, conversions and leads into Attio as records, no Zapier needed. Click + Add destination, then:

Create this Attio record: choose Person, Company or Deal.
When this happens: pick the LeadJourney event. For a conversion event you can narrow it with Conversion type, or leave it on Any conversion type.
Write mode: Create always creates a new record, Update only updates an existing match and skips if none is found, Upsert updates the match if one exists, otherwise creates.
Matching attribute (Update and Upsert): the attribute that identifies an existing record, such as email addresses, phone numbers, domains or another unique attribute. In Update mode, a deal can also be matched through its associated person or company. If the object has no unique attribute, use Create or add a unique attribute in Attio.
Map fields: pick an Attio column, then the LeadJourney value to write into it. Columns Attio needs to create the record are marked Required and added automatically; values LeadJourney can't derive (e.g. a deal's stage, or an owner email) can be typed as a fixed value and added with Add. A reference column links to an existing record (people match by email, companies by domain), and an owner column matches a workspace member by email. Select several values to join them with a space. Find latest data shows real example values; + Add field adds another row. In Update mode, only the columns you map are changed.

Click Create destination. Each destination row has Pause / Resume, Edit and Delete (deleting stops new records; existing Attio records are not affected). The Sync history table lists every delivery with its Status (Success, Failed or Skipped), event, object, mode, time and detail, and a Retry button for failed or skipped ones.

Reconnecting

If Attio revokes the app, the webhook subscription goes missing, or Attio is unreachable, the header flips to Needs reconnect and a banner explains why (e.g. “Attio disconnected your app” or “Webhook subscription is gone”). Click Reconnect to re-run the authorization. To refresh granted permissions while everything still works, use Re-authorize in the header. In both cases your triggers and settings are kept.

Disconnecting

To remove Attio, click Disconnect in the header, type disconnect and confirm with Disconnect Attio. This is deliberate because it's destructive:

Disconnect deletes your triggers

Disconnecting permanently removes the Attio connection, deletes every trigger and revokes the webhook subscription. Attio events stop flowing into your conversions immediately. You can reconnect later, but your trigger configuration won't be restored – you'll set them up again.

Troubleshooting

No records when you click “Find latest data”?

Nothing recent exists in Attio for that object yet, or no record is at the target value you set. Create a matching record (a new person, deal or company) or move one to that value, then click Find latest data again. The record should appear so you can finish the mapping.

Records come in but aren't attributed to a campaign?

LeadJourney needs to know which click the record belongs to. Check that (1) the tracking script is installed and recording clicks, (2) your records carry the click ID in a click_id attribute and the trigger maps click_id to it, and (3) the trigger is Active. As a fallback, email or phone can be used to match.

Header shows “Needs reconnect”?

Attio has revoked the grant, the webhook is gone, or the API is unreachable. Click Reconnect in the banner to re-authorize. Your triggers are preserved.

A destination shows Failed or Skipped deliveries?

Open Sync history and read the Detail column. Update skips when no match is found, and every Required column needs a value when a record is created. Fix the destination, then click Retry.