How to Automate Follow-Ups in Attio With Workflow Rules
Attio workflows automate what happens when a record changes: a deal sits untouched for 7 days, a new lead lands, a stage flips. You build a trigger-plus-action rule once and it runs on every qualifying record. Workflows are a paid feature, so this assumes you are past the free tier.
Done well, the rules replace the mental checklist a rep carries. Done badly, they spam your team with notifications nobody reads. The difference is picking triggers that represent real signals.
What can an Attio workflow actually do?
A workflow has a trigger, optional conditions, and one or more actions. Triggers are record events — created, updated, attribute changed, or a time-based check like “no activity for N days.”
Actions create tasks, update attributes, send Slack messages, or call a webhook. That webhook is the escape hatch to anything Attio cannot do natively.
How do you build a stalled-deal rule?
- Open Settings, then Workflows, then New workflow.
- Set the trigger to “deal not updated for 7 days.”
- Add a condition: Stage is not Closed Won or Closed Lost.
- Add an action: create a task assigned to the deal owner, due today.
- Add a second action: post a Slack message to the sales channel.
- Publish and enable. It evaluates existing records on the next cycle.
Keeping the stage condition in there prevents the rule from nagging about deals you already closed — the single most common mistake.
What triggers are worth using?
| Trigger | Good for | Risk |
|---|---|---|
| Record created | Welcome tasks, data enrichment | Fires on imports too |
| Attribute changed | Stage-based playbooks | Loops if the action edits the same attribute |
| No activity for N days | Stalled-deal nudges | Noisy if N is too low |
| Scheduled | Weekly digests | Needs a solid filter or it floods |
Avoid a workflow that both triggers on and modifies the same attribute. That is a loop, and Attio will happily keep firing it.
How do you use webhooks productively?
Send a JSON payload to your own endpoint when a stage hits Qualified. From there you can enrich the company, post to a data warehouse, or trigger an email sequence in a dedicated tool. Webhooks keep Attio as the system of record without forcing every integration into its native list.
How many workflows should you run?
Fewer than you think. Three to five well-chosen rules cover most teams: new lead intake, stage-change playbook, stalled-deal nudge, and a scheduled digest. Every rule you add is one more thing to debug when a notification misfires.
Audit monthly. A rule that has not fired usefully in weeks is dead weight and should be disabled, not left running.
Who benefits most?
Small sales teams without a dedicated ops person, where a rep also does the CRM admin. If you have one salesperson and five deals a month, manual follow-up is honest and lighter than maintaining automation. Automate when volume makes manual tracking slip.
Quick Summary
- Attio workflows pair a trigger, optional conditions, and actions to automate CRM follow-up.
- Workflows are a paid feature; the free tier covers core records and views only.
- A stalled-deal rule needs a stage condition so it ignores closed records.
- Never combine a trigger and an action on the same attribute — that creates a loop.
