Resources · n8n integration

Vero n8n integrationAutomate Vero with n8n.

Everything the Vero node touches starts with one identifier and one auth token. The Vero n8n integration exposes 8 operations across 2 resources, User and Event, from creating a profile to sending a named event. Vero has no trigger node, so another step starts the run.

Try the Vero integration on n8n See the 8 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Vero n8n integration actually cover?

The Vero node ships with n8n and groups 8 operations over 2 resources. The User resource holds the customer profile: create or update it, change its identifier, add or remove tags, unsubscribe, resubscribe, delete. The Event resource holds a single operation that sends a named event for one identified customer. That is the whole map.

Start with the profile. A signup form drops a row into a spreadsheet, the workflow (a chain of steps n8n runs for you) reads it, and user.create writes the profile into Vero under the identifier your own system already uses. If that identifier is new, the profile appears. If it is already there, the same step updates it, so you never need a branch to decide which case you are in. Pair it with Google Sheets and the whole intake runs without anyone opening Vero.

Then the lifecycle. Tags are plain strings on the profile, and two operations move them: user.addTags puts one on, user.removeTags takes it off. A trial that converts loses its trial tag and gains a paid one in the same run. When somebody opts out through a preference page, user.unsubscribe records it, and user.resubscribe reverses it later if they come back. Teams usually post the result into a channel with Slack so support sees the change before the customer writes in.

The third one is behavioral. event.track sends a named event against a customer, with any key value pairs you want to carry along. An order confirmation flow that already goes out through Gmail or SendGrid can send the same event to Vero in the branch right next to it.

When an endpoint of the Vero API is not in that list of 8 operations, the HTTP Request node calls it directly and reuses the same credential through predefined authentication, so nothing forces you to leave n8n for it.

One structural point worth knowing before you build: there is no Vero trigger node in n8n. A workflow about Vero starts with a Schedule Trigger on a fixed interval, an n8n Webhook (a URL another service calls) or the trigger of a different tool. If you are still comparing platforms before committing, the n8n review walks through the trade-offs.

Connect

How do you connect Vero to n8n?

01
Grab the auth token from Vero
You need a Vero account first. Open your project settings in the Vero app and copy the auth token it shows there. That token is the only secret the node asks for: Vero authenticates the n8n node with an API auth token, and there is no second method to pick between. Keep the tab open, you will paste the value in the next step.
02
Create the credential in n8n
In n8n, go to Credentials, create a new one and search for Vero. Paste the value into the Auth Token field and save. A credential is a saved set of login details: you write it once and every workflow on the instance can pick it, so a token rotation later is a single edit rather than a tour of your workflows.
03
Point the node at a resource and an operation
Drop a Vero node into the canvas and select the credential from its dropdown. Two fields decide what the node does: Resource, where you choose between User and Event, then Operation, which lists what that resource allows. Change the resource and the form under it changes too, because the required fields are not the same on both sides.

Actions

Every operation the Vero node ships with

The Vero node exposes 8 operations across 2 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
Resource	Create or Update	Delete	Add Tags	Alias	Remove Tags	Re-Subscribe	Track	Unsubscribe
User	✓	✓	✓	✓	✓	✓		✓
Event							✓

User

7 operations

Add tags to a user

user.addTags

What you see in n8n

Notes & use cases

Tags are how a Vero profile carries a label from the rest of your stack. This operation writes one or several onto a profile that already exists.

Key parameters

ID: the unique identifier of the user, usually read from the incoming item with an expression like {{ $json.field }}.
Tags: the tags to add, in a single string with a comma between each one.

Use cases

a webinar registration list runs through the workflow and every attendee profile picks up the session tag before the follow up sequence is prepared.

Change a user's alias

user.alias

What you see in n8n

Notes & use cases

Identifiers move. Alias replaces the identifier Vero holds for a customer with another one, in a single call.

Key parameters

ID: the old unique identifier of the user, the value Vero knows today.
New ID: the new unique identifier of the user, the value you want Vero to use from now on.

Use cases

a billing migration renumbers every account, and a run over the mapping table walks the old identifiers to the new ones so later operations still find the right profile.

Create or update a user

user.create

What you see in n8n

Notes & use cases

One operation covers both directions: it creates the profile behind an identifier, and updates that same profile when the identifier is already known to Vero.

Key parameters

ID: the unique identifier of the customer, the value your own system uses to name that person.
Data: key value pairs that represent the custom user properties you want to update, added one row at a time.

Use cases

the intake workflow behind a signup form writes plan, company and signup source onto the profile in the same step that creates it.

Delete a user

user.delete

What you see in n8n

Notes & use cases

Delete removes the profile that matches the identifier you pass. It is the last step of an erasure path, not something to wire into a loop by accident.

Key parameters

ID: the unique identifier of the user, which has to be the identifier and not the person's name or email.

Use cases

a deletion request lands in a form, an approval step gates it, and the workflow removes the matching Vero profile once somebody has signed off.

Resubscribe a user

user.resubscribe

What you see in n8n

Notes & use cases

Resubscribe puts a profile back into the subscribed state after an earlier opt out.

Key parameters

ID: the unique identifier of the user, the same value used when the profile was created.

Use cases

a customer walks back an opt out from a preference page, the page posts to an n8n webhook, and the workflow resubscribes the profile without anyone touching the Vero interface.

Remove tags from a user

user.removeTags

What you see in n8n

Notes & use cases

Labels that stay on a profile long after they stopped being true make later filters lie. This operation takes tags back off, one or several at once.

Key parameters

ID: the unique identifier of the user whose profile you are editing.
Tags: the tags to remove, in a single string with a comma between each one.

Use cases

a trial ends in a paid plan and the workflow strips the trial tag in the same run that records the conversion.

Unsubscribe a user

user.unsubscribe

What you see in n8n

Notes & use cases

Unsubscribe records the opt out on the Vero profile named by the identifier.

Key parameters

ID: the unique identifier of the user, matched against what Vero already stores for that person.

Use cases

a support agent marks a ticket as an opt out request, and the workflow carries it to Vero straight away instead of leaving it on a list somebody processes on Friday.

Event

1 operation

Track an event

event.track

What you see in n8n

Notes & use cases

The Event resource has one job: send a named event for a specific customer, with the properties that go with it.

Key parameters

ID: the unique identifier of the customer the event belongs to.
Email: the customer's address, in the name@email.com shape.
Event Name: the name of the event tracked, a value you choose and keep stable, such as order_placed.
Data: key value pairs that represent any properties you want to track with this event.

Use cases

a checkout workflow sends the event with the plan and the currency as properties.

Need help

Need help automating Vero with n8n?

A person reads every message.

FAQ

Questions that come up next

01Is the Vero n8n integration free?

Yes on the n8n side. The Vero node ships with n8n, so there is nothing to install and nothing extra to pay to use it. That holds on n8n Cloud, the hosted offer run by n8n, and on an instance you host yourself with Docker or npm under the Community Edition and its Sustainable Use licence. A workflow behaves the same way in both places, which means you can build on Cloud and move the same JSON onto your own server later. What a Vero account itself costs is a separate question and this page does not cover it.

02Which credentials are needed to connect Vero to n8n?

One credential, built around an API auth token. Vero supports a single authentication method for this node, so there is no OAuth flow or scope list to work through. You create a Vero account, open the project settings in the Vero app, copy the auth token shown there, and paste it into the Auth Token field of a new Vero credential in n8n. Credentials live outside the workflow: once saved, the same one appears in the dropdown of every Vero node you add, on every workflow of that instance, and rotating the token later means editing one record.

03What are the limits of the Vero node in n8n?

The node covers 8 operations spread over 2 resources, User and Event, and that catalogue is the boundary. When an endpoint of the Vero API sits outside it, the HTTP Request node calls that endpoint directly and reuses the same Vero credential through predefined authentication, so you stay inside n8n and keep the token in one place. Worth remembering as well: every parameter marked as required has to be filled. An empty required field stops the node during execution rather than sending an incomplete call, which is annoying in testing and useful in production.

04Does Vero trigger an n8n workflow in real time?

No, because there is no Vero trigger node in n8n. A workflow about Vero has to be started by something else. Three options cover nearly every case. A Schedule Trigger runs the workflow on a fixed interval, which fits batch work like a nightly pass over new rows. An n8n Webhook gives you a URL that another service calls, so your own app or form can start the run at the moment something happens. Or the trigger of another tool starts it, and the Vero node sits downstream as one step among others.

05n8n or Make for automating Vero?

It depends on where you want the automation to live. Make is hosted only, with no self-hosting option, and it bills per operation, so a workflow that fires often has a cost that grows with its volume. n8n runs on your own server or on n8n Cloud, and the same workflow moves between them, which matters when customer data has to stay under your control. The visual logic differs too: n8n leans on expressions and code steps for branching, Make on its own module chain. Pick on hosting, data control and cost model rather than on feature lists.

Grab the auth token from Vero

Create the credential in n8n

Point the node at a resource and an operation

Need help automating Vero with n8n?