Automation recipes
Recipes combine Triggers, Actions, mappings, Paths, and Audit into one observable business outcome. Complete the Quickstart first if you have not built a Workflow yet.
Send a Slack message for each new Google Sheets row
Learn a linear two-app automation. Configure a Google Sheets Source, map named row columns into Slack text, activate the Workflow, and verify the provider output.
Create a Linear issue from a GitHub issue
Connect two development tools. Restrict the GitHub Source to issue events, map repository and issue fields into Linear, and prevent non-opened actions from creating duplicates.
Route Stripe events through conditional Paths
Learn multi-route automation. Subscribe one Source to several Stripe event types, split by trigger.type, add a fallback, and inspect selected and skipped branches.
Save webhook payload fields to Google Sheets
Receive an HTTP webhook, map a controlled set of fields into a two-dimensional row value, and verify both Workflow evidence and the appended spreadsheet row.
Transform a webhook before an API Action
Normalize a webhook with JSON Patch, then map the transformed output into a provider Custom API Request.
Handle a failed Action through an error route
Create a safe terminal failure, connect its Error output, map the normalized error envelope, and distinguish recovered routing from business success.
Send a delayed follow-up
Send an immediate Slack message, wait with a durable Delay Step, and deliver an idempotent follow-up using stored or freshly looked-up data.
Troubleshoot a failed Workflow run
Trace Trigger evidence, the first failed Step, mapped input, retry state, skipped routes, and safe recovery before repeating a side effect.
Recipe design rules
- Give Workflows outcome-oriented names.
- Restrict Trigger definitions before adding broad downstream Filters.
- Map with the field picker and test more than one real payload shape.
- Add a fallback or error route for events that need an explicit operational outcome.
- Verify success in both Workflow Audit and the destination app.
- Design side-effecting Actions to tolerate provider retries and operator replays.