Identify User

vero.identify_user

ActionEmailconnection required

Calls the Vero API with the connection's credentials.

Create a user profile in Vero, or update the properties of the one that already carries this identifier.

Ask about Vero All Vero nodes Provider API docs ↗

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
data Custom user properties to set, as a JSON object. Keys are yours to choose, apart from Vero's reserved language, timezone and userAgent.	object	No	—	—	{"first_name":"Ada","plan":"pro"}
channels Device tokens to attach to the profile: one object per device, each with type, address and platform.	array	No	—	array of object	[{"address":"DEVICE_TOKEN","platform":"android","type":"push"}]

At least one of id, email must be set.

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "channels": [
    {
      "address": "DEVICE_TOKEN",
      "platform": "android",
      "type": "push"
    }
  ],
  "data": {
    "first_name": "Ada",
    "plan": "pro"
  },
  "email": "ada@example.com",
  "id": "1000"
}

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 profile was written under.	string	—
email The email the profile was written under.	string	—

{
  "email": "",
  "id": "",
  "message": "",
  "status": 0
}

Related Vero nodes

See Identify 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.

Book a technical demo Talk to sales