Vero
Track users and their events into Vero Cloud: create and update user profiles, alias identifiers, edit tags, manage global subscription state and record events through the Track REST API.
OCNORA ships 7 typed Vero operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.
Before you connect Vero
- Authentication
- API key
- Credential
- the Vero auth token, or {"auth_token": "…"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
What you can do with Vero
Operations, grouped by what they do to your data.
Update 1
Delete and cancel 1
Other operations 5
A sample Vero workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Vero trigger is needed.
- 2Alias Uservero.alias_userChange a user's identifier, merging the data held under the old one into the new one.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 7
- Alias UserChange a user's identifier, merging the data held under the old one into the new one.vero.alias_user
- Delete UserDelete a user from Vero along with every property and event recorded against them.vero.delete_user
- Edit User TagsAdd tags to a user's profile, remove tags from it, or do both at once.vero.edit_tags
- Identify UserCreate a user profile in Vero, or update the properties of the one that already carries this identifier.vero.identify_user
- Resubscribe UserGlobally resubscribe a user who had been unsubscribed.vero.resubscribe_user
- Track EventRecord an event against a user, creating the user profile first when Vero has never seen them.vero.track_event
- Unsubscribe UserGlobally unsubscribe a user, so no Vero campaign reaches them.vero.unsubscribe_user
Vero questions
- How does OCNORA authenticate with Vero?
- With a stored API key credential, shaped the Vero auth token, or {"auth_token": "…"}. A connection test can check it when you add it.
- What can I automate with Vero?
- 7 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Vero operation I need is not listed?
- Where Vero has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Vero?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Vero calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
See your first Vero workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.