Attio workflows: how CRM automation works in Attio

You build a workflow on a canvas. The trigger block decides when it runs, and the action blocks after it decide what happens. Attio's block library groups triggers into four kinds:

• Record triggers, such as 'Record created'.
• List triggers, such as 'Record added to list'.
• Task triggers, such as 'Task created'.
• Utility triggers, such as 'Manual run', a schedule or an incoming webhook.

Attio's help center gives updating a record, creating a task, sending a Slack message, enrolling someone in a sequence and making an HTTP request as examples of action blocks. You can also describe a workflow in plain language and let Ask Attio build it. Apps built with the Attio SDK can add their own blocks, which then appear in the block picker next to the built-in ones.

Workflow runs and AI features draw on the workspace's shared credits. Attio's billing docs describe how they are counted:

• Most workflow blocks use one credit each time they run.
• Credits are only charged for blocks that actually run. If a run fails partway, the failed block and every block after it use no credits.
• Recalculating AI attributes also uses credits.
• Admins can see credit usage per workflow in Workspace settings.

The number of credits included differs by plan, and Attio has changed its plans before. Check the current allowance on Attio's pricing page and estimate usage from the number of blocks per run times your expected runs per month.

For anything a workflow can't do on its own, Attio has a REST API and outbound webhooks. Here is what the developer docs say about each.

To check that a webhook came from Attio, recompute the HMAC-SHA256 of the raw body with the webhook secret and compare it with the Attio-Signature header. Attio also sends the same value as X-Attio-Signature for older middleware. Use the Idempotency-Key header to skip messages you have already processed, so a retry doesn't create a second task or Slack message.

Attio has a Slack app for notifications and an official Zapier app. Zapier lists ready-made connections between Attio and helpdesks such as Zendesk and Intercom. For more control, connect a helpdesk to Attio's API and webhooks through n8n or Make. Here is a common pattern, described as steps. It shows how the pieces fit together. It isn't a TascaLab case study.

1. Trigger: your helpdesk sends a webhook to n8n or Make when a ticket is created or escalated.
2. Look up: the workflow finds the customer's company record in Attio through the API, staying within the 100 reads per second limit.
3. Update: it writes the ticket's status or category to an attribute on the record, or creates a task for the account owner.
4. React in Attio: an Attio workflow triggered by that record update sends a Slack message to the account owner.
5. Handle errors: wait and retry on HTTP 429, and use the Idempotency-Key header to drop duplicate webhook deliveries.

TascaLab connects tools like Attio to the helpdesk and chat tools you already use, through APIs, webhooks, n8n and Make, with no platform switch. Custom Automation projects cost from $1,200. Most setups take 1 to 3 weeks, and every project includes basic documentation and 30 days of post-launch support. You can start with a free 30-minute Health Check call.