Resources · Make integration

Vero Make integrationAutomate Vero with Make.

What happens when a Vero email gets clicked, and who should know about it? The Vero Make integration gives you 17 modules: 8 instant triggers and 9 actions. This page shows marketers how to link the account, build a first scenario and pick the right module.

Try the Vero integration on MakeSee the 17 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Vero Make integration actually do?

The Vero Make integration lets Make listen to what happens in your Vero project and act on your users without code. A scenario (the automation you build in Make, a chain of modules) starts when Vero reports an email event or a user change, then tags, updates, tracks or unsubscribes people in Vero or passes the data to another app.

Engagement tags that write themselves. Start with Watch Email Clicked and follow it with Add Tags to a User. Anyone who clicks gets a tag, so your next segment is ready without an export. Remove Tags from a User does the reverse when someone changes plans or leaves a program.

One clean profile per person. When a signup form or your CRM holds new people, Identify a User creates them in Vero or updates the existing record. If the same person shows up under two identifiers, Alias a User merges both sets of data into one profile.

Consent kept in sync. Watch User Unsubscribed and Watch User Resubscribed tell Make the moment a preference changes, so your other tools can follow. The other way round, Unsubscribe a User and Re-subscribe a User apply a choice made elsewhere, for example in a support tool.

What Make does not cover out of the box: there is no search module and no scheduled trigger for Vero. For any other endpoint of the Vero API, Make an API Call uses the same connection. If you also work with n8n, the Vero n8n integration page covers that node, and n8n vs Make compares the two tools. New to the editor? The Make training walks through it step by step.

Connect

How do you connect Vero to Make?

  1. 01

    Copy your API token in Vero

    In Vero, open Settings, then Project Details, and copy the API token shown on screen. You need an active Vero account with access to API credentials; without it, Make has nothing to connect to.

  2. 02

    Add a Vero module and open the connection

    In your Make scenario, add any Vero module and click Create a connection. A connection is your Vero account linked to Make once, then reused by every Vero module. The Connection name field is optional, but a clear name helps later.

  3. 03

    Paste the token and save

    Paste the token you copied from Vero, or follow the on-screen instructions, then save. From now on, each Vero module in any scenario can pick this connection from a list instead of asking for the token again.

First scenario

Your first scenario: tag every Vero user who clicks an email

GoalWhen a user clicks an email in Vero, Make adds a tag to that user in Vero.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to add the first module. The first module decides when the whole scenario starts.

  2. 02

    Pick Watch Email Clicked

    Search for Vero and choose Watch Email Clicked. Click Create a webhook, then pick or create your Vero connection. Make now waits for Vero to report clicks.

  3. 03

    Add Add Tags to a User

    Click the + on the right of the trigger and pick Add Tags to a User. Map the user from the trigger's output into the module, then type the tag you want clickers to carry.

  4. 04

    Test with Run once

    Click Run once, then click a test email in Vero. Each module shows the bundles it received (a bundle is one item passed along, here one click). Check the tag landed on the right user.

  5. 05

    Switch the scenario on

    Turn the scenario on. With an instant trigger, it runs each time Vero calls Make, and every module run counts as one operation (the unit Make counts on your plan).

Triggers

What can start a Vero scenario?

8 modules start a scenario when something happens in Vero. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Vero as soon as it happens.

Vero1Watch Email Clicked

Watch Email Clicked

Instant trigger

In Make“Triggers when an email is clicked.”

Starts your scenario the moment a recipient clicks a link in an email sent by Vero, so a click becomes something you can act on instead of a number in a report.

How it fires
instant, Vero calls Make through a webhook as soon as the click happens.
When to use it
a prospect clicks the pricing link in your nurture email and you want a tag added or a sales tool told right away.
Watch out
when you add it, click Create a webhook before Create a connection; without it, Make most likely never receives the click.
Vero2Watch Email Delivered

Watch Email Delivered

Instant trigger

In Make“Triggers when an email is delivered.”

Hands you proof that an email reached the inbox, one bundle per delivered message, ready to be logged in another tool or used as the first step of a follow-up.

How it fires
instant, Vero pings Make through a webhook as soon as delivery is confirmed.
When to use it
a transactional message such as an onboarding email must show up in your CRM timeline once it actually lands.
Watch out
delivery says nothing about reading; pair it with Watch Email Opened if engagement is what you need.
Vero3Watch Email Opened

Watch Email Opened

Instant trigger

In Make“Triggers when an email is opened.”

Tells Make who opened which email, so you can reward attention instead of guessing at it from a dashboard.

How it fires
instant, Vero notifies Make through a webhook as soon as the open is recorded.
When to use it
a customer finally opens the renewal reminder and your account manager should get a heads-up in their own tool.
Watch out
one person can open the same email several times; expect each open to arrive as its own bundle, and every module run to count as an operation.
Vero4Watch Email Sent

Watch Email Sent

Instant trigger

In Make“Triggers when an email is sent.”

Gives you a record of every email Vero sends, the earliest signal in the email chain, before delivery or opens exist.

How it fires
instant, Vero calls Make through a webhook as soon as the email goes out.
When to use it
you keep a shared log in a spreadsheet or database of every message a key account received from marketing.
Watch out
sent is not delivered; if a bounce matters to you, build on Watch Email Delivered instead.
Vero5Watch User Created

Watch User Created

Instant trigger

In Make“Triggers when a user is created.”

Reacts to a new person appearing in your Vero project and passes their data to the rest of the scenario, ready to be copied into another app.

How it fires
instant, Vero alerts Make through a webhook as soon as the user exists.
When to use it
every new Vero profile should also land in your CRM or in a welcome channel for the growth team.
Watch out
if the same scenario feeds Identify a User, it could plausibly restart itself in a loop; test with Run once to be sure.
Vero6Watch User Resubscribed

Watch User Resubscribed

Instant trigger

In Make“Triggers when a user is resubscribed.”

Catches a person who opts back in to your emails, so every tool that stopped writing to them can start again with a clear conscience.

How it fires
instant, Vero tells Make through a webhook as soon as the resubscription happens.
When to use it
your support platform or SMS tool keeps its own consent flag and must follow the choice made in Vero.
Watch out
map the user identifier carefully, since the other app has to find the same person to update.
Vero7Watch User Unsubscribed

Watch User Unsubscribed

Instant trigger

In Make“Triggers when a user is unsubscribed.”

Signals an opt-out from Vero so the rest of your stack stops messaging that person too, which protects both your reputation and the reader's choice.

How it fires
instant, Vero calls Make through a webhook as soon as the unsubscribe is recorded.
When to use it
a lead unsubscribes and your CRM should flag the contact before a sales rep sends another sequence.
Watch out
test it with Run once and a real test unsubscribe before trusting it with consent data.
Vero8Watch User Updated

Watch User Updated

Instant trigger

In Make“Triggers when a user is updated.”

Follows changes to an existing Vero profile and sends the updated person to your scenario, so other tools never work from stale details.

How it fires
instant, Vero notifies Make through a webhook as soon as the profile changes.
When to use it
a customer updates their details in your product and your billing or support tool must show the same version.
Watch out
tagging the user from this same scenario probably counts as a change too; check with Run once that it does not wake itself up.
Modules

What can Make do in Vero?

Vero gives you 9 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Vero1

Add Tags to a User

Action

In Make“Adds tags to a user.”

Puts one or more tags on a Vero user so your segments and campaigns can target them without a manual export or a CSV import.

When to use it
right after Watch Email Clicked, to mark everyone who showed interest in a given offer.
Watch out
a tag is only as useful as its name, so settle on a naming rule before several scenarios start adding them.
Vero2

Alias a User

Action

In Make“Changes a user’s identifier. Also, the alias method is used to merge two user identities, merging two sets of user data into one.”

Changes the identifier Vero uses for a person, and can merge two identities so their two sets of data become one profile.

When to use it
an anonymous visitor signs up and you want their earlier activity attached to the new account.
Watch out
a merge folds two profiles together; run it once on a test user before plugging it into live data.
Vero3

Delete a User

Action

In Make“Deletes a user.”

Removes a user from your Vero project entirely, which is the clean answer to a deletion request coming from another system.

When to use it
a customer asks to close their account in your app and Vero must forget them as well.
Watch out
treat it as final; if you only want to stop emails, Unsubscribe a User is the safer choice.
Vero4

Identify a User

Action

In Make“Creates a new user or updates an existing one.”

Creates a new user in Vero, or updates the one that already exists, so you do not have to check first which case applies.

When to use it
a webinar signup or a new CRM contact should appear in Vero with current details, whether or not the person was there before.
Watch out
place it before tagging or tracking; those modules most likely need a user who already exists.
Vero5

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the rest of the Vero API from your scenario, reusing the same connection, for anything the eight other actions do not cover.

When to use it
you need an endpoint of the Vero API that has no dedicated module in Make.
Watch out
you build the request yourself, so keep the Vero API documentation open next to the module while you set it up.
Vero6

Remove Tags from a User

Action

In Make“Removes tags from a user.”

Takes tags off a Vero user so they drop out of segments that no longer fit, keeping your targeting honest without someone cleaning lists by hand.

When to use it
a trial user becomes a paying customer and the trial tag should disappear before the next trial email goes out.
Watch out
spell the tag exactly as it was added; a different spelling will likely remove nothing.
Vero7

Re-subscribe a User

Action

In Make“Re-subscribes a user.”

Puts a previously unsubscribed person back on your Vero mailing, applying a consent they gave somewhere other than Vero.

When to use it
a customer ticks the newsletter box again in your account settings or in a checkout form.
Watch out
trigger it only from a real opt-in event, never from a bulk import, since it overrides an earlier unsubscribe.
Vero8

Track an Event

Action

In Make“Tracks an event.”

Records something a person did outside Vero as an event on their profile, which your Vero campaigns can then react to.

When to use it
a purchase in your shop, a booked demo or an abandoned form should feed Vero so the right email follows.
Watch out
keep event names consistent across scenarios, or Vero sees two different events for the same action.
Vero9

Unsubscribe a User

Action

In Make“Unsubscribes a user.”

Stops Vero emails to a person while keeping their profile and history, the gentle alternative to deleting them.

When to use it
someone opts out through your support tool or your app, and Vero needs to respect that choice too.
Watch out
keep it apart from Watch User Unsubscribed; in one scenario, one would likely keep firing the other.
Need help

Need help automating Vero with Make?

A person reads every message.

FAQ

Vero and Make: common questions

01Is the Vero Make integration free?
Yes on the Make side. Vero is a standard app, available from the Free plan. That plan caps you at 2 active scenarios, a 15 minute minimum gap between scheduled runs, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute, remove the active scenario cap and count usage in credits per month. You still need an active Vero account of your own, whose subscription is set on Vero's pricing page.
02What do you need to connect Vero to Make?
An active Vero account with access to API credentials, and its API token. In Vero, go to Settings, then Project Details, and copy the API token on screen. In Make, add a Vero module, click Create a connection, optionally name it, and paste the token. For a trigger, click Create a webhook first, then Create a connection. The connection is saved once and every Vero module reuses it, in this scenario and in the next ones.
03Do Vero triggers in Make fire instantly?
Yes. All 8 Vero triggers are instant: Vero calls Make through a webhook as soon as an email is sent, delivered, opened or clicked, or a user is created, updated, unsubscribed or resubscribed. There is no scheduled Vero trigger, so the default 15 minute schedule does not apply to them. Remember to create the webhook when adding the trigger, then test with Run once while you trigger the event in Vero.
04What if a Vero module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Vero API with the same connection, so you are not limited to the 9 listed actions. There is no search module for Vero, which is often the gap people notice first. Also note that the Make documentation for Vero says it was generated from Vero's own documentation and may contain mistakes, so check important details against Vero and contact Vero directly for questions about their docs.
05Should you use Make or n8n for Vero?
It depends on what you need from Vero, since both tools have an integration for it. On Make you get 17 modules, including 8 instant triggers on emails and users, 9 actions and Make an API Call for the rest of the API. Compare that list with the Vero node on n8n before choosing. Neither page ranks one tool above the other; the n8n vs Make comparison linked above lays out the differences between the two platforms.
Same platform

Other docs you might need on this stack.

Browse all integrations