Documentation
AutomationBlocks

Blocks Overview

Understand how blocks run inside an automation step.

Blocks are actions performed by a funnel. They can send a message, update client data, call an external API, route a chat, store a value, or stop a run.

How a Step Runs

When a funnel enters a step, GChat runs its blocks from top to bottom.

  1. The first block starts.
  2. When it completes, the next block starts.
  3. Processing continues until the last block or a stop block is reached.
  4. GChat then evaluates the step's outgoing triggers.

Drag blocks in the inspector to change their order. Order matters whenever one block prepares data for another. For example, put Set variable before an HTTP request that reads that variable.

Choose a Block

GoalBlock
Send text to the clientSend text
Send one or more files, optionally with textSend media + text
Send a voice recordingSend voice
Send a round video messageSend video note
Add or remove client segmentationAdd client tags / Remove client tags
Save a value on the clientChange custom field
Assign the conversationTransfer to operator
Store temporary run dataSet variable
Call another serviceHTTP request
End this runStop automation
Cancel selected parallel funnelsStop funnels

Add and Configure a Block

  1. Select a step on the canvas.
  2. In the inspector, click Add block or trigger.
  3. Choose an item from Blocks.
  4. Open the block card and complete its required fields.
  5. Drag the block to the required position in the step.
  6. Open Checklist and resolve any errors.
  7. Click Save.

Use a block's actions menu to rename or delete it. Renaming changes the label shown in the builder and does not change the action type.

Expressions in Blocks

Text, variable values, and HTTP request fields can insert runtime data with expressions.

Hello, {sys.client.name}!

Use autocomplete in an expression field to select available system, funnel, and environment variables. See Expression Language for syntax and functions.

Validation

The builder prevents saving when a required block value is missing or an expression is invalid. The checklist links each error to the affected step and block.

An unconnected outgoing trigger is a warning rather than an error. The funnel can be saved, but that branch ends after the step finishes.

On this page