Resources · Make integration

Mailvio Make integrationAutomate Mailvio with Make.

Keep your Mailvio contacts, lists and attributes in step with the rest of your stack. The Mailvio Make integration gives you 13 modules: one scheduled trigger, 10 actions and 2 searches. This guide connects your account, builds a first scenario and explains when each module earns its place.

Try the Mailvio integration on MakeSee the 13 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Mailvio Make integration do for you?

The Mailvio Make integration links your Mailvio account to Make, a visual tool where you chain modules into a scenario, the automation you build. It covers contacts, the lists they belong to and the custom attributes stored on each contact, so audience upkeep stops being a copy and paste job between tools.

New subscribers land in the right list. Watch New Contacts spots contacts added to Mailvio, and Add Contacts to a List files each one where your next campaign expects it. For a small online shop, that means a welcome segment that fills itself.

Your CRM and Mailvio agree on who is who. When a deal closes in another app, Get a Contact finds the matching person and Update a Contact rewrites their details. Remove Contacts from a List takes them out of a prospect sequence at the same moment.

Your data model stays tidy. List Contacts Attributes shows which custom attributes exist, and Create a Contact Attribute adds the one a new form needs before contacts start carrying it.

The official documentation gives no numeric limit for Mailvio, so plan around the limits of your Make plan instead, described on Make pricing. If you are weighing tools, n8n vs Make lays out the criteria, and Make training walks through scenario building step by step.

Connect

How do you connect Mailvio to Make?

  1. 01

    Copy your API key in Mailvio

    Log in to your Mailvio account. From your Dashboard, click API Details, then copy the API Key to your clipboard. That key is what Make uses to act on your account, so treat it like a password.

  2. 02

    Open the connection dialog in Make

    Add any Mailvio module to a scenario and click Create a connection. A connection is your Mailvio account linked to Make once; every Mailvio module in every scenario can reuse it afterwards.

  3. 03

    Name it and paste the key

    Type a clear label in Connection name, such as the account or brand it belongs to. Paste the key into API Key and click Continue. Make then lists the Mailvio data it can reach.

First scenario

Your first scenario: sort new Mailvio contacts into a list

GoalWhen a new contact appears in Mailvio, Make adds that contact to the list you choose.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big +. Search for Mailvio and pick Watch New Contacts as your first module.

  2. 02

    Link your account

    Click Create a connection and use the API key from your Mailvio Dashboard. Once saved, fill in the trigger's settings; Make reads what your account holds and offers it in the fields.

  3. 03

    Add the list action

    Click the + on the right of the trigger and choose Add Contacts to a List. Pick the target list, then map the contact coming out of the trigger so Make knows who to add.

  4. 04

    Test with Run once

    Add a test contact in Mailvio, then click Run once. Each module shows the bundles it received, a bundle being one item passed along, here one contact. Check that the right person reached the list.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set how often Make checks Mailvio; a new scenario runs every 15 minutes by default. Switch the scenario on and it keeps going without you.

Triggers

What can start a Mailvio scenario?

1 module starts a scenario when something happens in Mailvio. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Mailvio as soon as it happens.

Mailvio1Watch New Contacts

Watch New Contacts

triggerIn the docs only

This trigger brings every contact newly added to Mailvio into your scenario, one bundle per contact, so the modules after it can tag, file or copy that person elsewhere. It is the only Mailvio trigger.

How it fires
it is a scheduled trigger, meaning Make checks Mailvio on the scenario's schedule rather than being alerted the moment a signup happens. On the Free plan the shortest gap between checks is 15 minutes; paid plans go down to 1 minute.
When to use it
a signup form feeds Mailvio and you want each new name pushed to a list, a spreadsheet or your sales tool.
Watch out
each contact it brings in costs operations, the unit Make counts on your plan.
Modules

What else can Make do in Mailvio?

Mailvio gives you 12 modules in 3 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Contacts

7 modules
Mailvio1

List Contacts

SearchIn the docs only

Pulls a set of your Mailvio contacts into the scenario so you can export, audit or loop over them. As a search module it can return none, one or many bundles, and every module placed after it runs once per contact.

When to use it
you need a full snapshot of the audience in a sheet before a cleanup.
Watch out
a large result multiplies the operations spent by the modules downstream.
Mailvio2

Get a Contact

ActionIn the docs only

Fetches one specific contact so later modules can read their current details. Pick it over List Contacts when you already know which person you are after and want a single, predictable bundle.

When to use it
a support ticket arrives and you want the sender's Mailvio record before replying or updating anything.
Watch out
the scenario needs a reliable way to identify that person, mapped from an earlier module.
Mailvio3

Create a Contact

ActionIn the docs only

Adds a brand new person to Mailvio from data another app hands over, like a form entry, a checkout or a webinar registration. It is the entry point for anyone who does not exist in your account yet.

When to use it
a lead signs up somewhere Mailvio cannot see and you want them reachable by email.
Watch out
if that person may already be in Mailvio, look them up first so you update instead of creating twice.
Mailvio4

Update a Contact

ActionIn the docs only

Rewrites details on a contact who already exists, so Mailvio reflects what changed in your other tools. It keeps the same person and history rather than starting a new record.

When to use it
a customer edits their profile in your app, or a deal moves to won in your CRM, and Mailvio should know.
Watch out
map only the values you mean to change; then check the result with Run once before switching the scenario on.
Mailvio5

Delete a Contact

ActionIn the docs only

Removes a contact from your Mailvio account altogether, which suits erasure requests or clearing out records you no longer have a reason to hold. Reach for Remove Contacts from a List instead when the person should simply stop receiving one campaign.

When to use it
someone asks for their data to be erased.
Watch out
treat it as final and test on a dummy contact first.
Mailvio6

Add Contacts to a List

ActionIn the docs only

Places existing contacts into a Mailvio list, which is how you decide who receives which campaign. Pair it with the trigger or with Create a Contact so every newcomer lands in the right audience without a manual import.

When to use it
buyers of one product line should join the list for that line's follow-up emails.
Watch out
the contact must already exist in Mailvio; create it earlier in the flow if needed.
Mailvio7

Remove Contacts from a List

ActionIn the docs only

Takes contacts out of one list while leaving them in your account and in their other lists. That makes it the gentle option compared with Delete a Contact: the person just stops getting that particular sequence.

When to use it
a trial user converts, so the nurture list for trials no longer fits them.
Watch out
check you picked the right list and test with Run once first.

Contacts Attributes

4 modules
Mailvio8

List Contacts Attributes

SearchIn the docs only

Shows the custom attributes defined in your Mailvio account, the extra fields that describe a contact beyond the basics. Because it is a search, it can return several bundles, one per attribute.

When to use it
you are mapping a new form and want to see which attributes already exist before creating another.
Watch out
put an aggregator after it if you want one summary rather than one run per attribute.
Mailvio9

Create a Contact Attribute

ActionIn the docs only

Defines a new attribute in Mailvio so contacts can start carrying an extra piece of information, such as a plan name or a signup source. It shapes your data model, not a single person.

When to use it
a new form collects something Mailvio does not store yet and you want segments built on it.
Watch out
running it on every bundle tries to create the same attribute again; keep it out of loops.
Mailvio10

Update a Contact Attribute

ActionIn the docs only

Changes an attribute definition that already exists in Mailvio, so the whole account follows the new version. Choose it when the concept stays but its setup needs adjusting, rather than creating a near duplicate beside it.

When to use it
your team renames or reworks an attribute and Mailvio should match.
Watch out
every contact using that attribute is affected, so check the segments that rely on it.
Mailvio11

Delete a Contact's Attribute

ActionIn the docs only

Going by its name, it removes an attribute from a contact when that piece of information should no longer be kept; the documentation says nothing more. It helps when a data point is outdated or was collected by mistake.

When to use it
a customer asks you to drop a detail they shared, or a retired field still clutters your records.
Watch out
treat it as final, try it on a test contact first and check the segments that filter on that attribute.

Other

1 module
Mailvio12

Make an API Call

ActionIn the docs only

Calls any endpoint of the Mailvio API from your scenario, reusing the connection you already created. It fills the gaps when none of the ready-made modules does what you need.

When to use it
you need a Mailvio feature that has no dedicated module in Make.
Watch out
you build the request yourself, so keep the Mailvio API documentation open and test with Run once before switching the scenario on.
Need help

Need help automating Mailvio with Make?

A person reads every message.

FAQ

Mailvio and Make: common questions

01Is the Mailvio Make integration free?
Yes. Mailvio is a standard app, so it works on Make's Free plan like the other 3,000+ standard apps. The Free plan has limits: 2 active scenarios, at least 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lift the scenario cap, bring the interval down to 1 minute and allow 40 minutes of execution. Usage is counted in operations each month. Your Mailvio subscription is separate and not covered here.
02What do you need to connect Mailvio to Make?
You need an existing Mailvio account and its API key. In Mailvio, open your Dashboard, click API Details and copy the API Key. In Make, add a Mailvio module, click Create a connection, give the connection a name, paste the key into the API Key field and click Continue. The connection is then shared by every Mailvio module you add, so you only do this once per account. No other prerequisite is listed in the official documentation.
03Does the Mailvio trigger in Make work in real time?
No. Watch New Contacts is a scheduled trigger: Make checks Mailvio on the scenario's schedule instead of being notified the instant a contact is added. A new scenario checks every 15 minutes by default, which is also the shortest interval on the Free plan. Paid plans can check as often as every minute. If you need a quicker reaction, tighten the schedule, keeping in mind that every check that finds contacts spends operations.
04What if a Mailvio module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Mailvio API with the same connection as the other modules, so you are not limited to the 12 ready-made actions and searches. You write the request yourself, which takes a look at the Mailvio API documentation. The Make documentation for Mailvio lists no numeric limit, so the practical constraints come from your Make plan: execution time, interval between runs and monthly operations.
05Should you use Make or n8n for Mailvio?
It depends on the tool your team already runs. On Make, Mailvio offers 13 modules covering contacts, lists and contact attributes, a simple API key connection and Make an API Call for anything else. Whether n8n has a dedicated Mailvio node is not something this page confirms, so check its node list before deciding. Compare the two on the criteria that matter to you, such as how you prefer to build and how usage is counted, rather than on the app alone.
Same platform

Other docs you might need on this stack.

Browse all integrations