Overview
Building a workflow in Pulse is a visual process. You drag nodes onto a canvas, connect them, configure each node’s behavior, and test the result — all without writing code.Create a new workflow
1
Open Pulse
Navigate to Pulse from the app switcher (the grid icon in the top-right corner).
2
Click Create new workflow
Click the Create new workflow button in the top-right corner. A new workflow opens in the editor with an empty canvas.
3
Name your workflow
Enter a descriptive name for your workflow (e.g., “Price Checker,” “Order Router”). The name appears in the Pulse dashboard and helps your team identify what the workflow does.
The workflow editor
The editor consists of three main areas:- Node inventory (left sidebar) — a collapsible panel that lists every node type and custom component you can drag onto the canvas. See The node inventory below.
- Canvas (center) — the visual workspace where you build your workflow by placing and connecting nodes.
- Top bar — shows the workflow name, version number, area configuration, and the Active/Inactive toggle.
The node inventory
The node inventory is the launchpad for everything you can drop onto the canvas. By default it sits collapsed against the left edge of the editor to give the canvas more room — hover over it (or focus any control inside it) and it expands to show the full list. The inventory has two sections:- Core nodes — built-in node types (Webhook, HTTP, Switch, Transform). Always visible, even when collapsed, so you can drag them onto the canvas with one motion.
- Custom components — reusable groups of nodes saved to your tenant’s library. Only visible when the inventory is expanded. See Custom components.
- Search — filters both core nodes and custom components by name. Core nodes also match on their description, so searching for “route” finds the Switch node.
- Pin — keeps the inventory open even after you move the cursor away. Useful when you’re dragging several nodes in a row or scrolling through a long list of custom components. Click the pin again to release it.
Zoom and navigation
Use the zoom controls in the bottom-right corner to zoom in, zoom out, or fit the entire workflow to screen. Click and drag on empty canvas space to pan around large workflows.Select multiple nodes
You can work with several nodes at once:- Shift-drag on empty canvas space to draw a selection box around the nodes you want.
- Shift-click individual nodes to add them to (or remove them from) the current selection.
Copy and paste nodes
Use standard keyboard shortcuts to duplicate parts of a workflow — even between two different workflows open in separate browser tabs:- Cmd/Ctrl + C — copy the currently selected nodes (and the edges between them) to the clipboard.
- Cmd/Ctrl + V — paste them at the cursor position. Pasted nodes get new IDs and are added to the current workflow.
Webhook nodes can’t be copied — every workflow has exactly one webhook, and it’s added automatically when you create a new workflow.
Custom components
A custom component is a reusable group of nodes that you’ve saved to your tenant’s library. Use components to share common patterns — like an “enrich + validate + route” sub-flow — across many workflows without rebuilding them by hand.Save a selection as a component
1
Select the nodes you want to package
Shift-drag or shift-click to select two or more connected nodes. The selection toolbar appears.
2
Click Save as component
Give the component a clear name and pick an icon. If a component with the same name already exists, you’re asked whether to overwrite it.
3
Use it in any workflow
Open a workflow and hover the node inventory to expand it. Scroll to the Custom components section and drag a component onto the canvas to insert all of its nodes and connections. Use the search box at the top of the inventory to jump to a component by name.
Components don’t include webhook nodes. To turn a selection into a component, make sure the webhook isn’t part of it.
Add and connect nodes
1
Drag a node from the palette
Click and drag a node type (HTTP, Switch, or Transform) from the left palette onto the canvas.
2
Connect nodes
Drag from the output port (the dot on the right side of a node) to the input port (the dot on the left side of another node) to create a connection.
3
Configure the node
Double-Click on a node to open its configuration panel. Set the node’s parameters — these vary by node type (see below).
4
Repeat for each step
Continue adding and connecting nodes until your workflow is complete.
Node types
Webhook
The webhook node is the starting point of your workflow. It defines what triggers the workflow — for example, when a new request is received or when a specific intent is detected. Every workflow starts with a webhook.Switch
The switch node routes data along different paths based on conditions. You define rules — for example, “if the intent is Order, go to Path 1; if the intent is Quote, go to Path 2.” Each output path is labeled so you can track the logic.Transform
The transform node modifies data as it passes through. Use it for calculations (e.g., price checks), data formatting, field mapping, or any processing step before data reaches its destination.HTTP
The HTTP node makes API calls to external systems. Use it to send data to your ERP, query a pricing service, or trigger actions in other tools. Configure the URL, method, headers, and payload.Test your workflow
Before activating a workflow, use the Test Workflow button at the bottom of the canvas. This sends sample data through the workflow and shows you the result at each node — so you can verify the logic works correctly before it handles real requests.Activate and manage
- Active toggle — use the toggle in the top bar to turn the workflow on or off. Active workflows process matching requests automatically.
- Version history — the version number (e.g., v.2) in the top bar shows the current version. The history icon lets you review previous versions.
- Save — click the save icon to persist your changes.
Workflows process requests that match their trigger conditions and area configuration. Make sure your area assignments are correct before activating a workflow.