The Input Node pauses a workflow to collect data from a user through one or more forms. Unlike the Trigger Input Node (which captures data at the start of a workflow), the Input Node can be placed at any point in a flow — making it ideal for multi-step processes where additional information, verification, or human action is needed mid-workflow.

When the workflow reaches an Input Node, it assigns a task to the configured user(s) and waits. The assignee sees the attached form(s) pre-populated with data from previous steps, fills in or updates the required fields, and submits. The workflow then continues to the next node.

When to Use

Use an Input Node when your workflow needs to:

Collect additional information from a user after the process has started (e.g., a finance team member adding budget codes after a manager approves a request).
Hand off a task to a different person or team mid-flow (e.g., routing an IT provisioning form to the infrastructure team).
Pause for human review or data entry before proceeding to an automated action or decision.
Request revisions or corrections on previously submitted data.

Configuration

Forms

Attach one or more forms to the Input Node. These forms define what data the assignee will see and fill in. Forms are created and managed separately in the Form Builder and linked to the node by their identifiers.

When the task is presented to the assignee, the system automatically pre-populates form fields with data submitted in earlier steps of the same workflow instance. This eliminates redundant data entry and gives the assignee full context.

If multiple forms are attached, you can enable Reorder Forms to allow the assignee to complete them in any order.

Task Assignment

Define who should receive the task when the workflow reaches this node. The following assignment types are available:

Assignment Type	Description
Audience	Assign to a predefined group of users (e.g., "HR Team", "Finance Approvers").
Users	Assign to one or more specific, named users.
Relation	Assign based on the initiator's organizational relationship — Manager, Skip-level Manager, HR, or a Dynamic relation resolved from workflow data.
DOA (Delegation of Authority)	Assign based on a configured DOA matrix, which routes tasks to the appropriate authority level based on business rules (e.g., approval thresholds).
Hybrid	Combine multiple assignment strategies in a matrix — for example, assign to both specific users and a relational role simultaneously.

A Default Assignee (Audience or User) can be configured as a fallback if the primary assignment cannot be resolved at runtime.

Escalation

When enabled, escalation automatically reassigns the task if the current assignee does not act within defined SLA thresholds. You can configure multiple escalation levels, each with its own time limit and target assignee. Escalation can also be applied within DOA-based assignments.

Each escalation level supports separate notification templates for the current assignee, the escalated assignee, and the requestor.

Auto-Action

Auto-action prevents workflows from stalling indefinitely. When enabled, the system automatically completes the task if the assignee does not act within a configured number of hours. The task is marked as auto-filled and the workflow proceeds to the next node.

The timeout duration can be a fixed number or a dynamic value resolved from workflow data (e.g., a form field or global constant).

Reminders

Reminders work alongside auto-action. When enabled, the system sends periodic notifications to the assignee at a configured frequency (in hours) until the task is completed or the auto-action deadline is reached.

Delegation

When delegation is enabled, the current assignee can delegate their task to another user. You can restrict who tasks can be delegated to by specifying allowed audiences or users. Notification templates for delegation events (new assignee, current assignee, delegated-by) are fully customizable.

Reassignment

Similar to delegation, reassignment allows an authorized user to transfer the task to a different person. Reassignment targets and notification templates are configured separately from delegation.

Revision Requests

When Request Revision is enabled, the assignee can send the workflow back to a previous step for corrections. You configure which earlier node the revision should be sent to. The target node must have a form attached — formless nodes cannot be selected as revision targets.

A separate navigation configuration can be set for what the user sees after requesting a revision.

Navigation

Navigation controls what the user sees after submitting the form.

Navigation Type	Description
Success Screen	Show a configurable success message after submission.
Render Document	Display a PDF or other document.
External Redirect	Navigate to an external URL (supports dynamic URLs built from workflow data).
Internal Redirect	Navigate to an internal application URL.

Additional options include a Back Button and a Popup on Navigate (confirmation popup with a custom message before navigating away).

Web Display Configuration

Control which contextual elements are visible to the assignee on the task page:

Option	Description
Show Progress Path	Display the workflow's step-by-step progress tracker.
Show Comments	Allow viewing and adding comments on the task.
Show Tags	Display any tags associated with the workflow item.
Show Initiated By	Show who originally started the workflow.
Show Note	Display additional notes or context.

Progress Path

You can optionally hide the Input Node from the progress path if it is skipped during execution. This keeps the progress tracker clean for the end user.

Notification Templates

Every key event in the Input Node lifecycle has a customizable notification template (both bot message and email):

Assignment: Sent when the task is assigned.
Rejection/Reassignment: Sent when a task is rejected and reassigned (with and without comment variants).
Revision Request Reassignment: Sent when a revision request routes the task back.
Auto-Complete: Sent when the system auto-fills the task (separate templates for initiator and assignee).
Reminder: Periodic reminders before the auto-action deadline.
Escalation: Separate templates for current assignee, escalated assignee, and requestor.
Delegation: Templates for the new assignee, current assignee, and the person who delegated.
Reassignment: Templates for reassignment events.

How It Works at Runtime

Workflow reaches the Input Node — the system evaluates the assignment configuration and determines who the task should be assigned to.
Notifications are sent — the assignee(s) receive bot and/or email notifications with the task details.
Timers begin — if escalation is configured, SLA timers start. If auto-action is enabled, the auto-fill countdown begins.
Form is pre-populated — data from previous workflow steps is pulled in and pre-fills the form fields.
Assignee interacts with the task — the assignee can fill in the form and submit, save as draft, delegate the task, or request a revision to a previous step.
On submission — the form data is saved and the workflow advances to the next node.
If no action is taken — reminders are sent at the configured frequency. If the auto-action deadline is reached, the system auto-fills the task and advances the workflow.

Best Practices

Always attach at least one form to your Input Node. Without a form, the assignee has nothing to interact with.
Set a default assignee as a fallback to prevent tasks from being unassigned if the primary assignment fails.
Enable auto-action for time-sensitive workflows to ensure the process doesn't stall if an assignee is unavailable.
Use reminders with auto-action — periodic nudges before the deadline significantly reduce the number of tasks that hit the auto-fill threshold.
Keep escalation levels reasonable — one or two levels with meaningful time gaps are typically sufficient.
Configure navigation thoughtfully — a clear success message or redirect after submission improves the end-user experience.