Actions and steps: what a workflow does

A step is one job in a workflow. It takes in some data, does its job and puts out new data for whatever comes after it.

What you need

• The job in plain words, one verb at a time: look up, create, send, change, wait.
• The account or connection for each app the step touches.
• A sample of the data the step will receive. Most editors let you run a test to see it.

What a step can do

The makers sort steps by what they do. n8n's glossary says some nodes start workflows, while others fetch, send and process data, define flow control logic, or connect with external services.¹

In plain terms, steps tend to fall into these groups:

• Fetch. Look something up, such as a contact or a row.
• Send or write. Create a record, post a message, upload a file.
• Change the data. Reformat a date, join two fields, split a list.
• Control the flow. Stop, choose a path, wait, or repeat. The filters and branches page goes into these.
• Call another workflow. n8n describes a sub-workflow as a workflow that another workflow calls.¹

How steps pass work along

Each step gets the output of the one before. n8n's page on referencing data says this allows you to use output from earlier steps as input for later nodes.²

Make describes the same thing with its own words. An input bundle is the data a module receives, and an output bundle is the module's response data. That process repeats throughout the scenario.³

Later steps can usually reach back further than the step right before them. A later page, on field mapping, covers how.

One item or many

A step may get one item or a whole list. In Make, modules process each bundle separately, and each bundle triggers its own module run.³ So a list of ten contacts means ten runs of the next module. This is why a step that fits one record can behave very differently when the trigger hands it a batch.

What counts as work

Zapier counts a task as any successful action that runs in Zapier.⁴ Steps that error or halt don't count, and neither do steps that never run because of an earlier filter or path condition.⁴

That's a billing rule. It says nothing about whether the job got done. A failed step still didn't do its job, so read the run history. Always.

Limits to look for

Tools cap how big one workflow can get. Zapier's Paths page, checked on 4 November 2026, says Zap workflows are limited to 100 steps total, including all steps within paths.⁵ Limits like this change, so check the current docs for your own tool.

Keep each step small and name it for its job. When a run goes wrong, a short list of one-job steps is far easier to read than a few big ones.