Steps

A step does one piece of work. Good workflows make that work legible: each step has a clear name, a focused job, and an output the next step can use.

Open the step library in the workflow builder to browse everything available to your organization.

Start with the job

I need to…	Start with
Call an API	HTTP
Save a value for later in the run	Set Variable
Return a webhook, form, or sub-workflow result	Return
Choose a path or repeat work	Control Flow
Reuse another workflow	Sub-Workflow
Transform a list or object	Working with Data
Read, create, or share a file	Working with Files
Generate text or use tools with AI	AI Steps
Write custom TypeScript	Code

Use the dedicated integration steps for providers such as Salesforce, Google, Slack, and Five9. They expose provider-specific fields and behavior that a generic HTTP request would make you rebuild.

Media and communication

Email sends messages through an SMTP connection.
Audio converts, trims, combines, and inspects audio files.
Speech transcribes speech or generates spoken audio.
Crypto hashes, signs, encrypts, and verifies data.

Configure a step

Select a step on the canvas to edit it. Fields accept fixed values, data from earlier steps, and template expressions.

Name steps after their result: load-customer, create-ticket, and return-summary are easier to follow than http-1 or code-step.

After a test run, open the step in the execution trace and compare its resolved input with its output. This is the fastest way to learn a new step or diagnose a surprising template.

Build in small proofs

Add one behavior at a time:

Prove the trigger supplies the expected input.
Configure one step and test it.
Inspect its output.
Connect the next step.
Add branching and recovery after the straight path works.

For a complete example, follow Build Your First Workflow.