Short answer: Drop the "Gmail → Create 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 Name name | string | Required | Label Name. Example: Projects/Active |
Show in Label List labelListVisibility | options | Optional | Show in Label List. Options: Show, Show if unread, Hide |
Show in Message List messageListVisibility | options | Optional | Show in Message List. Options: Show, Hide |
{"name": "e.g. Projects/Active","labelListVisibility": "{{trigger.labelListVisibility}}","messageListVisibility": "{{trigger.messageListVisibility}}"}
{"id": "Label_42","name": "Projects/Active","type": "user","labelListVisibility": "labelShow","messageListVisibility": "show"}
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.