Edit User Tags
vero.edit_tags
ActionEmailconnection required
Calls the Vero API with the connection's credentials.
Add tags to a user's profile, remove tags from it, or do both at once.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Vero
- Secret shape
- the Vero auth token, or {"auth_token": "…"}
- Config it needs
- base_url
- Resolved by
- config.connection_id, else node.connection_id
Configuration
4 fields, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
id The user's unique identifier in your own product, as Vero's 'id'. | string | No | — | — | 1000 |
email The user's email address; use it when your product has no id for them yet. | string | No | — | email format | ada@example.com |
add Tags to add to the profile; a JSON array, or a comma-separated list. | array | No | — | array of string | ["prospect"] |
remove Tags to take off the profile; a JSON array, or a comma-separated list. | array | No | — | array of string | ["trial"] |
- At least one of id, email must be set.
- At least one of add, remove must be set.
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"add": [
"prospect"
],
"email": "ada@example.com",
"id": "1000",
"remove": [
"trial"
]
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
status The status code Vero echoed in its response body. | number | — |
message Vero's own message, which is 'Success.' when it worked. | string | — |
added The tags that were sent to be added. | array | — |
removed The tags that were sent to be removed. | array | — |
{
"added": [],
"message": "",
"removed": [],
"status": 0
}See Edit User Tags run in a workflow.
In a technical demo we add the Vero connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.