Node Types & Assignment Methods
A workflow is made up of nodes, each representing one processing step. Different nodes support different assignment methods, giving you flexibility for any business scenario.
Node types
Start Node
The workflow entry point. Execution begins here when a member submits a request.
Task Node
A processing step in the workflow — someone (or a system) needs to take an action. Assignment methods (also apply to End nodes):
| Method | Best for |
|---|---|
| Assign to group | Any member of the group can handle it |
| Assign to manager level | Automatically finds the right manager based on the submitter's department |
| Assign to AI Agent | AI automatically reviews and makes a decision |
| Dynamic assignment | The previous approver picks the handler when submitting |
| API auto-execute | Calls an external API; the system completes the step automatically |
| Return to submitter | Lets the submitter revise and resubmit |
End Node
The final processing step of the workflow. Just like a Task node, an End node is assigned to a handler (group, manager, AI, etc.) — when that handler approves, the workflow is marked completed.
This means your last review step can itself be the End node. For example, if the flow is "submit → manager approval → done", the manager approval node should simply be an End node — there's no need to add an extra "return to submitter" node at the tail, unless you specifically want the applicant to confirm the result.
Conditional Branch
Routes the workflow based on form field values. For example: "Purchase amount > $50,000 → requires a second finance manager approval."
Assignment methods in detail
Assign to group
The most common method. Any group member can handle the task; once someone does, the workflow continues.
Best for: Tasks where any qualified person can handle it (e.g., anyone in the Finance team)
Assign to manager level
Uses the submitter's department structure to automatically find the right manager — e.g., "direct manager approval" or "Level 2+ manager approval."
One node can be approved several times. If you require Level 2 or above and the submitter's department sits at Level 3, this single node is first assigned to their direct manager, and once that manager approves it automatically moves up to the parent department's manager — the same node, approved twice. You do not need a separate node for each level.
If the next node uses dynamic assignment, only the last manager (the one whose level meets the requirement) is asked to pick the handler. The earlier managers simply approve and pass it up.
Best for: Level-based approvals (e.g., leave requests, expense reimbursements)
⚠️ Requires department structure to be set up first
Assign to AI Agent
An AI Agent reviews the form content and automatically approves or rejects based on your instructions.
Best for: Decisions with clear, describable rules (e.g., does the amount exceed policy? Is the format correct?)
Dynamic assignment
The handler is not fixed in the workflow design — whoever approves the previous node picks them at the moment of approval, from a user-selection dialog that appears when they submit.
If the previous node is an AI Agent, the AI picks the handler instead. See AI assigns the next handler.
Best for: Cases where the handler depends on the request content and can only be decided by the previous approver
API auto-execute
When the node is triggered, the system automatically calls an external API you've configured (e.g., Google Apps Script, Slack, ERP system).
Best for: Automated actions after approval (e.g., write to Google Sheets, send notifications)
Sending data (bodyMapping): Specify which form fields to send to the external system, and optionally rename the keys to match the external API's expectations. Format: {"external_key": "formFieldId"}. If not set, all form data is sent by default.
Receiving data (responseMapping): Specify which values from the external system's response should be written back to form fields. Format: {"response_key": "formFieldId"}. If configured but any key is missing from the response, the workflow is rejected.
Return to submitter
Lets the submitter correct and resubmit the form.
Best for: Incorrect data, missing attachments, or requests needing supplementary information
Conditional branches
Branches let one workflow take different paths based on form field values.
Example:
Purchase amount ≤ $50,000 → Direct manager approval → Done
Purchase amount > $50,000 → Direct manager approval → Finance manager confirmation → DoneTell SuperAdmin Agent your conditions
When describing your workflow, include branching logic: "Amounts over $50,000 need a second finance manager confirmation; under $50,000 just needs manager approval."