Getting started
Five steps from zero to an automated pipeline. This checklist is live — it checks off as your workspace grows. Flows can also live in your git repo as YAML (Flows → ⛓ Repo sync).
A connection holds the credentials for a system you want to talk to (a database, Slack, S3, Kafka…). Flows reference connections — secrets are stored once, never in the flow.
Connections → “+ Connect account” walks you through it and verifies the credentials work.
A flow is your automation: a trigger (manual, schedule/CRON, webhook, or message) followed by steps dragged from the palette.
Flows → name it → Create. Click palette items (or drag them) to add steps; click a step to configure it; hover any step for a summary bubble. The ✨ Copilot builds flows from plain English.
Run the draft before publishing. Step-through debugging pauses before every step so you can inspect inputs and outputs; mocks let you test without touching real systems.
In the designer hit ▶ Run — pick “step through” to debug. The run page shows each step lighting up live.
Publishing freezes the draft as the LIVE version — the one schedules, webhooks, and subscriptions execute. Drafts keep evolving separately.
Designer → Publish. The flow list shows live vs draft versions.
Subscriptions start your published flow automatically: a Kafka/NATS/RabbitMQ/Pulsar topic, a database change (Mongo change streams), or an outbox. Schedules and webhooks configure on the flow itself (Settings → trigger).
Subscriptions → “+ New subscription” — pick the broker connection, subject, and flow.