36 nodes
Source, compose, logic, output
4 products
One shared canvas
under 20 min
A 100-SKU creative run
1 recipe
Build once, run forever
How it works
Trigger, steps, approval - one engine
The same canvas powers every product's workflows. Learn it once.
- 01Pick a triggerAn event, a segment or signal change, a record update, or a schedule. The trigger is part of the workflow, not a cron somewhere else.
- 02Chain the stepsAny product's actions on one canvas - route data, generate assets, run journeys, move deals - with branches and waits in line.
- 03Approve, then runHold any step at an Approval Gate until you clear it. Blu drafts the steps; you keep the strategy and the sign-off.
Across your stack
The same workflows, in every product
Each product's workflow page used to live on its own. Here they are as worked examples on one page - pick the one that matches your job.
Your data, your destinations, your rules.
Route records to your own Kafka, webhooks, CRM, and messaging. The Data Engineer agent runs the recipe, you keep the destination - topic routing, partition keys, JSON or Avro.
Your cluster, your topics, your format.
Point a workflow at brokers you run. Ordered routing rules decide which record goes to which topic, first match wins, and the rest fall through to a default.
- Ordered topic routing rules, first match winsSet a rule per topic; the first match sends the record, and anything left over falls to your default.
- Partition key under your controlDefaults to the record ID, but you can override it per topic when a consumer needs a different key.
- JSON or AvroPick the format your consumers already parse and paste the writer schema in. No registry to stand up.
Everything else you already send to.
Webhooks, CRM writes, Slack, email and SMS run from the same canvas. Kafka is one destination among the ones you already use, not a separate product.
- Webhooks in and outReceive an inbound webhook or fire one out, from the same canvas as every other destination.
- CRM and spreadsheet writesPush a field update or a new row without a separate sync tool watching for changes.
- Messaging and email destinationsSlack, SMS and email sit next to Kafka as ordinary destinations, not a different product to configure.
Triggered by data, not by a schedule.
A workflow fires when a record changes, when an event arrives, or on a schedule if that is what you want. The trigger is part of the workflow, not a separate cron somewhere else.
- Event, record-change and scheduled triggersFires on an incoming event, a record changing, or a schedule - whichever matches how the data actually arrives.
- Branching and waits inside one canvasSplit the path on a condition or hold for a delay, without leaving the workflow you started in.
- Runs visible per recordOpen a record and see which branch it took and why, rather than an aggregate success count.
What gets routed, and where it lands.
Four destinations that need no code between the event and the consumer.
Common questionsquestions.
Everything you need to know about workflows across Intempt.