> For the complete documentation index, see [llms.txt](https://docs.lleverage.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lleverage.ai/canvas-actions/human-in-the-loop/request-approval.md). # Request Approval The Request Decision action pauses your workflow to request human approval or decision-making. It creates customisable decision requests with multiple button options and routes the workflow based on the user's choice. ### Overview Request Decision is perfect for: * **Approval workflows**: Get sign-offs on documents, proposals, or requests * **Decision gates**: Route workflows based on human judgment * **Quality control**: Review content or processes before continuation * **Compliance verification**: Ensure regulatory requirements are met * **Multi-option decisions**: Provide several response choices ### How to Add Request Decision **How to add the Request Decision node** 1. Click the "Add Action" button in the top left corner of your canvas 2. Navigate to the "Operator Actions" section 3. Select "Request Decision" 4. The node will be added to your workflow canvas 5. Connect it between the appropriate workflow steps ### Configuring the Request Decision Node #### Title Configuration **How to set the decision title** 1. Click on the Request Decision node to open its configuration 2. In the "Title" field, enter a clear, descriptive title 3. Use specific language that tells the assignee exactly what they're deciding 4. Keep titles concise but informative **Examples of effective titles:** * "Approve Marketing Campaign Budget" * "Review Customer Refund Request" * "Authorise Employee Time Off" #### Description Configuration **How to write the decision description** 1. In the "Description" field, provide comprehensive context 2. Include relevant information from previous workflow steps 3. Explain what the decision will trigger 4. Add any deadlines or urgency indicators **Best practice for descriptions:** * Include key details and background information * Reference specific amounts, dates, or criteria * Explain the consequences of each option * Keep language clear and professional #### Button Configuration **How to set up decision buttons** 1. Each decision option gets its own button configuration 2. Click on a button to customise it 3. Set the button text (what the assignee will see) 4. Choose the button style from these options: * **Default**: Standard button appearance * **Success**: Green styling for positive actions (like "Approve") * **Secondary**: Neutral styling for alternative options * **Destructive**: Red styling for negative actions (like "Reject") * **Outline**: Border-only styling for less prominent options * **Ghost**: Minimal styling for subtle actions * **Link**: Text-only styling for informational actions **Button configuration tips:** * Use clear, action-oriented language ("Approve", "Reject", "Request Changes") * Limit to 2-4 buttons to avoid decision paralysis * Match button style to the action type (Success for approvals, Destructive for rejections) * Order buttons logically with the most common action first #### Priority and SLA Deadline **How to set urgency** 1. Choose a **Priority** (Low, Medium, High, or Urgent) so assignees can see at a glance what needs attention first 2. Optionally set an **SLA deadline** for how long the request should take to resolve, so overdue requests stand out in the Request Inbox #### Attachments and Related Record **How to give the assignee more context** 1. Add **Attachments** to include files from earlier workflow steps, for example the invoice or document being decided on 2. Link a **Related record** by pointing the request at a data table record, so the assignee can open the record the decision concerns #### Assignee Configuration **How to assign decision tasks** 1. In the "Assignees" section, choose your assignment method: **Assign to Specific User:** * Select individual team members from the dropdown * Best for dedicated approvers or specific role holders * Ensures the right person handles domain-specific decisions **Assign by Role:** * Choose from available roles (Owners, Builders, Operators) * Automatically includes all users with that role * Better for coverage when specific people might be unavailable * Scales automatically as team membership changes > 💡 **Assignment Strategy**: Use role-based assignment for broader coverage, specific user assignment for specialised decisions. Requests can also be reassigned later from the Request Inbox if the wrong person received one. ### Workflow Branching with Request Decision #### How Button Responses Create Workflow Paths **Setting up branching logic** 1. Each button you configure creates a separate output connection point 2. The button clicked by the assignee determines which workflow path is followed 3. Connect different subsequent actions to each button's output 4. Design different workflow paths for different outcomes **Example branching scenarios:** * **"Approve" button**: Continue to next automation step * **"Reject" button**: Send notification email and end workflow * **"Request Changes" button**: Loop back to earlier workflow step * **"Escalate" button**: Assign to different approver or management #### Accessing Decision Data **How to use the decision in subsequent steps** 1. The chosen button and any reason given are stored as workflow variables 2. Reference them in later actions using variable syntax 3. The **resolvedBy** output tells you who resolved the request. Use it to assign a follow-up request to the same person, so one handler sees a case through end to end 4. Use the decision to customise subsequent workflow behaviour ### Best Practices #### For Clear Decision Requests * **Be Specific**: Clearly state what is being decided * **Provide Context**: Include all information needed for an informed decision, using attachments and a related record where they help * **Set Expectations**: Use the priority and SLA deadline to indicate urgency * **Include Relevant Data**: Reference key details like amounts, dates, or metrics #### For Button Design * **Logical Organisation**: Order buttons from most to least likely * **Visual Hierarchy**: Use styles that match button importance * **Clear Language**: Use action verbs that indicate exactly what happens * **Appropriate Quantity**: Stick to essential options only #### For Assignment Strategy * **Consider Coverage**: Ensure someone will always be available to respond * **Match Expertise**: Assign to people with relevant knowledge or authority * **Plan for Absences**: Use role-based assignment or multiple assignees for critical decisions * **Document Process**: Make decision criteria and expectations clear ### Working with Decision Tasks #### What Happens When a Decision is Requested 1. **Workflow Pauses**: Execution stops at the Request Decision node 2. **Task Creation**: A task is created in the assignee's Request Inbox 3. **Notification Sent**: Email notification sent to all assigned users 4. **Awaiting Response**: Workflow remains paused until someone responds 5. **Decision Recorded**: Button choice is saved with timestamp and user info 6. **Workflow Continues**: Execution resumes following the chosen button path #### Decision Task Details Assignees will see: * The title and description you configured * All available button options with their styling * The priority and any SLA deadline * Any attachments and the related record, if provided * Information about the workflow that generated the request > 💡 If a decision needs revisiting, a completed request can be re-opened from the Request Inbox, which rewinds the flow to that step. > ⚠️ **Important**: Workflows will remain paused until someone completes the decision task. Plan for appropriate timeouts or escalation procedures. ### Troubleshooting **Common Issues and Solutions** **Assignees not receiving notifications** * Verify email settings in user profiles * Check that assigned users have proper permissions * Confirm users are active in the organisation **Workflow not continuing after a decision** * Ensure button outputs are connected to subsequent actions * Check that the next actions don't have configuration errors * Verify the workflow is published and active **Too many options causing confusion** * Simplify to the most essential decision points * Use clear, distinct button labels * Provide detailed descriptions for complex scenarios --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.lleverage.ai/canvas-actions/human-in-the-loop/request-approval.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.