Short answer: Drop the "Gmail → Add Labels to Message" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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. |
Labels labelIds | dynamic-options | Required | Comma-separated Gmail label IDs. Find via List Labels. |
{"messageId": "e.g. 18a1b2c3d4e5f6","labelIds": "e.g. INBOX,Label_1234567890"}
{"id": "msg123","labelIds": ["INBOX","STARRED"]}
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.
Triggered by anything in the catalog. Free tier available. No credit card.