Workflows & cards
Building a flow, connecting steps, and what every one of the cards is for.
7 articles
- Building and saving a workflowTurn a one-off into something you can run again: add steps, save a draft, publish it, and it appears in Workflows with its own run, schedule, trigger and share actions.
- Connecting cards in Map viewEdges say what feeds what: a start into your items, items into a step, a step into the next, and anything into a gallery — with branches and joins where you need them.
- Card reference: all 17 cardsEvery card in the palette — what it does, when to reach for it, and the limit or cost worth knowing before you put it in a flow of two hundred items.
- Referring to data: {item.field}, {previous.text}, {step.X.text}Three placeholders let one instruction do two hundred different jobs — each item's own values, the step before, or any earlier step by name.
- The Data tab: rehearse a run for $0See exactly what every item will send, with your values already filled in, before a single provider call is made — and the real outputs in the same place afterwards.
- Duplicating, exporting and importing flowsCopy a flow to experiment safely, or move one between workspaces as a JSON file — with keys, pool bindings and webhook URLs deliberately left behind.
- Rebuild an ad so its words and typeface can changeTurn a finished ad image into text you can retype and a typeface you can swap — then re-render as many versions as you like for $0, with the artwork untouched.