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.

Nodes are the building blocks of a Pulse workflow. Each node performs a specific function — triggering the workflow, routing data, transforming it, or calling an external service. You connect nodes together on the canvas to define the path data takes from start to finish. To add a node, drag it from the left-hand node palette onto the canvas. Click any node to open its configuration panel.

​
Webhook

The webhook node is the entry point of every workflow. It listens for incoming events and triggers the workflow when one is received. Every workflow must begin with a webhook node — it cannot be deleted or moved to a different position in the flow. When you open the webhook node, you’ll see:
  • Test URL — a temporary endpoint for sending test events during development. Copy this URL to use when testing.
  • Production URL — the live endpoint that triggers the workflow once it’s active.
  • Response type — controls when the webhook sends a response back to the caller:
    • Immediate — responds to the caller as soon as the webhook is received, before the rest of the workflow runs.
    • After last node — waits until the final node in the workflow completes before responding. This adds a Response node to the end of your workflow.
Use the Listen for Event button in the node panel to activate the webhook listener during testing. This puts the node into a listening state so that when you send a request to the test URL, the workflow captures the payload and displays it in the input/output viewer.

​
HTTP

The HTTP node makes a call to an external API or service and passes the response downstream. Use it to query a pricing engine, send data to your ERP, or trigger actions in other tools. Configuration options:
  • URL — the API endpoint to call.
  • Method — the HTTP method: GET, POST, PUT, DELETE, or PATCH.
  • Authentication — select a pre-configured authenticator (OAuth2 or API key) to handle authentication automatically. Authenticators are configured under Administration > Authenticators.
  • Headers — toggle on to add custom request headers as key/value pairs.
  • Params — toggle on to add URL query parameters as key/value pairs.
  • Body — toggle on to add a request body (JSON or raw text).
  • Response mode — controls how the node’s response is passed to the next node:
    • Replace — the HTTP response replaces the current data payload entirely.
    • Append — the HTTP response is merged into the existing payload alongside previous data.

​
Transform

The transform node processes and modifies data as it moves through the workflow. Use it for calculations, field mapping, formatting, filtering, or any logic that needs to run between other steps. Transformation logic is written in JavaScript. The node provides a code editor where you write a function that receives the current data payload and returns a modified version. The input and output viewers show the live data state before and after transformation, making it easy to verify your logic is working correctly. Use the Test button to run the transformation against the current input data.

​
Switch

The switch node routes data down different paths based on conditions you define. Use it to branch your workflow — for example, sending order requests one way and quote requests another. Each switch node contains one or more routes. Each route has:
  • Name — a label for the path (shown on the canvas connection line).
  • Condition — a comparison that must be true for data to follow this route. Set a left value, an operator, and a right value.
  • Default — one route can be marked as the default fallback, which is taken when no other conditions match.
Available operators:
OperatorMeaning
EQEqual to
NEQNot equal to
GTGreater than
LTLess than
GTEGreater than or equal to
LTELess than or equal to
Each route creates a separate output handle on the node. Connect each handle to the next node in that path. The switch node evaluates conditions in order and follows the first route that matches.
Every switch node should have a default route configured to handle cases where none of your conditions match.

​
Response

The response node is a terminal node that marks the end of a workflow path. It appears automatically when the webhook node’s response type is set to After last node. The response node cannot be edited — it simply signals that the workflow has completed and returns the final data payload to the original caller. A green status indicator on the node shows whether the last test run completed successfully.