Skip to main content
Node type: gmail_get_email · Version: 1 · Category: Communication Retrieve a Gmail message. This node is not marked with the catalogue’s generic side-effect flag. That classification is not a guarantee that every configured operation is read-only; review the concrete action and its destination.

​
When to use this node

  • Retrieve full message details after receiving an ID from a trigger or prior result.
  • Fetch content only on the branch that actually needs it.

​
Example: Load a triggered message

Use the same Gmail connection as New Email and map the trigger’s message ID.
Example settings
This shows the important settings, not a complete exported node. Connection and profile IDs are illustrative; select the real resource in the inspector.
  1. Select the Gmail connection.
  2. Map a message or thread ID from the trigger.
  3. Inspect the returned shape before mapping body, headers, or attachments.

​
Configuration

​
Workflow JSON

The editor stores this node with the following implemented default configuration:
Default node configuration
Values may be entered literally or mapped from an earlier compatible output when the inspector exposes a mapping control. See Variables and data mapping.

​
Inputs

This node has no typed ports in this direction.

​
Outputs

​
Execution behavior

  • The secure integration host resolves the credential and returns message data without exposing token material.
  • Reading is distinct from drafting, sending, or changing labels.
  • The editor catalogue declares result (any) for mapping. The execution inspector can contain additional evidence fields; inspect a real result before selecting nested paths from object or any outputs.

​
Common issues

  • A thread ID and message ID are not interchangeable in every provider operation.
  • Fetched email content can contain sensitive or hostile text; treat it as untrusted input.

​
Where it can run

  • Desktop local runner
  • Paired self-hosted runner
  • Hosted runner

​
Test and inspect

Use Test node in the editor to preview this step with the current configuration. A full run records resolved inputs, outputs, logs, duration, and any artifacts in the execution inspector. Side-effecting or destructive nodes can require an additional confirmation or approved workflow permission.