Pulse overview

​

Overview

Pulse is Go Autonomous’s visual workflow builder. It lets you create automated workflows that trigger actions based on incoming requests — like checking prices, routing orders to the right team, or sending data to external systems. You build workflows by connecting nodes on a visual canvas: define a trigger, add logic and branching, transform data, and connect to external services. No coding required.

​

The Pulse dashboard

When you open Pulse from the app switcher, the dashboard has two tabs:

• Overview — the list of all workflows on your tenant. Use this to create, open, and manage workflows.
• Executions — a searchable history of past workflow runs. See Executions for details.

The Overview tab shows each workflow with the following details:

• Workflow — the name of the workflow.
• Nodes — how many nodes the workflow contains.
• Created — when and by whom the workflow was created.
• Last Edited — the most recent modification date and editor.
• Areas — which areas the workflow runs for. Default means all areas. Click the cell to change them directly from the list.
• Stage — the point in request processing where the workflow runs (e.g., On Transformation).
• Status — whether the workflow is currently Active or inactive.

Click the Create new workflow button to start building a new one — you’ll pick its stage and areas first — or click an existing workflow to open it in the editor. Opened Workflow View:

​

Key concepts

​

Nodes

Nodes are the building blocks of a workflow. Each node performs a specific action:

• Webhook — the trigger that starts the workflow when a matching event occurs.
• Switch — routes data down different paths based on conditions (e.g., intent type, customer status).
• Transform — modifies or processes data before passing it along (e.g., price calculations, field mappings).
• HTTP — makes calls to external APIs or services.

​

Connections

Nodes are connected by lines that define the flow of data. Each connection represents a path the data can take. Switch nodes can have multiple output connections — one for each condition.

​

Areas

Workflows can be assigned to specific areas to limit which requests they apply to. A workflow set to Default applies to all areas. You choose areas when you create a workflow, and you can change them at any time from the dashboard or the editor’s top bar. Area changes apply immediately and don’t create a new version. See Areas.

​

Stages

Each workflow runs at one stage of request processing — for example, right after extraction or after transformation. You pick the stage when you create the workflow. See Stages.

​

What’s next

• Create and configure a workflow
• Build with Pulse: what to build with it, for integrations
• Review past executions
• Configure areas