Documentation
Automation

How to Use

Create, validate, and activate a visual automation funnel.

The visual builder lets you arrange workflow steps on a canvas and connect each step to the next outcome.

Before You Start

Prepare the integration, tags, custom fields, and staff profiles that the funnel will use. Create a Builder space and then create a funnel inside it.

Configure the Funnel

When creating a funnel, set:

FieldDescription
Funnel nameA clear name that describes the workflow.
Trigger typeThe event that starts the funnel.
Message trigger modeFor message triggers, run on any message or only the first client message.
Trigger targetThe tag or custom field watched by a scoped trigger.
StatusDraft, Active, or Paused.
EnabledStarts or stops the funnel without deleting it.

Keep new funnels in Draft while building and testing.

Work on the Canvas

  1. Open the funnel and click Open builder.
  2. Use Add step to create the first action step.
  3. Select a step to open its inspector.
  4. Add one or more blocks, such as Send text, Add client tags, or HTTP request.
  5. Add an outgoing trigger to decide when the flow continues.
  6. Connect that trigger to another step.
  7. Repeat until each intended path has an end.

Blocks inside a step run from top to bottom. After the blocks finish, GChat evaluates the outgoing triggers. A Stop automation block prevents later blocks in the same step from running and completes the current run.

Build a Simple Reply Funnel

This example sends a welcome message, waits for a reply, tags the client, and confirms receipt.

  1. Create a funnel with Message received and First client message.
  2. Add a step named Welcome.
  3. Add Send text with Hello, {sys.client.name}. How can we help?.
  4. Add an Any message trigger to the Welcome step.
  5. Add a second step named Reply received.
  6. Connect the Any message handle to Reply received.
  7. In the second step, add Add client tags and select an intake tag.
  8. Add Send text below it with Thank you. A team member will review your message.
  9. Add Stop automation as the final block.
  10. Open Checklist, resolve errors, and click Save.

The first step waits because it uses Any message. The second step runs its tag and message blocks in order, then explicitly ends the run.

Use Go to start, zoom in, and zoom out to navigate the canvas. Drag steps to organize the flow. Select a step to edit it, or use its actions menu to rename or delete it.

Available keyboard shortcuts:

ShortcutAction
Cmd/Ctrl + ZUndo
Cmd/Ctrl + Shift + ZRedo
Cmd/Ctrl + CCopy the selected step
Cmd/Ctrl + VPaste the step at the viewport center
Delete or BackspaceDelete the selected step or item

Shortcuts do not run while the cursor is inside an input, text editor, or select control.

The builder does not save every edit automatically. The unsaved indicator appears after a change. Click Save to keep valid changes, or Reset to return to the last saved version.

If you try to leave with unsaved changes, GChat displays a warning before discarding them.

Validate the Funnel

Open Checklist before saving. Errors must be fixed; warnings identify branches that may not continue.

Common errors include:

  • missing message text or attachments;
  • an empty HTTP request URL or body;
  • an invalid expression;
  • no selected tags, custom field, operator, variable, or target funnel;
  • a reference to a deleted funnel variable.

A trigger without an outgoing connection is a warning: the funnel can be saved, but that branch stops there.

Click an item in the checklist to return to the affected step, block, or trigger.

Test and Activate

  1. Save the funnel in Draft.
  2. Trigger it with a test client on the linked integration.
  3. Confirm messages, tags, fields, transfers, and requests behave as expected.
  4. Review the inbox and audit logs.
  5. Change the status to Active.
  6. Turn on Enabled.

Use Paused or disable the funnel when you need to stop new runs while keeping the schema.

Before Activation

  • Confirm the automation space is linked to the intended integration.
  • Check that the funnel start trigger is narrow enough.
  • Follow every outgoing path, including ELSE branches.
  • Verify message wording and integration-specific formats.
  • Test tag, custom-field, variable, transfer, and HTTP effects.
  • Confirm that every intentional endpoint uses Stop automation.
  • Save the final version before setting the funnel to Active.

For detailed configuration, continue with Blocks and Triggers and Connections.

On this page