Short answer: You can get full email in Gmail by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Gmail Get Full Email action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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. |
{"messageId": "e.g. 18a1b2c3d4e5f6"}
{"id": "msg_123abc","payload": {"parts": [{"body": {"data": "<base64 encoded body>","size": 1234},"mimeType": "text/html"},{"body": {"size": 204800,"attachmentId": "ANGjdJ8xyz..."},"filename": "report.pdf","mimeType": "application/pdf"},{"body": {"size": 51200,"attachmentId": "ANGjdJ9abc..."},"filename": "screenshot.png","mimeType": "image/png"}],"headers": {"To": "you@example.com","Date": "Wed, 16 Apr 2026 10:30:00 +0000","From": "alice@example.com","Subject": "Project Report"},"mimeType": "multipart/mixed"},"snippet": "Hello, please find attached...","labelIds": ["INBOX","UNREAD"],"threadId": "thread_456def","internalDate": "1713264600000","sizeEstimate": 256000}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.