Getting Started With Blocks
Learn how Builders workflows are assembled from triggers, actions, logic and design blocks.
How to think about blocks
A workflow normally starts with a trigger, then moves through process, integration, condition and output blocks. When adding blocks, ask what starts the process, what data is needed, whether the workflow branches, and which external service should receive the result.
Data contract
Every executable block receives the previous block output plus workflow context such as run, input, files, project resources and Vault references. Most text fields support template expressions like {{input.email}}, {{run.id}} or values produced by earlier blocks. Treat the output of each block as JSON unless the block explicitly writes a file, sends a message or returns an HTTP response.
Output formatting
Use Transform or Render Block when downstream blocks need a stable output shape. Transform is better for JSON objects and arrays. Render Block is better when the workflow needs a final text, HTML, Markdown or structured response body. Code can format anything, but it should be reserved for logic that cannot be expressed safely with configuration fields.
Useful first path
- Add a trigger block.
- Add a Transform block to make the data shape explicit.
- Add one action or integration block.
- Add an If, If / Else or Switch block if the workflow needs routing.
- Publish and review logs with safe test input.