Workflow Node Settings

This guide covers the common settings and actions for Workflow Builder nodes, organized by setting type. Creators use this guide to look up a setting that several nodes share or to find which nodes offer a setting.

For output link settings, see Output Links.

Node Actions

Universal Actions

Selecting a node on the canvas opens its settings in the Properties panel and displays action buttons above the node. The following actions are available on every node:

Action	Description
Edit	Opens the node's settings in the Properties panel.
Delete	Removes the node from the canvas ().

Task Node

The following action displays only when the Task node has a module connected:

Action	Description
Open module	Opens the connected module in the Module Builder.

Timer Start Node and Signal Start Node

The following actions display on Timer Start and Signal Start nodes only. Start Node Administration also governs these nodes.

Action	Description
Start	Activates the node and begins the timer or signal listener.
Stop	Deactivates the node. Settings become editable again after stopping.
Run once	Triggers the node a single time without activating it on a recurring schedule.

While a Timer Start node is active, its settings are locked and the Properties panel displays a warning. Stop the node to edit its settings.

Settings Reference

Label

Available on all nodes.

Path

Available on the Start, Task, Timer, Timer Start, and Signal Start nodes.

Scheduling

Available on the Timer and Timer Start nodes.

Relative (default): Fires after a set amount of time.

Exact: Fires at a specific scheduled time. All times are in UTC.

<DocsHierarchyTable fieldLabel="Setting" extraColumns={["Field", "Type", "Default"]} rows={[ { field: "Frequency", cells: [frequency, "Drop-down", Daily], description: <>How often to fire. Options include: Daily, Weekly, Monthly, or Yearly.</>, children: [ { field: "Day of Week", cells: [dayOfWeek, "Drop-down", Monday], description: <>The day to fire. Options include: Monday through Sunday. Visible when Frequency is Weekly.</> }, { field: "Month", cells: [monthOfYear, "Drop-down", January], description: <>The month to fire. Options include: January through December. Visible when Frequency is Yearly.</> }, { field: "Day of Month", cells: [dayOfMonth, "Drop-down", 1], description: <>The day of the month to fire, or Last Day of the Month. If the selected day doesn't exist in a given month, the timer fires on the last day of that month. Visible when Frequency is Monthly or Yearly.</> } ] }, { field: "Time", cells: [time, "Time input", "—"], description: "The time of day to fire, in UTC." } ]} />

Cron: Fires based on a cron expression for advanced scheduling.

Error Message

Available on the Exclusive Gateway and Inclusive Gateway Split nodes.

Timed Event

Available on the Timed Event node.

The Timed Event node also includes the following sections:

• Send a Message: Select Add a Message to configure a message the node sends after a set duration. Each message displays as a card with Edit and delete options.
• Send workflow to new task after certain duration: Sets the output link the workflow follows after a set duration. Each Timed Event node supports one of these links. For link settings, see Output Links.

Triggering Event

Available on the Signal Start node.

<DocsHierarchyTable fieldLabel="Setting" extraColumns={["Field", "Type", "Default"]} rows={[ { field: "Triggering Event", cells: [triggeringEvent, "Drop-down", "—"], description: <>The platform event that begins this workflow. Options include: On Promotion (Specific Application), On Promotion (All Applications), On Save (Specific Module), On Save (All Modules), On Save (Specific Workflow), or On Save (All Workflows).</>, children: [ { field: "Application", cells: [applicationId, "Module selector", "—"], description: <>The application to monitor for promotion. Visible when Triggering Event is On Promotion (Specific Application).</> }, { field: "Module", cells: [moduleId, "Module selector", "—"], description: <>The module to monitor for saves. Visible when Triggering Event is On Save (Specific Module).</> }, { field: "Workflow", cells: [workflowId, "Module selector", "—"], description: <>The workflow to monitor for saves. Visible when Triggering Event is On Save (Specific Workflow).</> } ] } ]} />

Signal Display

Available on the Signal node.

<DocsHierarchyTable fieldLabel="Setting" extraColumns={["Field", "Type", "Default"]} rows={[ { field: "Use an Existing Module", cells: [useExistingModule, "Toggle", OFF], description: <>When set to ON, this setting displays an existing module to end-users at this point in the workflow instead of the default message.</>, children: [ { field: "Add a Module", cells: [form, "Module selector", "—"], description: <>The module to display to end-users. Visible when Use an Existing Module is ON.</> } ] }, { field: "Use Template", cells: [useTemplate, "Toggle", OFF], description: <>When set to ON, this setting displays a custom message to end-users generated from a template expression.</>, children: [ { field: "Template", cells: [template, "Text input", "—"], description: <>A template expression that generates the HTML message displayed to end-users. Supports template expressions for dynamic values. Visible when Use Template is ON.</> } ] } ]} />

Handoff

Available on the Handoff node.

<DocsHierarchyTable fieldLabel="Setting" extraColumns={["Field", "Type", "Default"]} rows={[ { field: "Continue Current Submission", cells: [continueCurrentSubmission, "Toggle", ON], description: <>When set to ON, this setting carries the current submission into the next workflow.</> }, { field: "Choose Workflow To Handoff To", cells: [workflow, "Drop-down", "—"], description: "The target workflow for the handoff.", children: [ { field: "Choose Node To Start From", cells: [workflowNode, "Drop-down", "—"], description: <>The start node in the target workflow. Visible when Choose Workflow To Handoff To is set.</> } ] } ]} />

Message

Available on the Message node.

<DocsHierarchyTable fieldLabel="Setting" extraColumns={["Field", "Type", "Default"]} rows={[ { field: "Label", cells: [label, "Text input", "—"], description: "A display name for the node." }, { field: "To", cells: [to, "Text input", "—"], description: "The recipient address. Supports template expressions." }, { field: "Send Via", cells: [channel, "Drop-down", "—"], description: <>The messaging channel to use. Options include: Email.</>, children: [ { field: "Cc", cells: [cc, "Text input", "—"], description: <>Additional recipients to copy. Supports template expressions. Visible when Send Via is Email.</> }, { field: "Bcc", cells: [bcc, "Text input", "—"], description: <>Additional recipients to blind copy. Supports template expressions. Visible when Send Via is Email.</> }, { field: "From Name", cells: [fromName, "Text input", "—"], description: <>The display name used for the sender. Visible when Send Via is Email.</> }, { field: "Reply To", cells: [replyTo, "Text input", "—"], description: <>The reply-to address for the email. Visible when Send Via is Email.</> }, { field: "Subject", cells: [subject, "Text input", "—"], description: <>The email subject line. Supports template expressions. Visible when Send Via is Email.</> } ] }, { field: "Template", cells: [template, "Text input", "—"], description: "The message body. Supports template expressions." }, { field: "Generate and Send Refer String", cells: [generateReferString, "Toggle", OFF], description: <>When set to ON, this setting generates an authenticated link and includes it in the message.</>, children: [ { field: "Refer String TTL (in minutes)", cells: [referStringExpiry, "Number input", "—"], description: <>How many minutes pass before the refer string link expires. Visible when Generate and Send Refer String is ON.</> }, { field: "Refer String Redirect Target", cells: [redirectTarget, "Text input", "—"], description: <>The end-users are redirected to when they follow the refer string link. Supports template expressions. Visible when Generate and Send Refer String is ON.</> } ] } ]} />