Attio AI employee

What can your AI employee do in Attio?

Viktor, the AI employee, connects to your Attio workspace and works with your records, objects, lists, list entries, notes and tasks. He can look up people and companies, read objects and attributes, read a record's attribute history (for example a deal's stage), review a pipeline in a list, create and update records, add notes and tasks, list workspace members, read meetings, call recordings and transcripts, and read and write comments.

REST API: for anything the named actions don't cover, he calls Attio's REST API v2 directly within the scopes you grant. Creating, changing or deleting webhooks that way is refused, because the triggers manage their own.

Triggers (webhooks): Viktor can react to Attio events as they happen. When you set up a trigger, he creates a webhook in your Attio workspace for it, and he deletes that webhook when you remove the trigger. Supported triggers: new record (a record is created, optionally only for one object such as people or companies), record updated (a record's attribute values change, optionally only for one object) and new note (a note is created on a record). Every incoming event is checked against Attio's webhook signature.

Permissions: Viktor asks for these 11 Attio scopes: record_permission:read-write, object_configuration:read-write, list_configuration:read, list_entry:read-write, note:read-write, task:read-write, user_management:read, webhook:read-write, comment:read-write, meeting:read and call_recording:read. Records are read and written through record_permission, object_configuration:read-write lets him add attributes and select options when you ask, triggers need webhook:read-write, meeting:read and call_recording:read let him list meetings, call recordings and transcripts, and comment:read-write lets him read comment threads and comment on records. A key missing a scope is refused at connect with the missing scopes named.

Setup: a workspace admin opens Workspace settings > Developers in Attio, creates an access token, ticks the scopes above and pastes the token when Viktor asks to connect Attio. Viktor checks the token against your workspace and its scopes before saving it. Disconnecting removes the token from Viktor; delete it in Attio under Workspace settings > Developers to revoke it. Signing in with your Attio account (OAuth) instead of a token becomes available once Attio approves the Viktor app.

What teams use Viktor for in Attio

• When a new company record is created, he reads it, fills in the attributes that are missing and adds a note saying what he changed.
• Every Friday he reviews the deals in your pipeline list, reads each deal's stage history and posts what moved, what stalled and for how long.
• After a sales call he adds a note to the person's record and creates a follow-up task with a deadline for the owner.

Use Attio from Slack and Microsoft Teams

Message Viktor in a Slack channel, a Microsoft Teams chat or a direct message. He opens Attio, does the work and posts the result in the same thread, so nobody has to switch tabs.

He can also run Attio work on a schedule, like a weekly Attio summary posted to your team's channel. Anything sensitive waits for your approval before it runs.