Skip to main content
Reference pages tell you what a block does; these pages explain why the Attio Workflows engine behaves the way it does. Read them when a reference page raises a “but why?” question. They cover the mental models that stop you building workflows that silently misfire, double-charge, or loop forever.

The engine

What are Attio Workflows?

The trigger-then-blocks-then-run model, and where workflows live in the workspace.

What's new in the 2026 Workflows engine

Agents, code, multi-trigger workflows, and the repriced credit model.

Choosing the right trigger

Picking a record, attribute, schedule, webhook, or command trigger, and the one distinction that trips everyone.

Variables & data passing

How an earlier block’s output becomes a later block’s input.

Conditions & filters

If, switch, and filter, and why a condition that stops a run costs nothing.

Records vs list entries

The distinction that decides which trigger and which block you reach for.

Running, scaling, and governing

Runs, debugging & publishing

What a run is, and how to read one in the run viewer.

Loops & processing many records

Why loop contents dominate the cost of most expensive workflows.

Infinite loops and safety

How a self-triggering workflow burns credits until someone notices, and how to prevent it.

Permissions & workflow access

What a workflow can read and write, and the “Run as” model.

Workflow governance

Naming, ownership, and change control once you have more than a handful.

Credits & pricing explained

The canonical credit table, plan allowances, and timeout numbers for every block.