Workflow node settings reference

This is the field-by-field reference for the workflow inspector. Select a block on the canvas to open Workflow node settings, change values in the inspector, and use Apply to apply the block configuration. Applying a node setting is a workflow change; use a workflow on the form named a test form or an approved draft only.

Common behavior

Every node has a Caption supplied by the workflow editor. The inspector loads the node-specific settings asynchronously and shows an Applied confirmation after a successful Apply. Close the inspector without applying to discard the current edit. A node must be connected to the intended next path before testing.

The inspector is scrollable and may hide dependent rows until a preceding selection is made. For example, HTTP authentication fields appear when Basic HTTP Authentication is selected, Wait Until’s date/time rows depend on its mode, and BigData fields depend on choosing a collection. A missing recipient, field, collection, target, branch label, or connection must be treated as a configuration error even if the canvas node still displays Ready.

Field-reference validation

Before a workflow is accepted, v2 validates references against the current form field names. Recipient fields are checked for Notification, Approval, Request Edit, Human Task, and Assign Form; condition statements and branch conditions must reference existing fields; Human Task field selections must still exist; BigData update/filter field values must still exist; and Wait Until’s field mode must reference an existing date/time-capable field. Renaming or deleting a form field can therefore invalidate a saved workflow. Reopen each affected node, select the replacement field, Apply it, and Save the workflow.

Validation does not prove that a recipient can receive mail, that a BigData row exists, that an HTTP endpoint responds, or that a timer has elapsed. Those are runtime tests and must be checked separately.

Node catalog

Node shown in the palette	Inspector settings	How to use it safely
Start	Caption	Entry point for the workflow. Connect it to the first action.
Stop	Caption	Terminal outcome. Give it a meaningful completion/rejection caption.
Condition (Exclusive Gateway)	Caption and condition/rules configuration	Use for a binary decision; test both true and false paths.
Conditional Branch	Caption, branch labels, branch conditions	Give every branch a clear label and test the non-matching/default path.
Notification	To (user, group, or form-field recipient), Notification message	Sends an email message to the selected recipient. Use New notification to create a message with a subject and reusable content blocks, then Save and use before applying the node. Use an approved test mailbox.
Timer	Delay value and delay unit: seconds, minutes, hours, days, weeks, months, years	Pauses for a fixed duration. Use a short delay only in a test workflow.
Approval	Assignee, notification sent to assignee, approval timeout value/unit, Require comment	Test approve, reject, timeout, and required-comment behavior.
Entry Point	Maximum cycles (1–10), unique entry-point ID	Defines a loop target and sends execution to its overrun branch after the cycle limit.
Go To	Entry point target	Jumps to the selected Entry Point. Confirm the target before applying.
Request Edit	To, Notification message	Requests additional edits to the original result from a user, group, or original filler.
BigData Update	Operation (Update or Insert), BigData collection, update operations, first matching-row filter	Use a dedicated test collection. Update mode acts on the first row satisfying the filter; Insert mode supports only SET operations and still requires at least one operation.
Human Task	Assignee, notification, timeout value/unit, selected form fields	Generates a dynamic form containing only the selected fields for the assignee.
HTTP Request	Method (GET/POST), URL, authentication (None/Basic HTTP Authentication), Basic username/password, request type (form-data or x-www-form-url-encoded), parameters, Continue workflow if HTTP request fails	Use a controlled HTTPS endpoint. Never place real secrets in a workflow. Decide explicitly whether an HTTP error stops or continues the path.
Form Fill (Assign Form)	Form to Fill, To, Notification	Sends another form to a recipient and continues after that form is submitted.
Wait Until	Mode: Specific date and time or Date, Calendar, or Appointment field; date/time and time zone or source field; Run before target value/unit	Use a short controlled date offset. Verify the source field, target value, time zone, and behavior when the source is empty or invalid.
Integration	Enabled integration	Runs an already enabled form integration. It does not also run immediately after submit when invoked by this node.

Duration units

Timer, Approval timeout, Human Task timeout, and Wait Until offsets use the same units: Seconds, Minutes, Hours, Days, Weeks, Months, and Years. Numeric shortcut inputs reject non-numeric characters and leading-zero-only values in the current editor implementation.

Security and data-handling notes

• Treat HTTP Basic username/password, SMTP settings, integration credentials, and notification content as sensitive.
• Do not test against production endpoints, real customer submissions, or real recipient lists during documentation.
• BigData operations can insert or update persistent records; use a dedicated test collection and an explicitly approved form.
• Do not use looping nodes to conceal a failing branch. Set a finite cycle limit and include an overrun outcome.