Create Missive Shared Label
The Create Missive Shared Label action creates one shared label in a Missive organization. It can create a root label or place the new label beneath an existing parent, control who can see the label, optionally auto-share conversations with one team, and check for matching siblings before creation.
When to Use This Action
Use this action when:
- You need to add one shared label to a Missive organization
- You want to create a root label or a nested label
- You want to control whether everyone or only admins and auto-shared users can see the label
- You want to auto-share conversations in the label with one Missive team
- You want the automation to detect an existing matching label before it creates another one
- You need the created or reused label ID in a later automation step
Don't use this action to rename or move an existing label. Use Update Missive Shared Label instead. To find existing labels, use List Missive Shared Labels.
How It Works
The action creates one label in the organization you choose, unless a label with the same name already sits beside it. Before it creates anything, it checks that the parent label and team you chose belong to that organization. If any check fails, the action creates nothing and follows your Error Handling choice.
Create a Root or Nested Label
Choose a Parent Label to create a nested label. Leave Parent Label empty to create a root label.
The locked selector shows labels from the selected organization. Unlock it to enter a parent label ID or text expression. If the organization uses a dynamic ID or text expression, the parent field uses manual mode because the editor cannot load an organization-specific label list in advance. Leave the manual parent value empty to create the label at the root.
Configure Visibility and Auto-sharing
The action treats label visibility and conversation auto-sharing as separate settings.
Label is visible to provides these choices:
- Everyone in the organization: Everyone can see and use the label. This is the default.
- Admins and auto-shared users: Only organization admins and users who receive auto-shared access can see and use the label.
Leave Auto-share with Team empty to avoid auto-sharing conversations with any team. Select one team to use Missive's native team access, which follows future membership changes for that team.
The action always disables organization-wide conversation auto-sharing and does not auto-share with individual users. Selecting Everyone in the organization makes the label visible to everyone, but it does not automatically share conversations in that label.
You can select Admins and auto-shared users without selecting a team. In that configuration, organization admins can use the label, but no team receives automatic conversation access.
Handle Duplicate Labels
Before creation, the action compares the label name with existing labels, ignoring letter case and any spaces at the start or end. A duplicate must have:
- The same name
- The same exact parent ID
- The same organization
Root labels only match other root labels. A label beneath one parent does not match a label with the same name beneath another parent.
| Matching labels | Return Existing Label If Duplicate | Behavior |
|---|---|---|
| None | Off or on | Creates one new label. |
| One | Off | Follows Error Handling and does not create a label. |
| One | On | Returns the existing label only when Missive confirms that its visibility and auto-sharing exactly match the request. Otherwise, follows Error Handling. |
| More than one | Off or on | Reports an ambiguous duplicate and follows Error Handling. |
The duplicate check reduces accidental duplicates, but another Missive client can create a matching label between the check and the create request.
Configuration
Shared Label
| Field | Description |
|---|---|
| Missive Connection | Select a Missive connection. Leave this empty to use your default Missive connection. |
| Label Name | Enter the new label name. This required field supports text expressions. The action removes spaces at the start and end of the name. |
| Organization | Select an organization, or unlock the field to enter an organization ID or text expression. |
| Parent Label | Select a parent in the organization, or unlock the field to enter a label ID or text expression. Leave it empty to create a root label. |
| Auto-share with Team | Optionally select one team in the organization, or unlock the field to enter a team ID or text expression. Leave it empty for no team auto-sharing. |
| Label is visible to | Choose Everyone in the organization or Admins and auto-shared users. Default: Everyone in the organization. |
| Return Existing Label If Duplicate | Return one matching sibling instead of reporting a duplicate error. Default: off. |
| Error Handling | Choose what the automation does if validation or a Missive request fails. |
Changing Missive Connection reloads organization, label, and team choices. Changing a selected organization clears a locked parent or team that does not belong to the new organization.
Returned Variables
The action returns one compact label object. It does not return an array or the Missive response wrapper.
| Property | Type | Description |
|---|---|---|
id | string | The Missive shared-label ID. |
name | string | The label name without parent names. |
parent_id | string or null | The direct parent label ID, or null for a root label. |
path | string | The full label path, including parent names. |
organization_id | string | The Missive organization ID that owns the label. |
When Return Existing Label If Duplicate reuses a label, the action returns that existing label in the same shape.
FAQs
What happens if I enter an unknown parent ID?
The action checks the parent against labels in the selected organization. If it cannot find exactly one matching parent, it does not create the label and follows Error Handling.
Can a failed create request still create a label in Missive?
Yes, in an uncertain connection failure, Missive may accept the request before the connection fails. The action does not automatically retry an uncertain create request because a retry could create a duplicate. Review Missive before retrying the automation manually.
What happens if I enter an unknown team ID?
The action checks the team against teams in the selected organization. If it cannot find exactly one matching team in that organization, it does not create the label and follows Error Handling.
Does Return Existing Label If Duplicate choose among multiple matches?
No. Multiple matches are ambiguous, so the action reports an error even when this option is on. A single match must also have the requested visibility and auto-sharing settings before the action can reuse it.