Skip to main content
The Attio Workflows Handbook is a community-maintained, source-backed guide for people building go-to-market systems in Attio. It is written by Dan Hull, who builds Attio workspaces for venture capital (VC) funds and startups full-time. The handbook is not affiliated with or endorsed by Attio Ltd. For how the product behaves, the official Attio Help Center is still the source of truth. What the handbook adds on top is implementation judgment: how to actually build these systems well. You get patterns, step-by-step recipes, migration checklists, cost tradeoffs, and go-to-market (GTM) examples. Use the four modes below to find what you need. You can also skip to the contribution rules and license terms.

Learn Attio workflows

Follow the guided paths that take you from your first workflow to AI-owned pipeline stages.

Guides

Build real GTM workflows end to end, from webhook lead intake to funding-signal outbound.

Block reference overview

Look up every trigger and block with its inputs, outputs, credit cost, and gotchas.

How the engine works

Understand triggers, variables, loops, permissions, and the 2026 engine’s design.

Credits & pricing explained

Read the one canonical credit table and the cost model every other page links to.

Go Pro

Work with Dan directly on workflow builds, audits, and migrations.

​
Contribution principles

Good contributions raise the handbook’s accuracy and stay inside its scope. Follow these principles when you add or edit content.
  • Prefer tested workspace behavior over speculation.
  • Link to the relevant Attio Help Center page when you document product behavior.
  • Keep examples GTM-specific: pipeline, routing, enrichment, outbound, product signals, fund workflows, and customer operations.
  • Mark assumptions clearly.
  • Never publish private customer data, screenshots, or workspace-specific IDs.
  • Include the cost model and a safety guard whenever a workflow can burn credits at scale.

​
Good first contributions

These changes are small, high-value, and a good place to start.
  • Add a missing block gotcha.
  • Add a recipe from a real GTM workflow.
  • Improve a migration note for a legacy block.
  • Add a troubleshooting error and its exact fix.
  • Update a page when Attio changes a block’s behavior.

​
Verification standard

Each block reference page aims to carry the same six elements. That way you can trust a page at a glance.
  • The block type and credit cost.
  • The inputs and outputs.
  • When to use it.
  • Common gotchas.
  • One GTM example.
  • The official source link.
The goal is not to out-document Attio’s official reference. The goal is to make builders faster and safer.

​
Licensing

The handbook is dual-licensed. This lets the prose and the code travel on different terms.
  • Prose and documentation content carries the CC BY-NC-SA 4.0 license. You can share and adapt it non-commercially, with attribution, under the same license.
  • Code snippets, examples, and repository scripts carry the MIT license. You can use them anywhere, including commercial projects.
Full terms live in LICENSE.md. Do you want to use the prose commercially? That covers republishing, training datasets, or paid products. Email dan@80x.ai for a commercial license. “Attio” is a trademark of Attio Ltd, used nominatively to describe what the handbook documents.
The handbook is community-maintained and not affiliated with Attio Ltd; the Attio Help Center remains the source of truth for product behavior. Last reviewed against the Attio Help Center, June 2026.