Resources · Make integration

Vision6 Make integrationAutomate Vision6 with Make.

What if your Vision6 lists kept themselves in sync with the rest of your stack? The Vision6 Make integration gives you 16 modules, 6 of them instant triggers, all about contacts. This guide shows you how to connect your account and build a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Vision6 Make integration do for you?

The Vision6 Make integration links your Vision6 email lists to the other tools you use, without writing code. In Make you build a scenario, which is simply the automation: a chain of modules, where each module is one brick such as a trigger, an action or a search. Vision6 brings contact-focused bricks to that chain.

Clean opt-outs everywhere. When someone leaves a list, Watch Unsubscribed Contacts wakes your scenario at once. Add Get a Contact to pull the full record, then pass it to your CRM or support desk so nobody writes to that person by mistake.

Signups that land in the right list. A form, a shop or a webinar tool can feed Vision6: Search Contacts checks whether the address already exists, then Create a Contact or Subscribe a Contact places it in the list you pick. No duplicates, no copy and paste.

A live view of your audience. Watch Added Contacts and Watch Updated Contacts can push each change to a spreadsheet or a reporting tool, which helps a sales team see fresh leads as they appear.

What the integration does not do: every listed module works on contacts. Campaigns, message sending and reports are not in the list, so for those you would reach for Make an API Call, which calls the Vision6 API directly with the same connection, provided the API exposes what you need. If you are weighing tools, the same app often has an n8n node too; the n8n vs Make comparison lays out the criteria, and the Make pricing page explains what each plan includes. For hands-on help, the Make training walks through scenarios like these step by step.

Connect

How do you connect your Vision6 account to Make?

  1. 01

    Create an API key in Vision6

    In Vision6, open Integrations from the sidebar, then the API Keys tab. Click Create API Key, give it a name, choose the access level and confirm. Copy the key and the REST API endpoint shown on the same screen.

  2. 02

    Add a Vision6 module in Make

    In your scenario, add any Vision6 module and click Create a connection. A connection is your Vision6 account linked to Make once, then reused by every Vision6 module. The Connection name field is optional but helps when you run several accounts.

  3. 03

    Paste your credentials and save

    Paste the API key and the endpoint you copied, or follow the instructions Make shows on screen, then save. Your Vision6 account needs full access and network access over port 443, otherwise the connection will not go through.

First scenario

Your first scenario: send form signups into a Vision6 list

GoalWhen someone fills in a form in another app, Make creates that person as a contact in your Vision6 list.

  1. 01

    Start a new scenario

    From the Scenarios page, create a new scenario and click the big +. Pick the form or signup tool you already use: its new entries become the starting point of the flow.

  2. 02

    Add Create a Contact

    Click the + on the right of that first module, search for Vision6 and choose Create a Contact. Click Create a connection and paste your API key and endpoint.

  3. 03

    Map the form answers

    Pick the target list, which Make can show once the connection works. Then map the name and email from the form into the contact. Each form entry travels as a bundle, one item passed from module to module.

  4. 04

    Test with Run once

    Click Run once, then submit a test entry in your form. Open the bubble above each module to read the bundles it received and check that the new contact appears in Vision6.

  5. 05

    Set the schedule and switch it on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, which you can keep or adjust within your plan. Then flip the scenario on and let it work.

Triggers

What can start a Vision6 scenario?

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

Vision61Watch Added Contacts

Watch Added Contacts

Instant trigger

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

Starts your scenario the moment a new person joins a Vision6 list you choose, and hands Make that contact so the next modules can use it right away.

How it fires
instant. Vision6 calls Make through a webhook as soon as the contact is added, so there is no waiting for a schedule.
When to use it
a sales rep wants every newsletter signup copied into the CRM with a follow-up task.
Watch out
click Create a webhook before Create a connection, and watch one list per trigger, since it listens to the list you specify.
Vision62Watch Deactivated Contacts

Watch Deactivated Contacts

Instant trigger

In Make“Triggers when a contact is deactivated from a list.”

Tells Make whenever a contact is deactivated in one of your lists, which lets you mirror that status in the tools that still hold the address.

How it fires
instant. Vision6 sends the event to Make by webhook the moment the deactivation happens.
When to use it
your support desk should tag the customer as inactive so agents stop sending marketing follow-ups.
Watch out
a deactivated contact is different from an unsubscribed one; pick Watch Unsubscribed Contacts if you care about opt-outs rather than status changes.
Vision63Watch Reactivated Contacts

Watch Reactivated Contacts

Instant trigger

In Make“Triggers when a contact has been reactivated in a list.”

Brings a returning contact back into your workflow: it fires when someone who had been deactivated becomes active again in a list.

How it fires
instant. Vision6 notifies Make through a webhook as soon as the reactivation is recorded.
When to use it
an account manager wants a heads-up in the team chat when a lapsed client is active again.
Watch out
if your scenario also runs Reactivate a Contact on the same list, you may trigger yourself; keep the two in separate flows with a clear filter.
Vision64Watch Subscribed Contacts

Watch Subscribed Contacts

Instant trigger

In Make“Triggers when a contact has subscribed to a list.”

Catches every new subscription to a list, so you can greet people or record the consent elsewhere while their interest is fresh.

How it fires
instant. Vision6 calls Make by webhook right after the contact subscribes.
When to use it
an events team logs each subscriber for a conference list into a shared attendee sheet.
Watch out
adding and subscribing are two separate events in Vision6, each with its own trigger; test with Run once to confirm which one your signup path produces.
Vision65Watch Unsubscribed Contacts

Watch Unsubscribed Contacts

Instant trigger

In Make“Triggers when a contact has unsubscribed from a list.”

Reacts when a person leaves a list, giving you the chance to respect that choice in every other tool that stores their details.

How it fires
instant. Vision6 pings Make through a webhook as soon as the unsubscribe happens.
When to use it
marketing ops must stop a sequence running in another platform for anyone who opts out of the Vision6 list.
Watch out
the event concerns one specific list; pair the trigger with Get a Contact if the next tool needs the full record.
Vision66Watch Updated Contacts

Watch Updated Contacts

Instant trigger

In Make“Triggers when a contact is updated in a specified list.”

Follows edits to contacts in a specified list, so a changed name, company or email reaches your other systems without anyone retyping it.

How it fires
instant. Vision6 alerts Make by webhook whenever a contact in that list is updated.
When to use it
a finance team keeps billing contacts aligned with what customers correct in their preference center.
Watch out
a scenario that ends with Update a Contact on the same list will fire this trigger again; add a filter or you create an endless loop that burns operations.
Modules

What can Make do in Vision6?

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

Vision61

Create a Contact

Action

In Make“Creates a contact.”

Puts a new person into Vision6 from data that arrives elsewhere, such as a form, a shop order or a CRM record, so your lists grow without manual imports.

When to use it
a lead fills in a quote request and should join your prospects list.
Watch out
run Search Contacts first if the same address might already exist.
Vision62

Deactivate a Contact

Action

In Make“Deactivates a contact from the list you choose.”

Switches a contact to inactive in the list you pick while keeping the record, which is the gentle option when someone should stop receiving mail but might come back.

When to use it
a customer cancels a subscription in your billing tool.
Watch out
this is reversible with Reactivate a Contact, unlike Delete a Contact.
Vision63

Delete a Contact

Action

In Make“Delete a contact.”

Removes a contact from Vision6 for good, useful when a person asks you to erase their data or when you clean up test entries.

When to use it
a deletion request comes in through your privacy form.
Watch out
a delete cannot be undone from Make, so test it on a dummy contact with Run once before switching the scenario on.
Vision64

Get a Contact

Action

In Make“Returns details for a specific contact.”

Fetches the full details of one contact when you already know its ID, giving the next modules the details Vision6 keeps for that person.

When to use it
a trigger hands you a contact and your CRM needs more than the basics.
Watch out
it needs the ID; with only an email, use Search Contacts.
Vision65

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the rest of the Vision6 API to your scenario, reusing the connection you already created, so you can reach anything the ready-made modules leave out.

When to use it
you need something outside contacts, such as campaigns, which no listed module covers; check first that the Vision6 API offers it.
Watch out
you write the request yourself, so keep the Vision6 API reference open while you set it up.
Vision66

Reactivate a Contact

Action

In Make“Reactivates a contact from the list you choose.”

Turns a previously deactivated contact back on in the list you choose, so a returning customer receives your emails again without being recreated.

When to use it
a client renews a plan after a pause.
Watch out
it only works on contacts that are deactivated; for someone brand new, use Create a Contact, and for opt-ins use Subscribe a Contact.
Vision67

Subscribe a Contact

Action

In Make“Subscribes a contact into your list.”

Adds an existing contact to one of your lists as a subscriber, which is how you move someone into a new audience such as a product update list or a training cohort.

When to use it
a customer ticks a box to receive product news.
Watch out
make sure the consent really exists in the source app before automating it.
Vision68

Unsubscribe a Contact

Action

In Make“Unsubscribes a contact from the list you choose.”

Takes a contact out of the list you pick when the opt-out happens in another tool, so Vision6 honors a choice made in your CRM or help desk.

When to use it
a client asks your support agent to stop the newsletter.
Watch out
other lists are untouched; add one module per list if the person should leave several.
Vision69

Update a Contact

Action

In Make“Updates a contact.”

Writes fresh details onto an existing Vision6 contact, keeping names, companies and other fields in line with the system your team treats as the reference.

When to use it
a deal owner corrects a job title in the CRM.
Watch out
if Watch Updated Contacts starts the same scenario, filter carefully to avoid a loop.
Vision610

Search Contacts

Search

In Make“Returns the contacts in the list that match the search criteria.”

Looks through a list and returns the contacts matching your criteria, the check you run before creating, updating or unsubscribing anyone.

When to use it
you receive an email address and need to know whether that person is already in Vision6.
Watch out
a search can return zero, one or several bundles, so plan a filter for each case.
Need help

Need help automating Vision6 with Make?

A person reads every message.

FAQ

Vision6 and Make: common questions

01Is the Vision6 Make integration free?
Yes, Vision6 is a standard app in Make, so it works on the Free plan. That plan gives you 2 active scenarios, a minimum of 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) lower the interval to 1 minute and remove the cap on active scenarios. Make counts usage in operations, one operation being one module run on one bundle. You still need your own Vision6 account, which is billed separately by Vision6.
02What does it take to connect Vision6 to Make?
You need an active Vision6 account with full access, an API key and network access over port 443. Create the key in Vision6 under Integrations, then the API Keys tab, choose an access level, and copy both the key and the REST API endpoint shown on that screen. In Make, add a Vision6 module, click Create a connection and paste those two values. For the instant triggers, Make first asks you to create a webhook, then the connection.
03Do the Vision6 triggers react in real time?
Yes. All six Vision6 triggers in Make are instant: Vision6 calls Make through a webhook as soon as a contact is added, updated, subscribed, unsubscribed, deactivated or reactivated. There is no polling interval to wait for, which is different from scheduled triggers that Make checks on a clock. Test each trigger with Run once to see the bundle Vision6 sends. Because the event comes from Vision6 itself, nothing reaches your scenario until the matching change really happens in a list.
04What if a Vision6 module is missing in Make?
Use Make an API Call. It sends any request to the Vision6 API with the connection you already set up, so you are not limited to the contact modules listed on this page. That is the route to try for anything outside contacts, like campaigns or reporting, which have no dedicated module, as long as the Vision6 API exposes it. The official documentation carries a note that its content is AI-generated from Vision6 sources and may contain mistakes, so check important details with Vision6 before building on them.
05Make or n8n: which fits Vision6 better?
It depends on the tool your team already knows. In Make, Vision6 comes with 16 ready modules, six of them instant triggers, plus Make an API Call for the rest, and it runs on the Free plan. The same app often has an n8n node as well. Pick the platform where your other scenarios already live and where your team is comfortable, and compare the criteria in the n8n vs Make comparison before committing a whole list workflow to one side.