Action Cards

An action card represents one configured step in a Workflow.

The compact canvas view is designed to let a builder understand the flow quickly: cards show an action type or icon, a name and a short description of what that step is intended to do.

What a card tells you

A card is useful for orientation, but it is not the full configuration.

Use the visible card to answer:

• what kind of step is this?

• what is the step called?

• what is its intended role in the process?

• what comes before and after it?

Open or select the action when you need to inspect the actual configuration, inputs, outputs, bindings or action-specific settings.

Cards can represent different kinds of work

A Workflow can combine integration actions, data and flow-control actions, AI or Agent actions, and human handoff steps. Their detailed configuration differs, but they share the same role on the canvas: one executable step in the defined path.

Trigger and output-style actions can behave differently from ordinary middle steps, so do not assume every card exposes identical controls or connection points.

Names and descriptions matter

Give actions names that explain their operational meaning. A Workflow full of generic labels is hard to inspect and harder to debug later.

The card description is a concise explanation of intent. Treat the underlying configuration as authoritative for what the step actually does.

Test the behaviour, not the picture

Use the Workflow Run surface to test the draft and inspect the resulting execution. Do not assume that an isolated-looking test is harmless: Workflow runs can call real external systems and produce real side effects.

If a step fails, inspect the run or trace evidence and its input/output rather than relying only on the visual state of the card.