WebsiteLegalPlatform

Operator Actions

Operator Actions enable human-in-the-loop workflows by pausing automation at critical decision points and requesting human approval or input before proceeding. These actions ensure that workflows can incorporate human judgment, authorisation, and data entry when needed.

Key Features

  • Request approval with customisable buttons for different decision paths

  • Request input with dynamic form fields for data collection

  • User and role-based assignment for task routing

  • Email notifications for assigned tasks

  • Integration with the Request Inbox for task management

  • Workflow branching based on human decisions

Available Operator Actions

Request Approval

Pauses the workflow to request a human decision with customisable button options.

Request Input

Pauses the workflow to collect information through a custom form interface.

How to Add an Operator Action

  1. Open the Add Action menu using one of three methods:

    • Click the "Add Action" button in the top left corner

    • Click on a connection circle on an existing action card

    • Click and drag from one node to create a connection

  2. Navigate to the "Operator Actions" section

  3. Choose either:

    • Request Approval - for decision-based approvals

    • Request Input - for data collection forms

  4. Click on your chosen action to add it to your canvas

💡 Operator Actions automatically create branching points in your workflow based on the human's response.

How to Configure Request Approval

Basic Configuration

  1. Title: Enter a clear title that describes the approval being requested

  2. Description: Provide detailed context to help the approver make an informed decision

  3. Buttons: Configure the decision options available to the approver

  4. Assignees: Specify who should receive and action this approval request

How to Configure Approval Buttons

  1. Click on each button to customise its properties

  2. For each button, you can set:

    • Label: The text displayed on the button

    • Style: Choose from available styles:

      • Default - Standard button appearance

      • Success - Typically for positive/approval actions

      • Secondary - For alternative options

      • Destructive - For rejection or deletion actions

      • Outline - For less prominent options

      • Link - For text-only button appearance

  3. Each button creates a separate branch path in your workflow

  4. The button clicked becomes the status of the completed task

⚠️ Each button represents a different workflow path, so ensure you connect appropriate actions to each branch.

How to Assign Approval Tasks

  1. Choose between two assignment methods:

    • Assign to specific user: Select individual users from your organization

    • Assign by role: Assign to all users with a specific role

  2. Multiple assignees can be selected for redundancy

  3. All assigned users receive email notifications when the task is created

💡 Using role-based assignment ensures tasks are always assigned even as team members change.

How to Configure Request Input

Basic Configuration

  1. Title: Enter a clear title describing the information needed

  2. Description: Provide context about why this information is required

  3. Form Fields: Configure the input fields for data collection

  4. Assignees: Specify who should provide this input

How to Set Up Form Fields

  1. Add form fields based on the information you need to collect

  2. Each field can be configured with:

    • Field type (text, number, date, etc.)

    • Field label

    • Required/optional status

    • Default values

  3. The collected data becomes available as variables in subsequent workflow steps

💡 Keep forms focused and only request essential information to improve completion rates.

Assignment Options

Assignment for Request Input works the same as Request Approval:

  • Assign to specific users

  • Assign by role

  • Multiple assignees supported

  • Email notifications sent automatically

How Operator Actions Work in Your Workflow

Workflow Execution Flow

  1. When the workflow reaches an Operator Action, it pauses execution

  2. Assigned users receive email notifications about the pending task

  3. The task appears in the Request Inbox with all relevant information

  4. Users complete the task by:

    • Clicking a button (for approvals)

    • Filling out and submitting the form (for input requests)

  5. Once actioned, the workflow continues based on the human's response

  6. Different responses follow different workflow branches

⚠️ Workflows remain paused at Operator Actions until a human completes the task. Plan for appropriate timeouts or escalations if needed.

Branching Logic

For Request Approval:

  • Each button creates a separate output path

  • Connect different actions to each button's path

  • The workflow follows the path of the clicked button

For Request Input:

  • Typically has one output path after form submission

  • Submitted data is available as variables for subsequent actions

Best Practices

For Request Approval

  • Use clear, action-oriented button labels (e.g., "Approve", "Reject", "Request More Info")

  • Provide sufficient context in the description for informed decision-making

  • Limit the number of buttons to avoid decision paralysis

  • Use appropriate button styles to indicate the nature of each action

For Request Input

  • Keep forms concise and focused

  • Use descriptive field labels

  • Mark required fields clearly

  • Provide helpful descriptions or examples for complex fields

General Guidelines

  • Always test the full workflow path including human interactions

  • Consider what happens if tasks aren't completed promptly

  • Use role-based assignment for better scalability

  • Monitor the Request Inbox regularly for pending tasks

💡 Operator Actions are perfect for compliance workflows, approval chains, data verification, and any process requiring human judgment or input.

Last updated