List Drafts: 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 to filter drafts
Max Results maxResults	string	Optional	Max Results. e.g. "10"

Sample request

{
  "q": "e.g. subject:proposal to:john@example.com",
  "maxResults": "10"
}

Returns

{
  "drafts": [
    {
      "id": "r1234567890",
      "message": {
        "id": "msg123",
        "threadId": "thread123"
      }
    },
    {
      "id": "r0987654321",
      "message": {
        "id": "msg456",
        "threadId": "thread456"
      }
    }
  ],
  "resultSizeEstimate": 2
}

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

FAQ

Questions about List Drafts.

What does the List Drafts action do in Gmail?

Lists email drafts with full content from your Gmail account. Used for review queues where AI-generated drafts await approval.

What inputs does List Drafts require?

List Drafts 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 Drafts support batch operations?

Yes. Run List Drafts 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