Alias User
vero.alias_user
ActionEmailconnection required
Calls the Vero API with the connection's credentials.
Change a user's identifier, merging the data held under the old one into the new one.
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
2 fields, 2 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 current identifier, the one being replaced. | string | Yes | — | — | 1000 |
new_id The identifier the user should carry from now on. | string | Yes | — | — | 2000 |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"id": "1000",
"new_id": "2000"
}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 | — |
id The identifier the user now carries. | string | — |
previous_id The identifier the user carried before. | string | — |
{
"id": "",
"message": "",
"previous_id": "",
"status": 0
}Notes
- Aliasing merges two identities into one and cannot be undone; Vero calls it an advanced operation.
See Alias User 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.