List Threads: Gmail action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Search Query q	string	Optional	Gmail search query (same syntax as the Gmail search box)
Max Results maxResults	string	Optional	Max threads to return (hard cap: 10)
Label labelIds	string	Optional	Comma-separated Gmail label IDs. Find via List Labels.

Sample request

{
  "q": "e.g. from:john@example.com is:unread after:2025/01/01",
  "maxResults": "10",
  "labelIds": "e.g. INBOX, UNREAD, STARRED"
}

Returns

{
  "threads": [
    {
      "id": "thread123",
      "messages": [
        {
          "id": "msg1",
          "payload": {
            "headers": []
          },
          "threadId": "thread123"
        }
      ],
      "historyId": "987654"
    }
  ],
  "resultSizeEstimate": 15
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about List Threads.

What does the List Threads action do in Gmail?

Lists email threads from Gmail with all messages and full content. Use for conversation-level workflows like CSAT analysis or AI summarization.

What inputs does List Threads require?

List Threads has no required inputs. Sensible defaults are applied if you leave fields blank.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Gmail returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does List Threads support batch operations?

Yes. Run List Threads inside a Loop node to process arrays. Tiny Command handles Gmail's rate limits automatically so you don't have to throttle manually.

More actions