Skip to content

Workflow node reference

This reference lists the workflow nodes and their configuration surfaces. Configure and test every node in the form named a test form before using it with production data.

Names used in the editor

The live node palette may use shorter or product-specific labels. Use this mapping when matching a palette button to a guide:

Live labelGuide/reference nameMeaning
Form is submittedStartEntry event that begins the workflow.
Assign FormForm FillSends another form to a recipient to complete.
Bigdata UpdateBigData UpdateWrites an insert or update to an authorized BigData collection.
Http RequestHTTP RequestCalls an external HTTP(S) endpoint.
ConditionCondition / Exclusive GatewayChooses a path from a condition result.
Conditional BranchConditional BranchSplits the workflow into labelled condition branches.

The palette also exposes Approval, Notification, Integration, Human Task, Timer, Wait Until, Entry Point, and Request Edit. See the live palette capture for the complete read-only list.

Start, Stop, and flow control

NodeConfigureVerify
StartCaption.It is the intended workflow entry.
StopCaption.Every terminal path reaches a deliberate end.
Conditional BranchCaption and branch configuration, including each branch condition and label.Every branch has a label, valid condition, and connected next step.
Condition / Exclusive GatewayCaption and condition configuration.The true/false paths are connected and tested.
Entry PointCaption, label ID, maximum cycles.The label is unique and the cycle cap prevents unbounded loops.
Go ToCaption and target Entry Point node.The target exists and its loop policy is safe.
TimerCaption, delay value, delay unit.The duration is correct and a delay cannot strand an urgent task.
Wait UntilCaption, mode, absolute date/time and time zone or a date/time field, plus before-value and before-unit offset.The chosen field/time zone and offset produce the expected time.

People and form-task nodes

NodeConfigureVerify
ApprovalCaption, recipient, approval notification/message, require-comment option, no-action delay value and unit.The recipient is valid; approve, reject, comment-required, and timeout paths work.
Human Task (Dynamic Form)Caption, recipient, notification/message, no-action delay, and the form fields shown to the task user.Every required task field is valid and the assignee can complete it.
Form Fill (Assign Form)Caption, target form, recipient, notification/message.The target form exists, recipient is valid, and values flow as intended.
Request EditCaption, recipient, notification/message.The recipient can edit the intended submission and re-enter the workflow correctly.
NotificationCaption, recipient, notification/message.The message reaches only an approved recipient with usable context.

Data and external-action nodes

NodeConfigureVerify
HTTP RequestCaption, method, URL, authentication type, basic-auth user/password where selected, request-body type, parameters, and whether workflow continues after HTTP error.The HTTPS endpoint, method, authentication, payload, error response, and retry/continuation policy are correct. Do not put secrets in form fields.
BigData UpdateCaption, operation mode, collection/table, row updates, and (for update mode) row filter/where clause.The collection is authorized; the filter updates the intended row. Insert supports only supported Set row values.
IntegrationCaption, integration type, integration name.The selected integration is connected, authorized, and safely mapped/tested.

Build checklist

  1. Drag the node onto the workflow canvas and connect it to its predecessor.
  2. Select/open the node and complete the settings in the applicable table above.
  3. Connect every required continuation and branch.
  4. Save; correct any node-specific validation error rather than ignoring it.
  5. Run a test through every path, including missing recipient, invalid field, timeout, and external-service error paths where applicable.

Build better forms with AbcSubmit.