Overview
Workflow Chain adds native workflow chaining to Attio. Use one workflow to start another, pass a record or payload, and keep the complete source run context attached to every handoff.
Replace checkbox workarounds and external automation tools with two blocks that live inside the Attio workflow editor. Workflow Chain is designed for reusable enrichment, qualification, routing and operational subflows.
The app runs entirely on Attio hosted App SDK capabilities. It requires no API key, OAuth connection or external service account.
How it works
Add Workflow invoked as the trigger on the target workflow and assign a unique channel.
Add Trigger workflow to the source workflow, enter the same channel, then optionally map an Attio record and a text or JSON payload.
When the source step runs, Workflow Chain looks up the registered target and sends the invocation through the callback provided by Attio. The target receives the payload, record reference, source workflow identifier, source run identifier, titles and direct URLs as native outputs.
Each call includes a unique idempotency key. Temporary rate limits and server errors are treated as retryable failures.
Configure
No external configuration is required after installation.
For each target workflow, choose a unique channel in the Workflow invoked trigger and publish the workflow. Then use that exact channel in every Trigger workflow step that should call it. Channel names are trimmed and normalized to lower case. One active target can own a channel inside a workspace.
The record and payload fields are optional. Workflow automation credit usage remains governed by the workspace Attio plan.
Full setup instructions, output definitions, behavior notes, support and privacy information are available in the Buildrhaus documentation.