Skip to main content

Agents & inbox

An agent represents one automation or workflow that can ask humans for approval. Each agent has its own inbox of requests and its own credentials for the HTTP API.

Approval Inbox (home) — mobile

The main Approval Inbox screen lists your agents across workspaces. Use it to:
  • See pending counts per agent
  • Search by agent or workspace name
  • Optionally show only agents that have pending work (filter toggle)
This is usually the fastest way to see where human input is needed on mobile.

Approvals — web

In the web dashboard, open Approvals to list and filter requests (for example by status or agent) and respond in the browser. Mobile and web show the same underlying approvals for your access level.

Opening an agent

Select an agent to open its hub. You will see:
  • The agent’s name and workspace
  • Pending approvals (questions waiting for a human)
  • Entry points to Manage this agent, Settings, Credentials, Subscribers, and related actions (depending on your role)
On the web, open Agents in the sidebar, then an agent for Defaults, Notifications, and Settings pages.

Manage this agent

Open Manage (sometimes Manage this agent) for a shortcut hub that groups:
  • Credentials & access — Agent ID and workspace API keys
  • Subscribers — who gets push notifications for this agent
  • Configuration — name and default timeout settings
Use it when you know you need one of these areas but do not want to hunt through menus.

Responding to approvals

When someone (or an automation) creates an approval request:
  1. It appears in the inbox for that agent (and in the Approval Inbox list on mobile, or Approvals on web).
  2. Subscribers may receive a push notification on mobile if they opted in and are configured for that agent.
  3. Open an approval to read the question and context, then either:
    • Choose one of the suggested options, or
    • Enter a custom instruction if your workflow allows it.
If you open the mobile app from a notification, you may land on the approval detail screen for that request—use it the same way as opening the approval from the inbox. Only one final response wins; if multiple people open the same request, the server ensures a single resolved outcome.

Where to configure things