Short answer: Drop the "Gmail → Delete Label" 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 |
|---|---|---|---|
Label labelId | dynamic-options | Required | Gmail label ID (system labels like INBOX, SENT, or user label IDs like Label_123). Find via List Labels. |
{"labelId": "e.g. Label_1234567890"}
{"success": true}
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.