Replace Label

gmail.replace_label
ActionEmailconnection required

Calls gmail v1 PUT /gmail/v1/users/{userId}/labels/{id}.

Updates the specified label.

Connection

Required
Yes — the node will not save without one
Auth type
OAuth 2.0
Providers
Gmail
Secret shape
{"client_id", "client_secret", "refresh_token"}
Config it needs
token_uri
Resolved by
config.connection_id, else node.connection_id

Configuration

3 fields, 3 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
user
User name or id.
stringYes———
id
Id name or id.
stringYes———
body
The Label resource, as the API defines it.
objectYes———

Output

One shape.

result

Extra keys beyond the ones listed can appear.

FieldTypeExample
color
object—
id
string—
labelListVisibility
string—
messageListVisibility
string—
messagesTotal
integer—
messagesUnread
integer—
name
string—
threadsTotal
integer—
threadsUnread
integer—
type
string—
{
  "color": {},
  "id": "",
  "labelListVisibility": "",
  "messageListVisibility": "",
  "messagesTotal": 0,
  "messagesUnread": 0,
  "name": "",
  "threadsTotal": 0,
  "threadsUnread": 0,
  "type": ""
}

See Replace Label run in a workflow.

In a technical demo we add the Gmail connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.