How-to

Attio New Workflows: June 2026 Relaunch Guide

9 min read Published

Overview

Overview

Attio relaunched Workflows in June 2026 as a new automation engine that sits alongside Legacy Workflows. The headline changes are plain-English building through Ask Attio, agents that can read across the stack through MCP, and a pricing model where about 9 in 10 block runs are now free.

This guide is for teams already on Attio, teams evaluating Attio, and teams sitting on dozens of Legacy Workflows wondering whether the migration is worth the work. The short version: existing Legacy Workflows do not need to move immediately, but the economics and migration path changed enough that high-volume workflow users should re-check the math.

The dates matter. Attio stopped creation of new Legacy Workflows after 2026-06-09. Legacy Workflows still run and remain editable, but new automation work now belongs in the new engine.

New engine

What ships in the new engine

The June 2026 release changes both how teams build workflows and what a workflow can reach. A handful of authoring upgrades do the heavy lifting, and each one removes a workaround that used to force teams into duplicate workflows, split branches, or off-platform scripts.

Multiple triggers per workflow

One workflow can now start from several trigger events. A play that used to require four near-identical copies (one per entry point) collapses into a single workflow with four triggers wired to the same body. This is the single biggest reduction in duplicate-workflow sprawl in the new engine, and it changes how you organize an automation library on day one.

Copy and paste blocks across workflows and workspaces

Copy and paste now works at the block level, not just the workflow level. Grab a configured block, or a chain of blocks, and drop it into another spot in the same workflow, into a different workflow, or into a different workspace entirely. Teams standardizing the same play across a production workspace, a sandbox, and client workspaces get a real time saver here instead of rebuilding the block config by hand each time.

Variable fallbacks inside a single node

A variable slot can now chain fallbacks in one node: try the primary field, and if it is empty fall back to a second field, then a third, and so on. This is not a static default value, it is a live waterfall across real fields. The old pattern of adding a Filter, splitting into two branches, and rejoining downstream just to handle a missing name or email goes away.

Ecosystem apps ship custom blocks

Third-party apps built on the Attio App SDK can now ship installable workflow blocks. That extends the block library without waiting on Attio to build every integration first. Neon Deer's own Advanced Automation Utilities for Attio is one of these apps, alongside Attio's Lemlist and Fin examples.

Branches can re-merge

When a workflow splits (through Switch, a Filter with two paths, or parallel branches), the branches can now re-join into a single downstream flow instead of each living its own life to the end of the workflow. That means shared post-branch steps (logging, notifications, cleanup) get written once, not duplicated at the tail of every branch.

Replay a run against the current workflow

Any completed or failed run can now be replayed against the live version of the workflow. The Retry menu on a run exposes a Retry with live workflow option that creates a new run using the current workflow definition and the same trigger output as the original, edits included. That closes the iteration loop in a way Legacy Workflows never did: see a run that failed or produced the wrong output, patch the workflow, and rerun the exact trigger data against the fix, without having to wait for the same trigger conditions to fire again. For debugging production automations, this is the change most teams will feel first.

The rest of the release rounds out the builder and the runtime:

  • Ask Attio builder. Build workflows in plain English, including migration prompts for an existing Legacy Workflow.
  • Custom Agents. Define an agent with a goal, tools, and data access. The agent can plan and execute research or retrieval work, but it is read-only.
  • Web Agent. Use Attio's pre-built record research agent to pull web context such as funding, hiring, and news signals into the research flow.
  • MCP integration. Let agents read connected tools such as Notion, Granola, Linear, and Slack through Model Context Protocol connections.
  • Operations controls. Pause, cancel, or resume workflows already in flight.
  • Code block. Run custom code inside a workflow when the native blocks do not cover the transformation.

Pricing

The pricing shift

About 9 in 10 block runs are now free. That is the main value story in the new Workflows engine, especially for teams whose Legacy Workflows spent credits on lookups, branches, delays, and control flow before any real write happened.

In the new model, free blocks include all triggers, all logic, all lookups, and all tool calls. Paid blocks are the moments where a workflow writes data, sends externally through Slack or webhooks, runs AI, or executes code. Non-AI paid blocks cost 1 credit. AI blocks are now priced on actual token usage instead of the flat 10-credits-per-question model in Legacy Workflows.

Attio also separates seat credits from workspace credits. Seat credits fund user-initiated actions, such as using Ask Attio to build. Workspace credits fund anything a Workflow runs on its own, including AI blocks. For current rates and plan packaging, check Attio pricing (checked 2026-07-14).

Block type Legacy pricing New pricing
Internal triggers Free Free
External triggers (webhook, Typeform) Free Free
Data lookups 1 credit Free
Conditional blocks (Filter/If/Switch) 1 credit (free only as terminal) Free in all positions
Delay 1 credit Free
Loop Free (inner blocks cost) Free (inner blocks follow new rules)
Other control flow (broadcast, round-robin, random) 1 credit Free
Data writes 1 credit 1 credit
External pushes (Slack, webhooks, sequences) 1 credit 1 credit
AI blocks 10 credits per question (fixed) Variable (token-based)
Code execution Not available 1 credit

Migration

Migration path and client outcome

Customers do not have to migrate immediately. Legacy Workflows keep running and remain editable. New pricing applies to new Workflows, not to Legacy Workflows that keep running on the old engine.

The hard cutoff is creation. No new Legacy Workflows can be created after 2026-06-09. Legacy Workflows will eventually be sunset, but Attio has not announced a date and says customers will get ample notice.

Ask Attio can migrate a Legacy Workflow when you point it at that workflow and ask it to rebuild the logic in the new engine. That changes the project shape for teams with many old workflows. The work is still review, testing, and cleanup, but it is no longer a blank-page rebuild.

Agent boundaries

Ask Attio vs Custom Agents

Use Ask Attio to build workflows. If the outcome needs to create, update, or send data, the writes should happen through workflow blocks that Ask Attio composes and that your team reviews before relying on them.

Use Custom Agents for read-only work: planning, research, summarization, and retrieval across CRM and connected tools. Custom Agents can reason over data and tools, but they do not write back to the CRM. The Web Agent is Attio's pre-built record-research example of this pattern.

The boundary is simple. If you need action, build a Workflow. If you need context, research, or a recommendation, use a Custom Agent.

App SDK

Ecosystem Blocks

Attio's Ecosystem Blocks let third parties ship installable workflow blocks through the App SDK. That matters because it moves common automation gaps into the workflow builder instead of forcing teams into one-off webhooks or external scripts.

Neon Deer ships one of these blocks-based apps: Advanced Automation Utilities for Attio. The app doc covers the trigger and action inventory, so this guide will not repeat it here.

Next steps

Where to go next

If you are evaluating the new engine, start with the vendor docs, then map your highest-volume Legacy Workflows against the pricing table above. The goal is not to migrate everything first. It is to find the workflows where free lookups, free logic, token-based AI pricing, or Ask Attio migration will change the operating cost.

FAQ

Frequently asked questions

Do I have to migrate my Legacy Workflows?

No. Legacy Workflows keep running and can still be edited. Attio stopped creation of new Legacy Workflows after 2026-06-09, so new automation work should happen in the new engine.

When will Legacy Workflows be sunset?

Attio has not announced a sunset date. Attio has said it will give ample notice before Legacy Workflows are retired.

Are AI blocks cheaper now?

Sometimes, but not always. Legacy Workflows charged a fixed 10 credits per AI question. New Workflows price AI blocks on actual token usage, so the cost depends on the prompt, context, and model work required.

Can Custom Agents write back to my CRM?

No. Custom Agents are read-only. Use Ask Attio to build a Workflow when the automation needs to create, update, or send data.

Can I migrate multiple Legacy Workflows at once?

Each instance of Ask Attio migrates Legacy Workflows one at a time, but multiple can be run simultaneously across browser tabs. In practice, we've found that migrations run quite fast, with simple flows taking a minute or two to transition.

Can I fix a workflow and rerun a failed run against the fix?

Yes. The Retry menu on any run exposes a "Retry with live workflow" option that creates a new run using the current workflow definition and the same trigger output as the original. Edits made after the run finished are included. Legacy Workflows do not support this. A rerun there executes the workflow as it existed at trigger time.

Where do I see current credit pricing?

Use Attio pricing for current credit rates and plan details: https://attio.com/pricing. This page last checked that source on 2026-07-14.

Sources

Sources checked

Attio's Workflows surface and credit model can change. These are the vendor sources used for this guide, with the date checked. For current pricing, trust Attio's pricing page over any dated summary.

Published

Thinking about migrating?

If you have Legacy Workflows to move, we can help scope the migration, rebuild the risky automations, and check the credit impact before your team changes production workflows.

Scope an Attio migration