01 / Receive
Add Workflow invoked
Place the trigger on the target workflow and give it a channel such as enrich-company.
Attio App SDK · Workflow automation
Workflow Chain for Attio
Version 1.0 · Submitted for Attio review · August 2026
Trigger an Attio workflow from another Attio workflow. Pass a record, payload and source run context without checkbox handoffs or external automation tools.
The 60 second overview
What it adds: one trigger block and one action block that let workflows call reusable subflows natively inside Attio.
What it replaces: checkbox handoffs, polling automations and external tools used only to bridge two Attio workflows.
What leaves Attio: nothing. The app uses Attio hosted App SDK capabilities and requires no API key, OAuth connection or external service account.
01 / How it works
A small primitive for much larger systems.
Workflow Chain adds two native blocks to Attio. A channel connects them. Everything else stays inside the workflow editor you already use.
02 / Call
Add Trigger workflow
Place the step on the source workflow. Use the same channel and optionally attach a record or payload.
03 / Continue
Use the outputs
The target receives the payload, record reference and source run metadata as native workflow outputs.
02 / In Attio
Visible, testable and traceable.
Every screenshot below comes from the working Attio sandbox used to validate the integration.
03 / Documentation
Setup takes two blocks and one shared channel.
Installation
Once Workflow Chain is available through the Attio App Store, a workspace admin can install it from Workspace settings, then Apps. After installation, the two blocks appear in the Workflow Chain section of the workflow block picker.
The current release uses only Attio hosted App SDK capabilities. It requires no API key, OAuth connection or external service account.
Configuration
Target workflow
- Create or open the workflow that should be called.
- Select
Workflow invokedas its trigger. - Enter a unique channel name.
- Add the remaining steps and publish the workflow.
Source workflow
- Add
Trigger workflowwherever the handoff should occur. - Enter the exact same channel.
- Optionally map an Attio record and a text or JSON payload.
- Publish and run the workflow.
Channel names are trimmed and normalized to lower case. One active target can own a channel inside a workspace.
Available outputs
| Output | Description |
|---|---|
| payload | The optional text or JSON value sent by the source. |
| record_id | The Attio record identifier when a record is provided. |
| object_slug | The standard Attio object associated with the record. |
| source_workflow_id | The identifier of the calling workflow. |
| source_workflow_run_id | The identifier of the calling run. |
| source_workflow_title | The current title of the calling workflow. |
| source_workflow_url | A direct link to the calling workflow. |
| source_run_url | A direct link to the calling run. |
Behavior and limits
- The source step waits for Attio to accept the target invocation, not for every target step to finish.
- Each source execution sends a unique idempotency key to protect against duplicate delivery during retries.
- Temporary rate limits and server errors are treated as retryable failures.
- Removing or changing the target channel breaks the link until the source configuration matches again.
- Workflow automation credit usage remains governed by the workspace Attio plan.
Support
For installation help, unexpected workflow behavior or security questions, email alexy@buildrhaus.com. Include the source run URL and target channel. Never include Attio API keys or other credentials.
Terms and privacy
Workflow Chain is provided by Buildrhaus for use with Attio. The app does not operate external infrastructure and does not send workspace data to Buildrhaus or third party services. Configuration and routing data are stored using Attio hosted App SDK storage. Workflow payloads are passed through Attio provided workflow callback URLs.
Users are responsible for configuring channels, payloads and downstream actions appropriately. Availability may change as Attio evolves its App SDK. The service is provided without a separate uptime commitment. Buildrhaus may update the app to maintain compatibility, security and reliability.
General website terms and privacy information are available in the legal notice and privacy policy.
Built by Buildrhaus
Request a free diagnosticNeed more than one missing block?
We design and implement the complete revenue system around Attio, from data model to workflows, integrations and handover.