KreaStack
  • Features
  • How it works
  • Pricing
  • About
  • Sign in
  • Get started
Getting started
5 pages
Account & organisation
4 pages
Inbox
2 pages
Projects
5 pages
Studio
3 pages
AI agents
7 pages
Automation
FlowsWorking on the flow canvasStep typesEngine room, event types, travellers and executionsJourneys: registration, login, verification, onboarding, checkoutBind a journey to your siteWebhooks and credentialsFunctions
APACS
6 pages
Websites
13 pages
Publisher & newsletters
2 pages
Webstore
6 pages
Affiliate programmes
2 pages
Courses, webinars & bookings
3 pages
Marketplace, directory & community
3 pages
Marketing & research
3 pages
Integrations & credits
4 pages
Support & help
3 pages
  1. Help Centre
  2. Automation
  3. Working on the flow canvas
Automation 1   Updated 14 Sep 2026

Working on the flow canvas

Step by step — add steps, connect them, configure each one, use data placeholders, save, test and read the execution.

1. Open or create the flow

/flows → New flow (name, purpose, trigger type) or Edit on an existing one. The canvas opens with a Source step: every traveller enters there.

2. Add steps

Drag a step type from the palette onto the canvas, or click one to drop it near the selected step. Each step shows its inputs on the left and outputs on the right. The full list is in Step types.

3. Connect them

Drag from an output to the next step's input. A step with two outputs (a condition, a split test, a register step) needs both connected, or the second path ends the run. Delete a line by clicking it.

4. Configure a step

Click a step to open its settings. Every text field accepts a placeholder that reads the traveller's data:

  • {{data.email}} — a value collected earlier
  • {{data.order.total}} — nested values
  • {{data.webhook.json.id}} — what an inbound webhook posted

The Set data step is where you compute a value once and reuse it by name.

5. Save and test

Save writes the flow. Run it yourself: open the page URL for a web flow, post to the webhook address for a webhook flow, or use Run now for a scheduled one. Then open /executions and read the run step by step — the data at each step, and the first error if one stopped it.

6. Waiting steps

A delay, async wait or agent invoke step parks the traveller. You will find it in /travellers with what it is waiting for; the engine resumes it when the wait ends.

Common mistakes

  • A condition with only the true output connected: false runs end silently. Connect both.
  • A placeholder for data that no earlier step collected: it renders empty. Check the execution's data view.
  • Editing a flow that has travellers in flight: they continue on the steps they were on; new steps apply to new travellers.
Was this helpful?Thanks for your feedback!
Related pages
Flows Step types Engine room, event types, travellers and executions Journeys: registration, login, verification, onboarding, checkout Bind a journey to your site

Still need help?

Open a Support Ticket All help pages
KreaStack

A short tagline for KreaStack — replace this in the CMS to describe what your site does.

Product

  • Features
  • How it works
  • Pricing
  • Affiliate program

Company

  • About
  • Contact
  • FAQ
  • Support

Legal

  • Terms of service
  • Privacy policy
  • Anti-spam
  • Disclaimer

Trusted infrastructure

Stripe payments SSL secured CDN delivered 99.9% uptime
© 2026 KreaStack. All rights reserved. Crafted with care · V26.08