Inbox summary
Count what is waiting in Inbox right now for each teammate: unanswered conversations, open and overdue escalations, and manual contact.
What each count means
Every count is a number of leads, grouped by the lead’s current owner. A lead counts at most once per column.How the response is organized
user_id from by_person as assigned_to in List escalations to see that person’s cases.
Filter by task
Addworkflow_id to count only leads active in that task (workflow in the API).
Before you start
- MCP keys need
leads:read. Full-access REST keys need nothing else. - Errors return a stable code in
error, such asinvalid_workflow_idorworkflow_not_found. Map the code to your own copy. - An AI connected to the Nexor MCP server reads the same counts with the
get_inbox_summarytool.
Authorizations
API key for authentication. Keys are prefixed with nxr_live_.
Query Parameters
Task ID (workflow in the API). Counts only leads active in this task. A malformed ID returns 400 invalid_workflow_id, and a task outside this account returns 404 workflow_not_found.
Response
Current Inbox counts per teammate.
true The task filter, or null for every task.
Sum of every teammate row and the unassigned row.
One row per teammate who has at least one lead in Inbox, sorted by unanswered, then escalated_open, then name.
Leads without an assigned teammate.