List conversations
list_conversationsLists threads, most recently updated first, with the contact, the subject of the mail and the one the team gave the thread ("team_subject", null until rename_conversation gives one), the ticket number of a helpdesk case (what the client quotes, null on somebody's mailbox), the status, where the thread stands in the pipeline, who is handling it, whether a draft is waiting for review, the folder each sits in and whether you have read it. Each thread also says since when its contact has been waiting for our answer ("waiting_since", their oldest message still unanswered, null when nobody waits), and when the last reply came and from which side ("last_reply_at", "last_reply_by"): the two figures a helpdesk queue is watched by, to tell which tickets drag. Name a "box" to read ONE mailbox exactly as its screen shows it: its Inbox by default, another folder on demand, and "unread" for the bold rows alone. Without a "box" it lists the whole account by pipeline status instead, which is a different question: a thread sitting unread in a mailbox has a status like any other, so a list by status is not the list of what is waiting to be read.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| box | No | The address of the mailbox to look in, for example "simon@sonentreprise.com": call list_sender_addresses to find it. A support queue is not a mailbox and has no folders. | |
| team | No | Narrows to the threads handed to one team, by its slug (list_teams gives it), taken by one of its members or not. Narrows the account list, so it does not go with "box". | |
| brand | No | The slug of a brand, to narrow to that subdivision of the account: call list_brands to find it. | |
| limit | No | How many threads to bring back, 1 to 200. Defaults to 100. | |
| before | No | Only the threads updated before this instant, as an ISO 8601 timestamp such as "2026-08-31T09:00:00Z". This is how you read past the first page: take the "updated_at" of the last thread the answer gave you and ask again with it. | |
| folder | No | Which folder of the box to list: one of inbox, sent, drafts, spam, trash, archive, or the id of a folder a person made (list_folders gives them). Defaults to the Inbox, like opening the mailbox does. Needs "box". | |
| status | No | Where the thread stands: "open" for one nobody has taken, "customer_reply" when the contact has written back, "answered" once we replied, "delivery_failed" when our reply bounced, "in_progress" while someone works on it, "closed" when it is over. | |
| unread | No | Only the threads you have not read: the bold rows of the screen, and the same count its Inbox shows. Needs "box". A key that acts for no person has no read state and is told so rather than answered with a list built for nobody. | |
| channel | No | The channel the thread runs on. Email is the usual one; "portal" carries the messages written from a client space. | |
| assignee | No | Narrows to the threads one person is handling, by the email address they sign in with, which list_people gives. The word "none" answers with what nobody has taken yet, which is the queue waiting to be shared out (a thread handed to a team has been shared out). Narrows the account list, so it does not go with "box". | |
| external_ref | No | Narrows to the threads of one contact identified by the reference a consumer app gave them, for example "epovest:account:42". |