Short answer: You can get attachment in Gmail by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Gmail Get Attachment action to a workflow, map its 2 inputs 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. |
Attachment ID attachmentId | string | Required | Attachment ID returned within a message's payload.parts[].body.attachmentId. Get from the parent message. |
{"messageId": "e.g. 18a1b2c3d4e5f6","attachmentId": "e.g. ANGjdJ_abc123..."}
{"data": "<base64 encoded file content>","size": 204800,"attachmentId": "ANGjdJ8..."}
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.