Short answer: You can reply to message in Gmail by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Gmail Reply to Message action to a workflow, map its 5 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 |
|---|---|---|---|
Original 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. |
To to | Required | To. e.g. "recipient@example.com" | |
Reply Body body | html | Required | Reply Body. e.g. "<p>Thanks for your email...</p>" |
CC cc | string | Optional | CC. e.g. "cc@example.com" |
BCC bcc | string | Optional | BCC. e.g. "bcc@example.com" |
{"messageId": "e.g. 18a1b2c3d4e5f6","to": "recipient@example.com","body": "<p>Thanks for your email...</p>","cc": "cc@example.com","bcc": "bcc@example.com"}
{"id": "msg456","labelIds": ["SENT"],"threadId": "thread123"}
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.