MailMoo
Open MailMoo
DocumentationAPI referenceMCP
EndpointsInbox

List what needs attention

The whole triage queue as one paginated feed, already in priority order: people waiting on you first, then dates you set, then tasks you wrote, then leads that have gone silent. Each item carries the last message either way, so you can tell what is owed without opening the conversation.

GET/triage.getTriageFeed

Authorization

bearerAuth
AuthorizationBearer <token>

Enter your MailMoo API key (format: sk_live_...)

In: header

Query Parameters

cursor?integer

The nextCursor from a previous page.

Range0 <= value <= 9007199254740991
Default0
limit?integer
Range1 <= value <= 100
Default40
order?string
Default"newest"

Value in

  • "newest"
  • "oldest"
search?string

Filter the queue to leads matching this text. Narrows the list only; triage.getTriageCounts is unaffected.

Lengthlength <= 200

Response Body

application/json

application/json

application/json

curl -X GET "https://example.com/triage.getTriageFeed"
{}

Count what needs attention GET

Returns how many leads sit in each bucket of the triage queue: waiting on a reply, due a catch-up, carrying a due task, gone quiet, stalled, or due to wake from on-hold. A lead lands in exactly one bucket, so the buckets sum to `total`.

Count unread conversations GET

Returns how many conversations have unread messages from a lead, across both channels. Cheap enough to poll: it is a count, not a list.