Properties, modes and keyboard shortcuts

The properties panel contains the settings of the selected node or the selected connection. Changes are only possible with write permission and an active edit lock.

Editing properties

After selecting a node, the panel shows the fields available for that activity type. Frequently used settings are:

• Label: the visible name of the step
• Output variable: the name used to access the result in subsequent steps; renaming it updates every reference to it in the workflow
• Description: an optional explanation of the step
• Target machine and credentials: the execution target for remote activities
• Timeout: the maximum runtime of the step
• Retry policy: repeats a failed step (attempts including the first, backoff, delay); permanent remote errors such as a rejected logon are not retried
• Disabled: skips the step during execution
• Breakpoint: pauses a debug run before this step; expert mode only

Mandatory fields are marked in the panel. The available fields differ per activity. A complete overview is in the Activity reference.

After selecting a connection, you can change the label, condition and appearance among other things. Further information is in Edge conditions.

Standard and expert mode

Standard mode contains the functions for creating, configuring, testing and publishing workflows.

Expert mode adds functions for larger workflows:

• Breakpoints and debug runs
• Simulation and version comparison
• Find and replace
• Grouping and precise positioning of nodes
• Additional view and appearance options
• JSON export and extended navigation

The mode can be switched in the designer. Existing workflow data is not changed by it.

Using variables

Variables carry values between triggers and activities. Typing {{ opens the variable picker.

Available values come from:

• The outputs of previous steps, for example {{script.output}}
• Global variables, for example {{globals.API_URL}}
• The inputs of a manual trigger, for example {{manual.customerId}}

A field can contain a fixed value, a variable, or a combination of both. Which values are available in a given place is described in Data bus and variables.

Configuring triggers

Triggers are also configured through the properties panel.

Checking and running

Several levels are available for checking a workflow:

• Step test: runs only the selected step with test data.
• Run: runs the workflow. Parameters of a manual trigger are requested before the start.
• Debug run: runs the workflow with breakpoints; expert mode only.
• Simulation: shows the possible flow without executing activities; expert mode only.
• Lint: shows missing mandatory values, unreachable nodes and other problems.

Errors from the lint check prevent publishing. Warnings have to be acknowledged before publishing.

With the edit lock held, unsaved changes are saved before a run or a debug run. Without the lock, a run executes the saved version, and its parameters are the ones requested. A running execution can be cancelled.

Monitoring a run

The execution panel contains:

• Live: the current state and output of the running steps
• History: past executions
• Output: the available trigger, variable and step data
• Watch: watched expressions; expert mode only

At a breakpoint, the debug run pauses before the step concerned. The following actions are then available:

• Continue: resume execution until the next breakpoint
• Step over: execute exactly one step and pause again
• Stop: end the execution

Before continuing, the variable inspector can change step results and run inputs (manual.*); global variables and engine keys stay read-only. Changes apply only to the current pause. After a page reload the paused step and its variables are shown again.

Saving, publishing and exporting

Changes are saved automatically as a draft after a short editing pause. Ctrl+S saves the draft immediately. If the workflow was saved elsewhere in the meantime, the save is rejected: the draft stays on the canvas, autosave stops and a reload shows the current version.

Publishing promotes the current draft to the executable version. Depending on the workflow's state, the same action can enable or disable the workflow. Earlier versions remain available through the version history.

The workflow can be exported as JSON. A PNG file captures the current canvas view.

Keyboard shortcuts

Ctrl corresponds to Cmd on macOS. The built-in quick reference opens with ?.

Standard mode

Expert mode

The following shortcuts add to those of standard mode.

Script editor

These shortcuts apply in the open script editor.

Canvas gestures