Blocks reference
Every block in the Add a block palette: what it does, its settings, and what later blocks can use from it.
The Add a block panel in the builder lists these blocks, in this order. Triggers are on their own page. Conditions, filters and loops are covered in Conditions and lists.
At a glance
| Block | Kind | What it does |
|---|---|---|
| Record event | Trigger | Runs when a record is created, updated or deleted. |
| Schedule | Trigger | Runs on a cron schedule (UTC). |
| Manual | Trigger | Runs only when you press Run. |
| Calendar event | Trigger | Runs when an event is created, changed, cancelled, or a set time before it starts. |
| People event | Trigger | Runs when leave is requested, approved or rejected, or someone joins or leaves. |
| Condition | Logic | Branches true / false on the data. |
| Update record | Action | Sets fields on a record. |
| Create record | Action | Creates a new record. |
| Run function | Action | Runs one of your JavaScript functions. |
| HTTP request | Action | Calls an external API and lets you use the response later. |
| Create event | Action | Puts an event on a calendar, optionally inviting people. |
| Send message | Action | Sends an email, text or WhatsApp message through one of your Phone & Messages connections. |
| Delete record | Action | Moves a record to the trash. |
| Add to work queue | Action | Puts an item into a Work Queue for someone to pick up. |
| Post to Relay | Action | Posts a message in a team chat channel. |
| Notify people | Action | Sends teammates a notification. |
| Ask Axis | Action | Has Ask Axis look something up or write something, and passes on its answer. |
| Approval | Logic | Waits until a person approves or rejects, then continues on the matching branch. |
| Wait | Logic | Pauses for minutes, hours or days, then continues. |
| Merge | Logic | Joins branches back into one path, then continues once. |
| Filter list | Logic | Keeps the items of a list that match. |
| Summarize | Logic | Folds a list to one value (sum, count and so on). |
| For each | Logic | Runs the next blocks once for each item in a list. |
Update record
Changes fields on an existing record.
| Setting | Notes |
|---|---|
| Object type | The record type. Required. |
| Record to update | The id of the record. Defaults to {{trigger.record_id}}, the record that started the flow. Required. |
| Set fields | One row per field. Required: at least one field. |
In Set fields, click Add field, pick the field, then give its value. For a field with a fixed list of choices, or a yes/no field, you get a dropdown. For anything else you type a value or insert a reference. Click the {} button on a dropdown row to type a reference instead, and click it again to go back to the picker.
Fields filled in automatically (auto-numbered) and computed (formula) fields are not offered, because the system owns them.

Later blocks can use Update record · saved id.
Create record
Creates a record.
| Setting | Notes |
|---|---|
| Object type | Required. |
| Field values | Same editor as Set fields. |
Later blocks can use Create record · saved id, which is handy for linking the new record to something else.
Both record blocks run with the permissions of the person the flow runs as, including field-level hiding. A field that person cannot change cannot be set by the flow. See Who a flow runs as.
Run function
Runs one of your functions.
| Setting | Notes |
|---|---|
| Function | Pick from your functions. Required. |
| Input | Name/value rows passed to the function as its input object. Values can be literals or references. |
Later blocks can use Run function · result. The step fails if the function throws an error, times out, or the person the flow runs as is not allowed to run functions (Can run on Custom code). Function rules that apply to flows are on Limits and permissions.
HTTP request
Makes one web request to another system.
| Setting | Notes |
|---|---|
| Method | GET, POST, PUT, PATCH or DELETE. Default GET. |
| URL | Required. Must start with http or https. |
| Headers | Name/value rows. Values can be references. |
| Body | Free text, usually JSON. You can put references inside it, for example {"text": "{{trigger.record.name}}"}. |
- Only public addresses work. Addresses inside private networks, and local addresses, are refused.
- Each request has a 10 second time limit and a 1 MB response limit.
- A response that is not a success (for example 404 or 500) is not a failed step. It is data you can branch on. A connection error or timeout does fail the step.
- Later blocks can use HTTP request · status and HTTP request · body. If the response is JSON, you can reach inside it, for example
{{node.<id>.output.body.<field>}}. The output also holdsok(true for a 2xx status) andheaders.
Create event
Adds an event to a calendar.
| Setting | Notes |
|---|---|
| Calendar | My own calendar or one you can see. |
| Title | Text or reference. |
| Starts (date or date-time) | Text or reference. |
| Ends (optional) | Leave empty and use the length below. |
| Or length in minutes | Default 60. |
| Location, Description | Optional. |
| Invite (comma-separated emails) | Optional guests. |
| Link to record id (optional) | If set, also choose Linked record type. |
| All day | No — timed or Yes — whole day(s). |
Later blocks can use Create event · event id and Create event · start.
Send message
Sends one message through your own Phone & Messages account.
| Setting | Notes |
|---|---|
| Channel | Pick a Phone & Messages connection that is turned on. Required. |
| Recipient | An email address or phone number. Text or reference. Required. |
| Template | Optional. A saved template. Only templates for the chosen channel are listed. |
| Subject | For email. |
| Message | The text to send. You can put references inside it. |
| Link to record id (optional) | Attaches the message to a record so it shows on that record's Messages tab. |
- The message goes out through your connection, so your own provider account sends and bills it.
- It runs with the permissions of the person the flow runs as. See Who a flow runs as.
- Addresses on your suppression list are never sent to. See Suppressions and unsubscribe.
Delete record
| Setting | Notes |
|---|---|
| Object type | Required. |
| Record to delete | The record's id, for example {{trigger.record_id}}. |
The record goes to the trash and can be restored for 30 days. The person the flow runs as needs delete permission on that record type.
Add to work queue
| Setting | Notes |
|---|---|
| Work queue | Required. |
| Stage | Leave as First stage, or pick one. |
| Linked record id (optional) | Links the item to a record, for example {{trigger.record_id}}. |
| Item key | Identifies the item. An item already open in the queue with the same key is left as it is, so a re-run never adds it twice. |
Post to Relay
| Setting | Notes |
|---|---|
| Channel | A channel you are in. The flow posts as you. |
| Message | Markdown and references such as {{trigger.record.amount}} work. |
Notify people
| Setting | Notes |
|---|---|
| Notify | Up to 20 teammates. |
| Title | For example Big order from {{trigger.record.customer}}. |
| Details (optional) | Shown in the email or WhatsApp copy. |
It lands in their notification inbox. Email, WhatsApp and push follow each person's own notification settings.
Ask Axis
| Setting | Notes |
|---|---|
| Ask Axis to… | What to do, for example Summarise this customer's last 5 orders and suggest a follow-up: {{trigger.record.name}}. |
Use the answer in later blocks as {{node.<id>.output.reply}}. Ask Axis runs with the flow owner's permissions. It can read and update records, but it never sends messages, moves money, invites people or deletes anything from a flow — those always need a person to confirm.
Approval
| Setting | Notes |
|---|---|
| Who approves | One person. |
| What needs approval | A short title, for example {{trigger.record.discount}}% discount on {{trigger.record.number}}. |
| Details (optional) | More context for the approver. |
The run waits at this block. The approver gets a notification and decides in Flows › Approvals (Waiting for you / Decided), with an optional note. The flow then continues on the approved or rejected branch; the note is {{node.<id>.output.note}}. Each approval is decided once and the decision is recorded.
You don't need any Flows permission to decide an approval — being the named approver is enough.
Note: an approval has no expiry or escalation yet, and there is one approver per block. An Approval or Wait block can't sit inside a For each loop.
Wait
Set Wait for and the unit (minutes, hours or days), up to 30 days. The run pauses, then continues on its own within a few seconds of the time.
Merge
Joins several branches back into one path, so the blocks after it run once instead of once per branch. Connect each branch into the Merge block, then connect what should happen next out of it.

Set Continue when:
- Every branch that runs has arrived (the default) — waits for every branch that is actually running. A branch a condition did not take is not waited for.
- The first branch arrives — continues straight away on the first arrival and ignores the rest.
If a block on one of the branches fails and stops its branch, the flow stops at the merge.
Approval and Wait blocks must sit before the branches split or after the merge, not on only some of the branches into it — the flow can't be saved otherwise. A merge inside a For each loop joins once for each item.
Logic blocks
- Condition, Filter list, Summarize and For each are described in Conditions and lists.
When a block fails
Every action block has an If this step fails setting:
| Choice | What happens |
|---|---|
| Stop this branch (run fails) | The default. The branch stops and the run is marked Failed. |
| Carry on to the next block | The flow continues as if the block had worked. |
| Go to the error path | Adds an on error output to the block. Connect it to what should happen instead, such as notifying someone. |

With Carry on or Go to the error path, the run still counts as successful, the step shows Failed, carried on, and the reason is available as {{error.message}} (under Failure in the insert-value picker). Test runs never fail an action, so they never take the error path.
Otherwise:
- A failed block stops its own branch. Branches that do not depend on it carry on.
- The run is marked Failed if any block failed. The failing block shows its error under Detail on the run. See Runs and overview.
- A failed block is not retried automatically.
- A run can carry out up to 50,000 blocks. Its history keeps 2,000 steps plus every failure; the rest are counted. A run still has a 10-minute limit.