ActionGmailUpdated May 2026

How do I fetch a Gmail thread by ID?

Short answer: Drop the "Gmail → Get Thread" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 27 Gmail actions

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
Thread ID threadId	string	Required	Gmail thread ID — groups related messages. Find via List Threads.
Format format	options	Optional	Format. Options: Full (headers + body), Metadata (headers only), Minimal (IDs only)

Sample request

{
  "threadId": "e.g. 18a1b2c3d4e5f6",
  "format": "{{trigger.format}}"
}

Returns

{
  "id": "thread123",
  "messages": [
    {
      "id": "msg123",
      "payload": {
        "headers": [
          {
            "name": "Subject",
            "value": "Project Update"
          }
        ]
      },
      "snippet": "Hi, I wanted to discuss...",
      "labelIds": [
        "INBOX"
      ],
      "threadId": "thread123"
    },
    {
      "id": "msg456",
      "payload": {
        "headers": [
          {
            "name": "Subject",
            "value": "Re: Project Update"
          }
        ]
      },
      "snippet": "Thanks for the update...",
      "labelIds": [
        "INBOX"
      ],
      "threadId": "thread123"
    }
  ],
  "historyId": "987654"
}

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

Triggered by

Apps that pair well as the trigger for Get Thread.

Any of these apps can fire this action as part of a workflow.

Slack → Gmail

13 Slack triggers

Google Sheets → Gmail

2 Google Sheets triggers

FAQ

Questions about Get Thread.

What does the Get Thread action do in Gmail?

Gets a specific email thread with all its messages. Used to feed AI summarization or for conversation exports.

What inputs does Get Thread require?

Required: Thread ID. Every input accepts a static value or a variable from any upstream node in your workflow.

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 Get Thread support batch operations?

Yes. Run Get Thread 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