How to get message in Gmail

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
Message ID messageId	string	Required	Gmail message ID — the hex string Gmail assigns to each message. Find via List Messages. Not the RFC822 Message-Id header.
Format format	options	Optional	Format. Options: Full (headers + body), Metadata (headers only), Minimal (IDs only), Raw (base64 encoded)

Sample request

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

Returns

{
  "id": "msg123",
  "payload": {
    "headers": []
  },
  "snippet": "Hello...",
  "threadId": "thread123"
}

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

FAQ

Questions about Get Message.

What does the Get Message action do in Gmail?

Gets a specific email message by ID. For full content with body and attachments, prefer Get Full Email which handles the message-payload walking for you.

What inputs does Get Message require?

Required: Message 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 Message support batch operations?

Yes. Run Get Message inside a Loop node to process arrays. TinyCommand handles Gmail's rate limits automatically so you don't have to throttle manually.

More actions