Set Conversation Tags

helpscout.update_conversation_tags
ActionBusiness appsconnection required

Calls the Help Scout API with the connection's credentials.

Replace a conversation's tags with exactly the list given; any tag left out is removed and any tag that does not exist yet is created.

Connection

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

Configuration

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

FieldTypeRequiredDefaultConstraintsExample
conversation_id
The numeric id of the conversation to act on.
stringYes———
tags
The complete tag list as a JSON array of names; send an empty array to clear every tag.
arrayYes—array of string—

Output

One shape.

result

FieldTypeExample
updated
True once Help Scout applied the tag change.
boolean—
moved
True when the conversation had been merged into another one and Help Scout answered a redirect instead of applying the write.
boolean—
status
The HTTP status Help Scout answered with.
number—
location
Where the merged conversation now lives, when moved is true.
string—
conversation_id
The conversation that was acted on.
string—
tags
The tag names that were sent.
array—
{
  "conversation_id": "",
  "location": "",
  "moved": false,
  "status": 0,
  "tags": [],
  "updated": false
}

See Set Conversation Tags run in a workflow.

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