Skip to main content

Documentation Index

Fetch the complete documentation index at: https://knowledge.goautonomous.io/llms.txt

Use this file to discover all available pages before exploring further.

Pulse

Go Autonomous’s visual workflow builder — automate actions, route requests, and connect to external systems without writing a line of code.

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, you see a list of all your workflows 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 is assigned to.
  • Stage — the workflow’s deployment stage (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, or click an existing workflow to open it in the editor.

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 with no areas configured applies globally.

What’s next