WebsiteLegalPlatform

Request Input Page

Request Input

The Request Input node pauses your workflow to collect information from users through customisable forms. When the workflow reaches this node, it creates a task in the assigned user's Request Inbox and waits for form completion before continuing.

Overview

Request Input is perfect for collecting:

  • Missing information that wasn't available at workflow start

  • User feedback and qualitative responses

  • File uploads and document attachments

  • Dynamic data based on previous workflow steps

  • Verification or confirmation of existing information

How to Add Request Input

How to add the Request Input node

  1. Click "Add Action" in the top left corner or click a connection circle on an existing node

  2. Navigate to the "Operator Actions" section

  3. Select "Request Input"

  4. The node appears on your canvas

  5. Connect it to your workflow sequence

Configuring Request Input

Title

How to set the request title

  1. Click on the Request Input node to open configuration

  2. Enter a clear, specific title in the "Title" field

  3. Use action-oriented language that tells users exactly what to provide

Examples:

  • "Provide Customer Feedback Details"

  • "Upload Project Documentation"

  • "Enter Budget Information"

Description

How to write effective descriptions

  1. In the "Description" field, explain what information is needed and why

  2. Include any formatting requirements or examples

  3. Set clear expectations for response time

  4. Reference relevant context from earlier workflow steps

Description best practices:

  • Explain the purpose behind the request

  • Provide examples for complex fields

  • Include deadlines if time-sensitive

  • Clarify what happens after submission

Form Fields

How to configure form fields

  1. Click "Add Field" to create new input fields

  2. Configure each field's name, type, and requirements

  3. Arrange fields in logical order

  4. Set appropriate validation rules

Available Field Types

Text

  • Single-line text input

  • Best for names, short descriptions, simple data

  • Can set character limits

Number

  • Numeric input with validation

  • Supports decimal values

  • Can set minimum and maximum ranges

Toggle

  • Boolean on/off switch

  • Perfect for yes/no questions

  • Set default state (enabled/disabled)

Single Select

  • Choose one option from a dropdown list

  • Create custom option lists

  • Good for categories and standardised responses

Multi Select

  • Choose multiple options from a list

  • Users can select several relevant items

  • Useful for tags, features, or multiple categories

Date Picker

  • Calendar-based date selection

  • Standardised date format

  • Can restrict date ranges

File Upload

  • Accept documents, images, and other files

  • Set file type restrictions

  • Configure file sise limits

Item List

  • Allow users to create dynamic lists

  • Users can add/remove multiple entries

  • Good for variable-length data collection

Lookup

  • Reference existing data or external sources

  • Connect to knowledge bases

  • Validate against existing records

💡 For detailed information about each field type, see the Form Triggers documentation as Request Input uses identical field configurations.

Field Configuration Options

How to configure individual fields

  1. Field Name: Internal reference for the data

  2. Field Label: What users see on the form

  3. Required/Optional: Whether the field must be completed

  4. Default Values: Pre-populated data when applicable

  5. Validation Rules: Constraints specific to the field type

Assignees

How to assign input tasks

Assign to Specific User:

  1. Select individual team members from the dropdown

  2. Best when specific expertise is required

  3. Ensures the right person provides accurate information

Assign by Role:

  1. Choose from available roles:

    • Owners: Organisation or project owners

    • Builders: Users who can create workflows

    • Operators: Users who can run workflows

  2. Automatically includes all users with that role

  3. Better coverage when specific people might be unavailable

💡 Consider who has the knowledge or access needed to complete the request accurately when choosing assignment method.

How Request Input Works

The Request Process

  1. Workflow Execution: Your workflow runs until it reaches the Request Input node

  2. Task Creation: A task is created in the assignee's Request Inbox

  3. Notification: Assigned users receive email notifications

  4. Form Completion: Users access and complete the input form

  5. Data Capture: Submitted information is stored as workflow variables

  6. Workflow Continuation: The workflow resumes with the new data available

What Users See

Assigned users receive:

  • Email notification with direct link to the task

  • Task in their Request Inbox with your title and description

  • Form with all configured fields

  • Clear indication of required vs optional fields

  • Submit button to complete the task

Using Submitted Data

How to access input data in subsequent steps

  1. Use variable syntax: {{request_input.field_name}}

  2. Reference in AI prompts, emails, or integrations

  3. Apply conditional logic based on submitted values

  4. Pass data to external systems

Available data includes:

  • All form field responses

  • Submission timestamp

  • User who completed the form

  • Any uploaded files

Form Design Best Practices

For Better Completion Rates

  • Keep forms as short as possible

  • Only request essential information

  • Use clear, descriptive field labels

  • Provide examples for complex fields

  • Group related fields together

For Data Quality

  • Choose appropriate field types for validation

  • Mark required fields clearly

  • Set reasonable default values where possible

  • Use consistent formatting across similar forms

For User Experience

  • Order fields in logical sequence

  • Provide help text for ambiguous fields

  • Minimise the number of required fields

  • Test forms with actual users before deployment

Common Use Cases

Customer Information Collection

  • Gathering additional customer details mid-workflow

  • Collecting feedback or satisfaction ratings

  • Requesting clarification on support tickets

Document and File Collection

  • Requesting supporting documentation

  • Collecting signed agreements or contracts

  • Gathering evidence or proof materials

Project and Task Management

  • Collecting project requirements

  • Gathering status updates from team members

  • Requesting resource allocation information

Approval Support Information

  • Collecting justification for approval requests

  • Gathering additional context for decision-making

  • Requesting budget or timeline details

Troubleshooting

Users not receiving requests

  • Check email settings in user profiles

  • Verify assigned users have proper permissions

  • Confirm users are active in the organisation

Forms not submitting

  • Ensure all required fields are completed

  • Check for validation errors

  • Verify field configurations are correct

Data not available in next steps

  • Check variable syntax in subsequent actions

  • Ensure field names match between form and usage

  • Verify workflow connections are proper

Low completion rates

  • Simplify forms by removing non-essential fields

  • Improve field descriptions and instructions

  • Follow up on pending requests

⚠️ Workflows remain paused at Request Input nodes until someone completes the form. Plan for appropriate follow-up procedures.

Last updated