Build your first workflow
Create a live HTTP endpoint and inspect its first run.
Understand workflows
Learn how triggers, actions, dependencies, and runs fit together.
Connect an integration
Add an external account, review its permissions, and see where it is used.
Browse every node
Open the complete action and trigger reference.
The core model
Projects contain your automation system
A project is the boundary around workflows, connected accounts, persistent variables, team access, run history, and billing. Data and accounts are scoped to a project, so choose the project before creating or connecting anything.A trigger starts each workflow
Every workflow has one trigger. It might receive an HTTP request, observe a new email or form response, run on a schedule, or accept a call from another workflow. The trigger provides the first values in the graph. An incoming HTTP request, for example, can expose its method, path, query parameters, headers, body, and uploaded files.Actions run when their dependencies are ready
Actions are nodes on the editor canvas. Connections carry values from outputs to inputs and establish execution dependencies.A workflow is not read from left to right or top to bottom. An action runs
when the values it depends on are ready. Independent branches can run at the
same time.
Every execution becomes a run
A run records the trigger data, status, node outputs, and node errors for one execution. Use Run History to understand what happened, inspect a historical snapshot, and rerun with the same trigger payload after making a change.A practical learning path
1
Create one small end-to-end workflow
Follow the Quickstart to receive a URL request, build a
message, and return an HTTP response.
2
Learn how data moves
Read Connect data before building larger graphs.
It explains static and dynamic inputs, connections, lists, objects, and
required values.
3
Add control and reuse
Use Meta controls,
branching, lists and
loops, and
sub-workflows as the automation grows.
4
Test with real events
Use Testing workflows and Run
History to inspect actual inputs, outputs, and
errors.
5
Operate it safely
Understand Live and Paused workflows,
account health, project variables, usage, and external-trigger lifecycle
before relying on the automation in production.