Attio

The Attio integration writes Target Account intent onto the matching company in Attio. When a signal fires for a target account, Logspot updates that company with the latest signal, how strong it was, when it happened, a short summary, and a link back to Logspot. Logspot writes companies only. It never creates or changes people.

Attio is in early access on the Pro plan and higher; email support@logspot.io to turn it on.

What Logspot Writes

Logspot writes six attributes on the company:

The link is a text attribute, which is what Attio recommends for full URLs.

You can keep these Logspot attributes, or point any field at one of your own Attio company attributes of the same type. Logspot Company ID always uses its own Logspot attribute, since it is the key that ties the two records together. Don't edit it.

The signals that reach Attio are the account-level intent signals: Target Account Visited, High-Intent Page Visit, Return Visit, Usage Spike, and Custom Rule Matched.

Connect Attio

1. Go to Integrations → Browse Catalog and open Attio.
2. Click Connect Attio. Logspot sends you to Attio to approve access.
3. Approve access for the workspace you want Logspot to write to, then return to Logspot.

In Logspot, connecting is for owners and admins. In Attio, Logspot asks for workspace-level access, and only workspace admins can grant it. Until Attio has reviewed the Logspot app, Attio shows a warning that the app has not yet been approved by the Attio team. Confirm to continue.

Logspot asks for two permissions: read and write records, to find, update and (if you allow it) create companies, and read and write object configuration, to create its six attributes. If Attio doesn't grant both, Logspot doesn't connect and asks you to connect again and approve every permission.

Each Logspot organization connects to one Attio workspace. The Attio card in Your Integrations shows the workspace's name.

Set Up the Fields

After connecting, the Attio card in Your Integrations shows Needs Setup with a Set Up Fields button. Open it to review each field:

• Create Logspot Attributes creates any missing Logspot attributes on Attio's Companies object. It never edits an attribute that already exists.
• Or point a field at one of your own Attio attributes of the same type, then Save Field Choices. Only your own attributes that Logspot can write are offered, never Attio's system attributes.

Each field shows a state (Ready, Missing, Archived, Incompatible, or Read-Only) so you can tell what is left before Logspot writes anything. An archived attribute needs to be restored in Attio. Use Check Again after you fix something in Attio. The card reads Connected once every field is ready.

Send Signals to Attio

Once every field is Ready, turn on Send Signals on the Attio card in Integrations → Your Integrations. Logspot creates a Send Notification action named Send Signals to Attio that writes each Target Account visit, high-intent page visit, return visit and usage spike to Attio as it happens. Turn the switch off to pause it.

To change what it sends, open the action in Actions → Your Actions:

• Add or remove triggers, including your custom rules.
• Turn on Create Missing Companies if you want Logspot to create a company in Attio when none matches.
• Use Send Test from the action's menu to write a test to Attio.

You can also build your own Send Notification action for Attio from Actions → Browse Catalog. An action that sends to Attio sends nowhere else, so post to Slack from a separate action. The switch pauses and resumes every action that sends to Attio.

Send Test takes the most recent real Target Account signal that matches the action's triggers and writes it to Attio right away. It is a real write: it updates the matching company, or creates one when Create Missing Companies is on. If no matching signal has fired yet, the test says so and writes nothing.

Each signal Logspot writes to Attio uses 1 Action, the same as any notification. Writes that are skipped, held for review or fail cost nothing, and so does Send Test.

How Matching Works

Logspot matches by domain, using the company's Domains attribute in Attio. A company saved with www.acme.com matches acme.com. A subdomain such as shop.acme.com is a different domain and doesn't match.

• No match: the write is skipped, unless Create Missing Companies is on. Then Logspot creates the company in Attio with the Target Account's name and domain. It first checks for a company it created earlier, so a reconnect doesn't create a duplicate.
• One match: Logspot updates that company.
• Two or more matches: Logspot leaves them alone for you to review, rather than guessing which is right.

For example, a Usage Spike for acme.com updates the one Attio company whose domain is acme.com. Once Logspot has written to a company, later signals for that account update the same company. An older signal never overwrites a newer one already written, so the fields always reflect the latest intent. Updates only touch the six Logspot fields.

Statuses and Reconnecting

The Attio card in Your Integrations shows one status:

• Connected: working.
• Needs Setup: connected, but the fields still need setup. Use Set Up Fields.
• Error: Attio access was lost. Use Reconnect to authorize again.

If Attio rejects Logspot's access, the card moves to Error with a Reconnect button, and nothing more is sent to Attio until you reconnect. If a write names an attribute Attio no longer has, Logspot marks that field Missing, the card moves to Needs Setup, and writes are skipped until the setup check passes again.

Reconnecting to a different workspace starts field setup over and cancels any writes still queued for the old workspace.

Disconnecting

Open the Attio card's ⋮ menu and choose Disconnect. Logspot revokes its Attio access token, stops using it, and cancels any writes still queued. Actions that send to Attio stop delivering until you connect it again.

Attio keeps listing Logspot as installed after you disconnect, with no access tokens. To remove it from your workspace too, go to Settings → Apps in Attio, open Logspot, and choose Uninstall.

The Logspot attributes, and the values already written, stay on your Attio companies. If you no longer want them, archive them in Attio. Your own attributes that you pointed fields at keep the values Logspot wrote.

Troubleshooting

Open the action's View Activity to see each write. Every write shows Created, Updated, Skipped, Needs Review, or Failed, with the reason. Created and updated writes link to the company with Open in Attio.

• No Attio company has the domain ...: nothing matched. Add the domain to the company in Attio, or turn on Create Missing Companies.
• More than one Attio company has the domain ...: merge or fix the duplicates in Attio. The next signal then updates the one company left.
• A newer signal for this company was already sent.: expected. The newer intent stays.
• The Attio fields need setup.: open Set Up Fields on the Attio card.
• Attio is missing ...: an attribute was deleted or archived. Open Set Up Fields, fix it, and use Check Again.
• Reconnect Attio.: Attio no longer accepts Logspot's access. Use Reconnect on the Attio card.
• Attio denied access.: reconnect Attio and approve every permission.
• The company has no usable domain.: the account's domain is missing, a personal email domain, or an IP address, so it can't match.
• The visitor opted out of sharing. or The company is not a Target Account.: the signal isn't eligible to send.

When Attio is busy or briefly unavailable, Logspot tries again with longer waits between tries, up to five tries in all. After that, the write shows Failed.

If connecting fails with This Attio connection link has expired or was already used, start again from Integrations. A connect link lasts ten minutes and works once.

Data and Privacy

• Logspot writes companies only. It never creates or changes people, or any other kind of Attio record.
• An update writes only the six Logspot fields, or the attributes you pointed them at. A create also sets the company's name and domain.
• The summary is built from the signal name, its strength, and fixed details: the matched page (/pricing, /demo, or /docs), the return-visit window, usage counts, or your custom rule's name. It never includes people or visitor details.
• Signals from visitors who opted out of sharing are never sent.
• Built-in signals are limited to one per type per account each day, so Attio stays current without the noise.
• Logspot stores its Attio access token encrypted, and revokes it when you disconnect.
• Logspot keeps the details of each write for 30 days, then keeps only its result.

Questions? Email support@logspot.io.

Related

• Integrations
• Signals and Target Accounts
• Actions