Attio integration
Documentation·SignalRaven app for Attio

SignalRaven app for Attio

How to install the app, what it is allowed to do, what it creates in your Attio workspace, and how to remove it.

What the app is

SignalRaven finds buying-intent signals on LinkedIn. A signal is one public action by one person, such as a comment on a competitor's post, that SignalRaven has scored and matched to your ideal customer profile. The SignalRaven app for Attio delivers those signals into your Attio workspace. For each signal it creates or updates a company record and a person record, adds a note that explains the signal, and creates a task for the follow-up.

SignalRaven operates the app and it runs on SignalRaven's servers. It connects to Attio through OAuth, using the permissions listed below. Nothing is installed inside Attio, and the app adds no custom attributes or objects to your workspace.

Requirements

  • A SignalRaven account. Every plan includes the Attio app, and the free trial includes it as well. You can create an account in a few minutes.
  • An Attio workspace in which you are allowed to authorize apps. If Attio refuses the consent screen, ask a workspace admin to connect.

Install and connect

The connection is created from SignalRaven. The Install button on the Attio App Store listing opens the same page in SignalRaven that step 1 describes, so both paths continue identically.

  1. Sign in to SignalRaven and open Destinations. A destination is a place SignalRaven sends signals to, such as a Slack channel or, here, an Attio workspace.
  2. Choose Add destination, then Attio.
  3. Choose Connect Attio. SignalRaven redirects you to Attio.
  4. On Attio's consent screen, pick the workspace, review the permissions and confirm. The permissions match the table in the next section.
  5. Attio returns you to Destinations. A banner reading Attio connected names the workspace, and the new destination appears in the list.
  6. Choose Send test message to confirm the connection. The next section but one describes what the test creates.

Attio issues the app a token that is limited to the workspace you picked. The token has no expiry date. It stays valid until you delete the destination in SignalRaven or a workspace admin removes the app in Attio.

Permissions

The app requests five scopes. Each one is needed for a single purpose.

ScopeWhy the app needs it
record_permission:read-writeRead, create and update company and person records. The app uses it to find an existing company or person and to create or update one.
object_configuration:readRead the attribute definitions on the Companies and People objects, so the app writes to the correct attribute slugs in your workspace.
note:read-writeCreate the note that carries the signal on the person record.
task:read-writeCreate the follow-up task linked to the person record.
user_management:readAttio requires this scope to call the tasks endpoint. The app reads no user data.

The app reads from Attio only to find a matching company or person before it writes. It never reads your existing notes, tasks or lists, and it never deletes anything.

What the app creates in Attio

Each delivered signal produces up to four items. The app writes them in this order, because Attio requires a record to exist before another record can reference it.

  1. A company record. If the signal includes the company's website, the app looks for a company whose domains attribute contains that domain. If there is no website, it looks for a company with exactly the same name. If it finds one, it uses that record. If it finds none, it creates a company with the name, the domain when the signal has one, and the LinkedIn company URL when the signal has one.
  2. A person record. The app looks for a person whose linkedinattribute equals the signal's LinkedIn profile URL. If it finds one, it uses that record. If it finds none, it creates a person with the full name, the job title, the LinkedIn URL and a reference to the company from step 1. SignalRaven does not collect email addresses, so email is never used for matching and is never written.
  3. A note on the person. The title names the signal type and its urgency score, for example SignalRaven: Competitor post comment (8/10). The body contains the score, why the signal matters, the context, a summary of the post, a suggested opening message, the ideal customer profile persona, and links to the signal in SignalRaven, the LinkedIn profile and the source post.
  4. A task linked to the person. The task is due two days after delivery. Its title names the person, the company and the signal, for example Reach out to Jane Smith at Acme Corp: Competitor post comment (8/10), and its body repeats the suggested opening message.

When the same person produces a second signal, the app finds the existing person record and adds a new note and a new task to it. It never creates a duplicate person or company for a record it can match.

The test message

Send test message on the Destinations page sends one sample signal through the same code path as a real delivery. In Attio it creates a company named Acme Corp with the domain acme.com, a person named Jane Smithlinked to that company, a note on Jane Smith, and a task due in two days. All four appear in Attio's activity feed as created by SignalRaven. The test records are ordinary records and you can delete them in Attio afterwards.

A test message always goes to the destination you chose. Routing rules, described next, do not apply to test messages.

Routing rules

A routing rule decides which signals a destination receives automatically. SignalRaven scores every signal for urgency on a scale from 1 to 10, and a signal that passes SignalRaven's review is called a qualified signal. Each destination has one of three rules:

  • All. Every qualified signal is delivered to this destination as soon as it is approved.
  • Min urgency. Only qualified signals whose urgency score is at or above a threshold you set, from 1 to 10, are delivered automatically.
  • Manual. Nothing is delivered automatically. You send individual signals to the destination from the signal's page in SignalRaven.

In the current version, Connect Attio creates the Attio destination with the All rule. Whichever rule a destination has, you can also send any single signal to it by hand: open the signal in SignalRaven and use Send to. You can pause a destination at any time from its page in SignalRaven, and resume it later.

Disconnect

You can disconnect the app from either side. Records the app already created in Attio stay in place in both cases.

  • From SignalRaven. Open the destination and choose Delete. SignalRaven stops delivering to that workspace, revokes its token with Attio, and deletes the token and the workspace details it stored. To reconnect later, add the destination again.
  • From Attio.A workspace admin removes the app in Attio's workspace settings. The next delivery fails, SignalRaven pauses the destination automatically and sends your workspace an email that explains how to reconnect. Delete the destination in SignalRaven to finish the removal.

What SignalRaven stores

For a connected destination SignalRaven stores the OAuth token, the Attio workspace id, name and slug, the destination's name and routing rule, and a delivery log that records which signals were sent and whether Attio accepted them. Deleting the destination deletes the token and the workspace details. SignalRaven's privacy policy and terms of service cover the rest of the account.

Support

Write to support@signalraven.ai with the name of your SignalRaven workspace and, if the question is about a specific delivery, the link to the signal. The Attio integration page gives a shorter overview of the app.