Skip to main content

How to connect Attio to Albacross

Setting up your integration from Albacross to Attio

Written by Oskar Johnson Hägglund

This guide walks you through connecting Albacross to your Attio workspace and setting up your first connector to push companies and people into Attio.

Before you begin, make sure you have:

  • An active Albacross account with the Attio integration included in your plan. If you don't see Attio in the list of available connectors, your current plan doesn't include it — please upgrade your plan or reach out to our support team to enable it.

  • An Attio workspace where you have permission to install and authorise apps.

Step 1 — Open the Attio integration in Albacross

  1. Sign in to Albacross.

  2. Go to Connectors → Create new connector.

  3. Select Attio from the list of integrations.

Step 2 — Connect your Attio workspace

  1. Click Connect to Attio.

  2. You'll be redirected to Attio's authorisation page. Make sure you are signed in to the correct workspace.

  3. Review the permissions Albacross is requesting and click Confirm to authorise.

Once the authorisation completes you are redirected back to Albacross with a Connected to Attio! confirmation. From here you can immediately start creating connectors.

Step 3 — Create your first Attio connector

A connector is the rule that decides what gets sent to Attio, when, and how. To create one:

  1. Click Create Connector on the success modal (or open Connectors and click + New connector).

  2. Give your connector a name that makes sense to your team, e.g. "Enterprise visitors → Attio".

Choose a segment and conditions

Pick the Albacross segment that defines which companies should be sent to Attio. You can also choose whether to send an event for every visit or only the first time a company is identified.

Choose what to send (Output)

Select what to push to Attio:

  • Company only, or

  • Company and People (contacts from your selected buyer personas).

Then pick an operation mode:

Mode

What it does

Add new records

Only creates records that don't exist in Attio yet. Existing companies/people are skipped.

Update existing records

Only updates records that already exist in Attio. New ones are not created.

Add new and update existing records

Upserts records — creates them if missing, updates them otherwise. This is the most common choice.

Map fields

For both Company and People you can map Albacross fields to the corresponding Attio attributes. Albacross provides a sensible default mapping; you can adjust any field, or add custom Attio attributes you have defined in your workspace.

You can also configure matching fields that Attio uses to identify whether a record already exists (for example, matching companies by domain).

When everything looks right, click Save. From this moment on, any company matching the segment's conditions will be pushed to Attio in real time.

Verifying the connection

To confirm everything is working:

  1. In Albacross, open the connector you just created — recent deliveries are listed in its history.

  2. In Attio, open the Companies (and People, if enabled) list and search for one of the matching companies. You should see the record with the fields populated by Albacross.

Troubleshooting

  • "Domain missing" errors in the delivery log — Albacross can only push companies that have a resolved website domain. Records without a domain are skipped.

  • Records are not appearing in Attio — Check the operation mode: Add new records skips companies that already exist, and Update existing records skips ones that don't. Switch to Add new and update existing records if you want both.

  • The wrong workspace was authorised — Disconnect Albacross from the Attio integration page and reconnect, making sure you are signed in to the correct workspace before clicking Confirm.

  • Permission denied during authorisation — Ask an Attio workspace admin to either authorise the integration or grant you the right to install apps.

Disconnecting

To stop sending data to Attio:

  • Pause a single connector: open the connector in Albacross and toggle it off — its rules are preserved and can be re-enabled later.

  • Disconnect the workspace: open Connectors → Attio in Albacross and click Disconnect. This removes the OAuth token and pauses every Attio connector. You can reconnect at any time by following Step 2 again.

Did this answer your question?