Resources · Make integration

VBOUT Make integrationAutomate VBOUT with Make.

Can Make keep your VBOUT contacts, campaigns and lists moving on their own? Yes. The VBOUT Make integration gives you 19 modules, 2 of them triggers. This guide is for marketers who already run VBOUT: connect your account, then build a first scenario step by step.

Try the VBOUT integration on MakeSee the 19 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the VBOUT Make integration do for you?

The VBOUT Make integration links your VBOUT account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules that runs on a schedule. Each module is one brick. Here, those bricks read, create and update your contacts, email lists, campaigns and social posts, so VBOUT reacts to your other tools without copy and paste.

Every new lead lands in VBOUT with its context. A form tool or a CRM sends the person to Make, Create a Contact adds them, and Create a Custom Event records where they came from. Your segments stay accurate without a single import.

Each email campaign gets its social echo. Watch Email Campaign Created spots the campaign once it is posted, and Create a Social Media Post prepares the matching message. One launch, two channels.

Your reports read VBOUT directly. Search Campaigns and List Contacts return every matching record, which you can push into a sheet or a database: the Airtable Make integration page shows that side.

Two limits to keep in mind. Both triggers are scheduled, so Make checks VBOUT at intervals rather than hearing from it instantly. And the official VBOUT page in Make's docs says itself that it was generated with AI and may contain mistakes: confirm anything important with VBOUT. An n8n node may exist for VBOUT as well; the n8n vs Make comparison helps you pick, and the Make pricing page explains how operations are counted.

Connect

How do you connect your VBOUT account to Make?

  1. 01

    Copy your VBOUT API key

    In VBOUT, open Settings from your dashboard, then API Integrations. Your API key is shown on that screen: copy it. You need an active VBOUT account for this, since Make signs in with that key.

  2. 02

    Add a VBOUT module and start the connection

    In your Make scenario, add any VBOUT module and click Create a connection. A connection is your VBOUT account linked to Make once; every other VBOUT module reuses it. The Connection name field is optional, but a clear name helps when you manage several accounts.

  3. 03

    Paste the key and save

    Paste the API key you copied from VBOUT, or follow the instructions Make shows on screen, then save. Make can now list the contacts, lists and campaigns it can read, so you pick them from menus instead of typing identifiers.

First scenario

Your first scenario: turn each new email campaign into a social post

GoalWhen an email campaign is posted in VBOUT, Make prepares a matching social media post in VBOUT.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. Search for VBOUT and pick Watch Email Campaign Created as the first module.

  2. 02

    Link your account

    Click Create a connection and paste your VBOUT API key. Once the connection exists, Make shows what it can read from your account, so the trigger settings come from menus.

  3. 03

    Add the social post

    Click the + to the right of the trigger and add Create a Social Media Post. Write the message and map data from the campaign bundle, the item the trigger passes along, into it.

  4. 04

    Test with Run once

    Post a test email campaign in VBOUT, then click Run once. Open the bubbles above each module to read the bundles they received and check the new post in VBOUT.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, which is also the shortest gap on the Free plan. Pick your interval, then switch the scenario on.

Triggers

What can start a VBOUT scenario?

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

VBOUT1Watch Contact Created

Watch Contact Created

Scheduled trigger

In Make“Triggers when a new contact is added to a list.”

This trigger picks up the contacts added to a list in VBOUT and hands each one to the next module as a bundle. It is the entry point for anything that should follow a new subscription.

How it fires
it is a scheduled trigger, so Make checks VBOUT on the scenario's schedule and picks up every contact added since the last check.
When to use it
send each new subscriber to your CRM, a sales channel or a spreadsheet, so the team sees them without logging in to VBOUT.
Watch out
every contact found counts as operations in the modules that follow, so a large list import can use a lot of your plan at once.
VBOUT2Watch Email Campaign Created

Watch Email Campaign Created

Scheduled trigger

In Make“Triggers when an email campaign is posted.”

Here the starting point is your email marketing: the scenario wakes up when an email campaign is posted in VBOUT and passes the campaign to the following modules. Handy when a campaign launch should ripple out to other channels.

How it fires
scheduled. Make asks VBOUT for new campaigns at the interval set on this module, not the moment you hit send.
When to use it
announce the campaign on social media with Create a Social Media Post, log it in a project board or alert the sales team.
Watch out
on the Free plan the gap between two checks is 15 minutes at least, so the follow-up never lands at the exact second the campaign goes out.
Modules

What else can Make do in VBOUT?

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

VBOUT1

Create a Campaign

Action

In Make“Creates a new email campaign.”

Builds a brand new email campaign in VBOUT from data flowing through your scenario, so content written elsewhere becomes a campaign without being pasted by hand.

When to use it
a blog post is published or a product sheet is approved, and you want the matching email campaign drafted straight away in VBOUT.
Watch out
run the scenario once on a test list first, so a mapping error never reaches your real subscribers.
VBOUT2

Create a Contact

Action

In Make“Creates a new contact.”

Adds one person to VBOUT as a new contact. It is the module that feeds your database from forms, webinars, shops or any app Make can read.

When to use it
someone fills in a form on your site or buys in your store, and they should join your VBOUT audience without an export and import.
Watch out
for someone who may already exist, look them up with Get a Contact or List Contacts first and choose Update a Contact when they are found.
VBOUT3

Create a Custom Event

Action

In Make“Creates a new custom event.”

Records a custom event in VBOUT, a trace of something that happened outside the tool. Your marketing can then react to behavior that VBOUT would never see on its own.

When to use it
a customer books a demo, pays an invoice or cancels an order in another app, and you want that moment logged in VBOUT for segmentation or follow-up.
Watch out
give each event a stable, clear name from the start, so the team can still read it later.
VBOUT4

Create an Email List

Action

In Make“Creates a new email list.”

Creates a fresh email list in VBOUT without opening the dashboard. Useful when your lists follow your projects rather than a fixed structure.

When to use it
a new event, a new client account or a new product line is created in another tool, and it deserves its own list in VBOUT from day one.
Watch out
check with List Email Marketing's that a list with the same name does not already exist, or you will end up with duplicates.
VBOUT5

Create a Social Media Post

Action

In Make“Creates a new social media post.”

Prepares a social media post inside VBOUT from your scenario's data. Your social calendar then fills itself from what happens in your other tools.

When to use it
an email campaign goes out, an article is published or a promotion starts, and the same news should reach your social accounts managed in VBOUT.
Watch out
map short fields into the message and review the first posts with Run once before switching the scenario on.
VBOUT6

Get a Campaign

Action

In Make“Retrieves an existing campaign.”

Fetches one existing campaign and returns its details to the next modules. You read a campaign you already know rather than searching the whole account.

When to use it
another module has just given you a campaign reference, for example Watch Email Campaign Created, and you need its full details to build a report line or a message.
Watch out
it targets a single campaign; to browse several, use Search Campaigns instead.
VBOUT7

Get a Contact

Action

In Make“Retrieves an existing contact.”

Retrieves one contact already in VBOUT so you can use their data later in the scenario. Think of it as a quick lookup before you decide what to do next.

When to use it
a support ticket or an order mentions a customer and you want to check what VBOUT knows about them before sending anything.
Watch out
test it with Run once on a contact you know, and read the bundle it returns before mapping anything from it.
VBOUT8

Get an Email List

Action

In Make“Retrieves an existing email list.”

Reads a single email list from VBOUT and passes its information along. It answers the question "which list is this, exactly?" inside a scenario.

When to use it
a trigger such as Watch Contact Created tells you a contact joined a list, and the next step needs that list's details, for a notification.
Watch out
map the list from an earlier module rather than typing it, so the scenario keeps working when lists change.
VBOUT9

Get a Social Media Post

Action

In Make“Retrieves an existing social media post.”

Pulls one existing social media post from VBOUT into the scenario. You get its content back to reuse, check or archive somewhere else.

When to use it
you want a copy of each post in a shared content library, or a teammate needs to review a post before an update goes out.
Watch out
it reads one post at a time, so feed it the right post from a previous module rather than guessing.
VBOUT10

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Sends any authorized request to the VBOUT API with the connection you already set up. It is your way out when none of the 19 modules does exactly what you need.

When to use it
VBOUT offers a feature in its API that the listed modules do not cover, and you still want it inside the same scenario.
Watch out
you write the request yourself, so keep the VBOUT API documentation open and test with Run once before going live.
VBOUT11

Update a Campaign

Action

In Make“Updates an existing campaign.”

Changes an existing campaign in VBOUT with fresh data from your scenario. Your campaigns stay in step with the source of truth, wherever it lives.

When to use it
a price, a date or an offer changes in your product sheet or project tool, and the campaign that mentions it has to follow.
Watch out
make sure the scenario targets the right campaign, found with Search Campaigns or Get a Campaign, before it edits anything.
VBOUT12

Update a Contact

Action

In Make“Updates an existing contact.”

Edits a contact that already exists in VBOUT, so their record reflects what your other tools know. Your segments stop relying on outdated records.

When to use it
a deal moves forward in your CRM or a customer changes their details in your shop, and VBOUT should hold the same information.
Watch out
pair it with Get a Contact or List Contacts to find the right person first, then map only the values that really changed.
VBOUT13

Update an Email List

Action

In Make“Updates an existing email list.”

Modifies an existing email list in VBOUT from inside your scenario. Handy when list settings depend on events happening in another tool.

When to use it
a project or event gets renamed elsewhere and the list that serves it should carry the new name straight away.
Watch out
find the list with List Email Marketing's or Get an Email List before changing it, so you never edit the wrong one.
VBOUT14

Update a Social Media Post

Action

In Make“Updates an existing social media post.”

Rewrites an existing social media post in VBOUT. Corrections and last-minute changes flow from your scenario instead of being done post by post.

When to use it
a promotion's end date moves or a link changes, and the posts already prepared in VBOUT need the new version.
Watch out
fetch the post with Get a Social Media Post first so you know exactly what you are about to overwrite.
VBOUT15

List Contacts

Search

In Make“Searches for contacts or lists them all.”

Searches your VBOUT contacts, or returns all of them, and sends each match to the next module as its own bundle. It is the module for bulk work on your audience.

When to use it
you want to copy a segment into a spreadsheet, check who is already in VBOUT before creating someone, or update many contacts in one run.
Watch out
it can return zero, one or many contacts, and every result costs operations downstream, so narrow the search as much as you can.
VBOUT16

List Email Marketing's

Search

In Make“Searches for email marketing's lists or lists them all.”

Finds your email marketing lists in VBOUT, or lists every one of them, and outputs one bundle per list. You get an overview of your lists that other modules can act on.

When to use it
you need the right list before adding a contact, or you want an inventory of all lists in a sheet for a cleanup.
Watch out
when several lists match, the next modules run once per list, and each run costs operations.
VBOUT17

Search Campaigns

Search

In Make“Searches for campaigns or lists them all.”

Looks up campaigns in VBOUT, or returns all of them, with one bundle per campaign found. This is the starting point for reports and bulk checks on your email marketing.

When to use it
you want a table of your campaigns in a spreadsheet, or you need to find the campaign to edit before Update a Campaign runs.
Watch out
an empty result is possible, so plan what the scenario should do when no campaign matches.
Need help

Need help automating VBOUT with Make?

A person reads every message.

FAQ

VBOUT and Make: frequent questions

01Is the VBOUT Make integration free?
Yes, on the Make side. VBOUT is a standard app, so it works from the Free plan. That plan allows 2 active scenarios, a gap of at least 15 minutes between two scheduled runs, 5 minutes of run time, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Make counts usage in operations, one per module run on one item. You still need an active VBOUT account, with its own subscription.
02What do you need to connect VBOUT to Make?
Two things: an active VBOUT account and its API key. In VBOUT, open Settings in your dashboard, click API Integrations and copy the key shown on screen. In Make, add a VBOUT module, click Create a connection, optionally name it, then paste the key. The connection is saved once and reused by every VBOUT module in every scenario. If Make refuses it, go back to API Integrations, copy the full key again and check that the VBOUT account is still active.
03Does the VBOUT trigger in Make work in real time?
No. Both VBOUT triggers, Watch Contact Created and Watch Email Campaign Created, are scheduled. Make checks VBOUT on the scenario's schedule and collects everything new since the last check. A new scenario runs every 15 minutes by default, which is also the minimum on the Free plan; paid plans go down to 1 minute. If your scenario needs to react faster, start it from another app that calls Make directly and use the VBOUT modules as actions.
04What if a VBOUT module is missing in Make?
There is a way out: VBOUT has the Make an API Call module, which sends any authorized request to the VBOUT API using the same connection as the other modules. It covers features the 19 listed modules leave aside, as long as the VBOUT API offers them. You write the request yourself, so keep the VBOUT API documentation at hand and test with Run once. Also note that the VBOUT page in Make's docs flags itself as AI-generated, so confirm details with VBOUT.
05Should you use Make or n8n for VBOUT?
It depends on the tool your team already knows. On Make, VBOUT comes with 19 modules: 2 scheduled triggers, 14 actions (Make an API Call among them) and 3 searches. The same app often has an n8n node too, so check its coverage for the operations you need. Pick the platform where the modules match your use case and where your team is comfortable building. The n8n vs Make comparison on this site lays out the criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations