Overview of workflows
Understand what workflows are and how they're structured in Attio.
Available on all plans.
Available for all workspace members.
Workspace credit limits depend on your Attio plan.
A workflow is a set of automated rules that runs inside Attio: when something happens, take these actions. Instead of manually updating records, sending notifications, or moving data between tools, you define the logic once and Attio handles it every time the conditions are met.
You can build workflows manually using the canvas, or describe your goal in plain language and let Ask Attio construct it for you.
Each run consumes workspace credits, and how many depends on the complexity of the workflow. Learn more about how workflows consume credits.
How a workflow is structured
Every workflow is made up of a trigger and one or more steps.
A trigger is the event that starts a workflow. Triggers include events like a record being created or updated, an attribute changing value, a recurring schedule, or a webhook from an external tool.
Steps define what the workflow does once it's triggered. Each block performs one operation: updating a record, creating a task, sending a Slack message, enrolling someone in a sequence, making an HTTP request, and so on.
You chain blocks together on the canvas to build the full logic you need. Some blocks apply conditional logic, such as a filter that stops the run if certain conditions aren't met, or an if block that routes the run down different paths.
What you can build
Workflows handle a wide range of automation use cases. For example, you could automatically notify your sales team in Slack whenever a deal is marked as won, or assign new leads to team members on a round-robin basis, or enroll a contact in an email sequence the moment they hit a specific stage in your pipeline.
Learn more about workflows
To start building, see Create a workflow for a step-by-step walkthrough of building and publishing your first workflow.
For a reference of every available trigger and step, see the Workflows block library.
Once your workflow is live, you can review individual runs, see what each block executed, and debug errors using the run viewer.