Editor

The Editor is the visual tool where you build a scenario. Nodes appear as dots on a canvas. You drag them, connect them with lines, and configure what each one does.

Nodes

A node is one action: send a request, change a value, wait, finish. There are two kinds.

• Built-in nodes are the core elements provided by PalDock, such as Start, Modify or HTTP. They work the same in every workspace.
• External nodes represent an outside service or API and are what connects PalDock to a third-party platform.

Click any node to open its configuration panel, where you define its inputs, outputs and rules.

Adding a node

Click the plus on the canvas and a panel opens with everything you can add. Type in the search box to find a node by name, or browse the groups:

• Flow control decides when and whether things happen: Wait, Breaker.
• Data operations change the data: Modify, Set.
• Connections talk to the outside world: HTTP, Webhook.
• Composition builds the scenario itself: Start, End, SubScenario, Mirror.

The tabs along the top are only a filter. The first one shows the nodes you reach for most often, and the rest narrow the list to one group. Nothing is hidden, so if you know the name, searching is quicker than browsing.

See List of nodes for what each one does.

The Start node

Every scenario begins with a Start node. Its type follows the context the scenario belongs to: Integration, Structure or Tracking. See Where Connection Creator is used.

A scenario can have more than one Start node when it serves separate paths that must not touch, which is how PING and POST flows are built in a pingtree. See How to integrate anything.

Connecting nodes

Nodes are joined by lines. A connection defines the order in which nodes run. Connections can branch. One node can lead to several others, so the flow takes a different path depending on a condition, for example routing leads to different integrations based on a validation result.

Every connection can carry a condition that decides whether the flow continues along it. If the condition is not met, that line is not followed, while other lines from the same node still can be. See Connections with Conditions.

Choosing a value

Almost every node asks you for a value: which field to send, what to compare against, where to store a result. You never have to remember names. Open the picker and take what you need from what the scenario has at that point.

It offers four groups:

• Form fields are the fields of the structure the lead came from, such as first_name or email. They are grouped the way the structure is, so related fields sit together.
• Keys are the tokens, endpoints and parameters this integration uses.
• System parameters are the values PalDock fills in itself, covering the conversion, the commission, the offer, the advertiser, the affiliate, the integration and the time.
• Previous steps is everything the earlier nodes produced, including a path into a response body.

The picked value appears as a tag in the field, and underneath it is stored in braces, such as {email} or {external_id}. You can type instead of picking, and mix the two freely, so Bearer {token} works as one value.

Only what was produced before the current node is available, because data travels forward and never back. If you need a value of your own, store it with a Set node and reference it by name afterwards.

See page parameters for what PalDock provides.

Turning a node off

A node can be disabled without deleting it. A disabled node is skipped and the flow does not continue past it. This is the safe way to take one branch out of a live scenario while you work on it.

Reusing a node

If the same request or configuration is needed in several places, do not copy it. Use a Mirror node, which inherits all settings from its master and updates automatically whenever the master changes.

Typical workflow

1. Start. Every scenario begins with a Start node.
2. Add nodes. Drag in built-in actions or external integrations.
3. Connect. Join them to define the order, and add conditions where the flow should branch.
4. Configure. Open each node and set its parameters, such as endpoints, credentials, field mapping and rules.
5. Run and test. Execute the scenario and check what happened in the log.

Checking what happened

Every run stores the input and output of each node. Open the run and follow it node by node. You will see the exact data each node received and returned, which is where you start whenever something does not work. See Logs.