Resources · Make integration

Vend Make integrationAutomate Vend with Make.

What if every new Vend sale or customer could flow into your other tools on its own? The Vend Make integration gives you 14 modules, including 2 instant triggers. This guide shows you how to link your store account, then walks you through a first working scenario.

Try the Vend integration on MakeSee the 14 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Vend Make integration do for your store?

It links your Vend account to Make so customers, products and register sales move between Vend and your other apps without copy and paste. You build a scenario, which is the automation itself: a chain of modules, each one a single brick that watches, reads, creates or updates something in one app.

Customer records that stay in sync. Watch Customers fires when a shopper profile is created or edited in Vend, so the same person can appear in your mailing tool or CRM right away. Going the other way, Create a Customer and Update a Customer write profiles collected elsewhere, such as a signup form, back into Vend.

Sales that reach the rest of the business. Watch Sales reacts to each register sale as it is recorded or changed. Add Get a Sale behind it and the complete sale is ready to pass to a spreadsheet, an accounting app or a team chat.

A catalog fed from one place. Create a Product adds items to Vend from a supplier sheet or another system, and List Products returns the catalog when you need to compare or report on it.

What Make does not do here: there is no module to delete a record, and products cannot be updated with a listed module. For anything beyond the list, Make an API Call reaches the Vend API with the same connection. Want to see how the builder feels first? Read our Make review. If you also weigh another tool, the n8n vs Make comparison lays out the differences, and Make pricing explains how operations are counted.

Connect

How do you connect Vend to Make?

  1. 01

    Add a Vend module

    Open your scenario in Make, search for Vend and pick any module. Then click Create a connection. The connection is your Vend account linked once to Make and reused by every Vend module after that. For Watch Customers or Watch Sales, click Create a webhook first.

  2. 02

    Name the connection

    The Connection name field is optional, but a clear label such as the store name helps when you run several Vend accounts. Before you go further, check that your Vend account is active and that your access token carries the auditread scope.

  3. 03

    Authorize with your credentials

    Paste the credentials you copied from Vend, or follow the instructions Make shows on screen. For your own OAuth client, go to Settings then Client API Access in Vend, pick your client and copy the Client ID and Client secret.

First scenario

Your first scenario: add new signups to Vend as customers

GoalWhen someone signs up in another app, such as a form tool, Make creates that person as a customer in Vend.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. The first module is where the data comes from: here, the app that collects your signups.

  2. 02

    Set up the source module

    Search for your form or signup app, pick the module that watches new entries and create its connection. Each new entry will reach the next module as one bundle, meaning one item with its data.

  3. 03

    Add Create a Customer

    Click the + on the right of the first module, search for Vend and choose Create a Customer. Create your Vend connection, then map the name and email from the signup into the customer fields Make shows you.

  4. 04

    Test with Run once

    Submit a test signup, then click Run once. Open the bubble above each module to read the bundles it received, and check in Vend that the test customer now exists.

  5. 05

    Schedule and switch it on

    Click the clock on the first module to set the schedule, every 15 minutes by default, then turn the scenario on. Each module run on a bundle counts as one operation on your Make plan.

Triggers

Vend triggers: what starts a scenario

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

Vend1Watch Customers

Watch Customers

Instant trigger

In Make“Triggers when a customer is created or updated.”

Starts your scenario the moment a customer profile is added or edited in Vend, so a new shopper or a corrected email address reaches your other tools without anyone exporting a list.

How it fires
instant. Vend calls Make through a webhook as soon as the change happens; you do not wait for a schedule.
When to use it
when your mailing tool or CRM should hold the same customer records as the till, including later edits.
Watch out
edits fire it too, so a scenario that writes back to the same customer with Update a Customer can trigger itself again. Keep the write to another app.
Vend2Watch Sales

Watch Sales

Instant trigger

In Make“Triggers when a register sale is created or updated.”

Gives you each register sale as soon as it is rung up or changed in Vend, which is the starting point for reporting, alerts or bookkeeping built on what actually sold.

How it fires
instant. Vend notifies Make through a webhook right when the sale is created or updated.
When to use it
to post each sale to a shared sheet, to warn the team in chat about a large order, or to pass the sale to an accounting app.
Watch out
an updated sale fires again, so the same sale can arrive twice. Plan for that in the destination, for example by updating a row rather than adding a new one.
Modules

Vend modules: what each one does for you

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

Vend1

Create a Customer

Action

In Make“Creates a new customer.”

Adds a brand new customer profile to Vend from data gathered somewhere else, so staff at the counter find the person already on file.

When to use it
after a web signup, a loyalty form or an event registration, when the person does not exist in Vend yet.
Watch out
it always creates, so run List Customers first if duplicates are a risk.
Vend2

Create a Product

Action

In Make“Creates a new product.”

Puts a new item into your Vend catalog without typing it at the back office, which saves time when products are already described in another tool.

When to use it
when a supplier sheet or a product database gets a new line that should be sellable in the store.
Watch out
no listed module edits a product afterwards, so check the mapping with Run once before switching on.
Vend3

Create a Sale

Action

In Make“Creates a new register sale.”

Records a register sale in Vend from an order that happened elsewhere, so your sales history covers more than the physical till.

When to use it
when orders taken in another channel, such as a booking or a marketplace, should show up in Vend reporting.
Watch out
if Watch Sales is active on the same account, this new sale will fire it, so avoid chaining the two in one loop.
Vend4

Get a Customer

Action

In Make“Retrieves a specific customer.”

Fetches one specific customer from Vend when you already know which one you want, giving the next module the full profile to work with.

When to use it
after a step that hands you a customer reference, to pull the profile before sending an email or updating a CRM.
Watch out
it needs that exact reference; to look someone up without it, List Customers is the better choice.
Vend5

Get a Product

Action

In Make“Retrieves a specific product.”

Returns a single product from your Vend catalog, which lets a scenario enrich a message or a report with the item's details instead of a bare reference.

When to use it
when an earlier module gives you a product reference and the following step needs more than that about the item.
Watch out
it reads one product only; to go through the catalog, List Products does the job.
Vend6

Get a Sale

Action

In Make“Retrieves a specific register sale.”

Pulls the complete record of one register sale, so the next step works from the whole sale with every detail Vend keeps on it.

When to use it
right behind Watch Sales, or after any module that gives you a sale reference, before sending the sale to a sheet or an accounting tool.
Watch out
each call is one operation on your plan, so skip it when the trigger already hands over what you need.
Vend7

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the whole Vend API to your scenario, with the same connection, so you can reach an endpoint that the other modules do not cover.

When to use it
when you need an action missing from the list, for example an operation of the Vend API that none of the 14 modules offers.
Watch out
you write the request yourself, so read the Vend API documentation and check the answer with Run once before relying on it.
Vend8

Update a Customer

Action

In Make“Updates a customer.”

Changes an existing Vend customer instead of creating a second profile, so contact details corrected elsewhere reach the till.

When to use it
when someone edits their details in a portal or a form and Vend should follow.
Watch out
feeding it from Watch Customers on the same account can create a loop, since an update also fires that trigger.
Vend9

Update a Sale

Action

In Make“Updates a register sale.”

Edits a register sale already recorded in Vend, which keeps the sales history aligned when an order changes after the fact.

When to use it
when a sale created by Create a Sale from another channel is modified at the source and Vend has to match.
Watch out
an updated sale also fires Watch Sales, so keep the two out of the same circuit.
Vend10

List Customers

Search

In Make“Retrieves a list of all customers.”

Brings back your Vend customers as separate bundles, which is the way to check who is already on file or to export the list elsewhere.

When to use it
before Create a Customer, to see whether a person exists, or to fill a sheet with your customer base.
Watch out
it can return zero, one or many bundles, and every following module then runs once per customer.
Vend11

List Products

Search

In Make“Retrieves a list of all products.”

Returns the products of your Vend catalog one bundle at a time, handy for comparing the catalog with another source or building a report.

When to use it
when a sheet, a website or a supplier file should be checked against what Vend actually sells.
Watch out
a large catalog means many bundles, and each module placed after it spends operations on every one of them.
Vend12

List Sales

Search

In Make“Retrieves a list of all register sales.”

Gathers register sales from Vend as a series of bundles, useful for catching up on past sales that no trigger delivered.

When to use it
for a first import of existing sales into a sheet, before Watch Sales takes over for the new ones.
Watch out
it can return many sales at once, so test with Run once and watch the operation count before switching the scenario on.
Need help

Need help automating Vend with Make?

A person reads every message.

FAQ

Vend and Make: frequent questions

01Is the Vend Make integration free?
Yes, on the Make side. Vend is a standard app, available on the Free plan. That plan allows 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 drop the interval to 1 minute and remove the cap on active scenarios. You still need your own active Vend account, whose subscription is separate from Make.
02What do you need to connect Vend to Make?
An active Vend account and an access token with the auditread scope. In Make, you add a Vend module and click Create a connection, then give the connection a name if you like and enter your credentials. For your own OAuth client, Vend shows the Client ID and Client secret under Settings, then Client API Access. If Vend asks for a callback URI, use the Make address given in the documentation.
03Do Vend triggers in Make fire in real time?
Yes. Both Vend triggers, Watch Customers and Watch Sales, are instant: Vend calls Make through a webhook as soon as a customer or a register sale is created or updated. That is why you click Create a webhook before creating the connection. Keep in mind that updates fire the triggers as well, so the same customer or sale can arrive more than once. Because nothing waits on a clock, you do not need to set a schedule on these two triggers.
04What if a Vend module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Vend API with the connection you already have, which covers what the 14 modules leave out. Note that the Make documentation for Vend is marked as AI-generated from the official Vend documentation, so verify important details against Vend itself and test each call with Run once. If what you need lives in another app entirely, add that app's own modules to the same scenario next to the Vend ones.
05Should you use Make or n8n for Vend?
It depends on the tool you already build in. On Make, Vend comes with 14 modules, 2 instant triggers and Make an API Call for the rest, all usable from the Free plan. The same app often has an n8n node as well, so check which operations it offers before choosing. Compare the modules each tool gives you against your scenario rather than picking on reputation. The n8n vs Make comparison linked earlier on this page lays out the general differences between the two builders.
Same platform

Other docs you might need on this stack.

Browse all integrations