Update Missive Shared Label
The Update Missive Shared Label action renames one shared label, changes its parent, or performs both changes together. It validates the resulting hierarchy and checks for matching siblings before sending the update.
When to Use This Action
Use this action when:
- You need to rename an existing Missive shared label
- You want to move a label beneath another label
- You intend to move a nested label to the root
- You want to reject duplicate siblings and invalid hierarchy cycles before updating
Don't use this action to create a label. Use Create Missive Shared Label instead. To find label IDs and paths, use List Missive Shared Labels.
How It Works
The action changes only what you select in Fields to Update and leaves everything else about the label as it was. Before it changes anything, it checks that the new position makes sense: a label cannot become its own parent or move beneath one of its own child labels, and it cannot end up beside another label with the same name. If any check fails, the action changes nothing and follows your Error Handling choice.
Choose Fields to Update
Fields to Update controls which values change. Select at least one option:
| Option | Additional field | Behavior |
|---|---|---|
| Name | New Label Name | Changes the label name. The action removes spaces at the start and end of the name and requires a non-empty name. |
| Parent | Parent Update | Changes the label's hierarchy location. |
| Name and Parent | Both sets of fields | Renames and moves the label in one update. |
If you do not select Name, the action leaves the current name unchanged. If you do not select Parent, it leaves the current parent unchanged.
Change the Parent
When you select Parent, choose one Parent Update mode:
| Parent Update | Behavior |
|---|---|
| Move to Root | Intends to clear the current parent so the label becomes a root label. |
| Change Parent | Requires New Parent Label and moves the target beneath that label. |
The action rejects a target as its own parent. It also rejects moving a label beneath one of its descendants because that would create a hierarchy cycle.
Move to Root asks Missive to clear the label's parent. Missive's published documentation does not describe this operation, so after a root move, confirm in Missive that the label now appears at the top level. If it does not, move the label to the top level in Missive directly.
Avoid Duplicate Siblings
The action calculates the name and parent that the label will have after the selected changes. It then checks the other labels in the organization for a sibling with:
- The same trimmed name, ignoring letter case
- The same exact resulting parent ID
The action excludes the target label from this check. If another matching sibling exists, the action follows Error Handling and does not send the update. For a root move, the duplicate check compares the label with other root labels.
Configuration
Shared Label
| Field | Description |
|---|---|
| Missive Connection | Select a Missive connection. Leave this empty to use your default Missive connection. |
| Organization | Select an organization, or unlock the field to enter an organization ID or text expression. |
| Label to Update | Select the target label, or unlock the field to enter a label ID or text expression. |
Updates
| Field | Description |
|---|---|
| Fields to Update | Select Name, Parent, or both. You must select at least one field. |
| New Label Name | Enter the new name. This required field appears when you select Name and supports text expressions. |
| Parent Update | Choose Move to Root or Change Parent. This field appears when you select Parent. |
| New Parent Label | Select a new parent, or unlock the field to enter a label ID or text expression. This required field appears for Change Parent. |
| Error Handling | Choose what the automation does if validation or a Missive request fails. |
Changing Missive Connection reloads organization and label choices. Changing a selected organization clears locked label choices that do not belong to the new organization.
If Organization contains a dynamic ID or text expression, the editor cannot load organization-specific labels in advance. Label to Update and New Parent Label then use manual mode so you can supply IDs or text expressions. The action checks those IDs when it runs.
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 updated label name without parent names. |
parent_id | string or null | The resulting direct parent label ID, or null for a root label. |
path | string | The resulting full label path, including parent names. |
organization_id | string | The Missive organization ID that owns the label. |
FAQs
What happens when I select only Name?
The action changes the name and leaves the parent unchanged. It checks for a label with the new name beneath that current parent before updating.
What happens when I select only Parent?
The action keeps the current name and checks for a label with that name beneath the new parent or at the root before updating.
Can I move a parent beneath one of its children?
No. The action checks all descendants and rejects any move that would create a cycle.
What happens if the target or new parent ID does not exist?
The action does not send the update. It follows your Error Handling choice when it cannot find exactly one matching target or new parent in the selected organization.