A node is one action on the canvas. Nodes are joined by connections, which decide what runs next and can carry conditions, so the flow branches on the result.
Different parts of PalDock use slightly customised versions of the Connection Creator, but the node types below are the same everywhere.
Start and End
Every scenario begins with a Start node and every path should reach an End node.
The Start node has a flow, which decides what triggers the scenario. In integrations there are two, Ping and Post, and each is a separate path with its own Start and its own End. Everywhere else there is one.
A scenario can also be started by an internal event, such as a conversion or a status change, or by an external system calling in through a Webhook node.
The End node records the outcome. Marked success, the lead goes through. Marked failed, it does not. See Where Connection Creator is used.
Working with data
Modify changes the value of one or more fields, with conditions inside the node. This is where you translate your values into whatever the other side expects.
Set stores a value from a response so it can be used later in the flow, or after it.
Set Event records an event. For example, when a response comes back as a duplicate, increment the Duplicate counter by one so it shows up in reporting.
Mirror inherits all settings from another node, so you maintain one master and the copies follow it.
Flow control
Wait pauses the flow before it continues. It can wait a fixed time, until a specific date and time, until a given hour of the day, until the next working day, or a set time after an event.
Breaker limits how many times a loop may repeat, so a retry cannot run forever.
There is no node that repeats something on its own. You build a loop from a Breaker, a Wait and a connection leading back to an earlier node. The Breaker is what caps it.
SubScenario calls another scenario from this one and exchanges data with it, which keeps shared logic in one place instead of copied across integrations.
Requests
HTTP node sends a request to an external service. You set the method, endpoint, query, headers and body, plus the format, the timeout and, where required, a signature.
Authentication is part of this node, not a node of its own. API keys, Basic auth, OAuth and client certificates are all configured here, and an access token can be stored and refreshed.
Webhook waits for an external system to call in. The flow pauses at the node and continues when the call arrives, which is usually better than polling when the other side supports it.
Related, but not nodes
- Connections join nodes and carry the conditions. See Connections with Conditions.
- Keys hold the tokens, endpoints and custom parameters an integration uses.
- Structures define the fields a scenario works with.
