Introduction
Requests is your central queue for handling requests from agents that need human input. When an agent reaches a point where it requires your approval or needs you to answer a question, it sends a request to Requests. You can review, respond to, and manage all of these requests in one place.Key Concepts
Request types:- Approval — The agent needs you to confirm or reject a decision before it can proceed.
- Question — The agent needs you to provide an answer or additional information.
- Pending — The request is waiting for your response. Your agent is paused until you act.
- Answered — You have responded and the agent has continued.
Where to Find It
Requests is located in the left sidebar under your workspace. A badge on the icon shows the number of pending requests so you can see at a glance when agents need your attention.Viewing Requests
The inbox lists all requests with their title, description, the agent that sent them, the request type, and a timestamp. Use the filters at the top to narrow the view:- By status — Show only Pending or Answered requests
- By type — Show only Approval or Question requests
Responding to Requests
To respond to a pending request:Open the request
Click on the request to open the detail panel.
Type your response
Type your response in the text field.
Submit your answer
Submit your answer. The agent will resume with your input.
Bulk Actions
When managing a large number of requests, use the bulk actions available at the top of the inbox:- Clear all pending — Removes pending requests from your inbox. They stay open, and you can still answer them from their Runs. Case approvals stay in your inbox because they need a decision.
- Clear all resolved — Removes answered requests from your inbox. They stay on their Runs.
- Clear all — Removes every request from your inbox. Requests stay on their Runs, and pending ones can still be answered there.
Who can answer an approval
An approval can be answered by:- the person who started the Run,
- the person a Case approval was assigned to,
- a team Owner, Administrator or Lead Builder.
403 and the approval stays open. A bulk answer still returns 200, and lists each refused request as skipped with status 403. Questions and Login requests can be answered there by any team member who can see them.
Chat apps are stricter. In Microsoft Teams, only the person who started the Run can answer a request. In Slack, only they can answer an approval; teammates who can see a question can still answer it. A Case approval follows the rule above in both.
Real-Time Notifications
Requests updates in real time. When a new request arrives:- A toast notification appears on screen.
- The sidebar badge counter increments.
API Webhook Status
For agent runs triggered via the API, Requests shows the webhook delivery status alongside the request details. This lets you verify whether external systems were notified when a request was created or resolved.Related
Monitor the First Week
Using Requests as a daily health signal during the first week after an agent goes live
Designing Human-in-the-Loop Workflows
When to add approval gates, escalation patterns, and how to manage exceptions at scale
Human-in-the-Loop
How to write AOP approval instructions and respond via Slack or Teams
Notifications
What each notification means and how to choose where you get it