Glossary · Workflow design
Action
Also called: workflow step, action step, task
An action is a workflow step that does something outside the workflow, such as creating a CRM record, sending an email, posting to Slack or calling an API.
If the trigger is the "when", actions are the "do". A typical workflow is one trigger, a few logic steps (route, check, transform) and one or more actions that change something in another system.
The distinction matters for two practical reasons.
Pricing. Task-based tools count actions. On Zapier, each successful action step in each run is a task, so a five-action Zap uses five tasks per run; logic steps like Filters don't count. Knowing which steps are "actions" to your vendor is how you predict the bill.
Risk. Actions are where side effects live. A Router that sends data down the wrong branch costs nothing; an action that emails the wrong customer or updates the wrong deal does. That's why careful workflows put checks and approvals immediately before the risky action, not at the start.
Good action design
- Make it safe to repeat. Prefer "create or update" (an upsert) over "create", and pass an idempotency key where the API accepts one.
- Map fields explicitly. Don't pass a whole AI output into an API body; pick the fields and validate them first.
- Decide what failure means. Retry, skip the item, or stop the run and alert someone: each action should have an answer.
In Fluxo Flow
On the canvas, actions are Action nodes (HTTP Request, Webhook Call, Send Email, Slack Post), Integration nodes that call a connected app's actions (like HubSpot's "Create or update a contact"), Sub-workflow and Output steps. Each action node has retries with exponential or fixed backoff and a failure behaviour (stop, skip or continue). Dry Run simulates every action, so nothing is sent while you test. Fluxo Flow doesn't count actions: plans limit workflows and seats, not steps.
Read next
Related terms
- TriggerA trigger is the event that starts a workflow run: a person pressing Run, a schedule coming due, a webhook arriving, or a new record or event in a connected app.
- WorkflowA workflow is a repeatable sequence of steps, started by a trigger, that turns an input (a form, an invoice, a new deal) into an outcome, with defined rules for each decision along the way.
- Sub-workflowA sub-workflow is a workflow that another workflow calls as one of its steps, passing data in and getting a result back, so shared logic is built once and reused.
- Dry runA dry run executes a workflow end to end with its side effects simulated, so you can see what every step would do without sending, writing or charging anything.
- Agentic workflowAn agentic workflow is a workflow with a fixed overall structure in which some steps use a language model to read, classify, decide between predefined branches or draft content.