Resources · Make integration

VTEX Make integrationAutomate VTEX with Make.

Every new VTEX order can start a workflow on its own. The VTEX Make integration gives you 6 modules: one instant trigger, four actions and one search. This guide connects your store, then builds a first scenario that fetches and invoices orders.

Try the VTEX integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the VTEX Make integration do for your store?

The VTEX Make integration links your VTEX store to Make, a no-code tool where you build a scenario: a chain of modules that runs by itself. Each module is one brick, such as a trigger, an action or a search. With VTEX, the work centers on orders: spotting new ones, reading them, invoicing them and pulling lists.

React the moment an order lands. Watch Orders is an instant trigger, so VTEX tells Make through a webhook as soon as a new order is added. Chain Get an Order behind it and the next modules receive the full order, ready to send to a spreadsheet, a CRM or a team chat.

Close the billing loop. Invoice an Order assigns billing information to an order, so the order in VTEX carries the billing details once your invoicing tool has done its part.

Review a batch of orders. List Orders returns the orders that match your filters, one bundle (one item passed to the next module) per order, handy for a report or a cleanup.

What the listed modules do not cover, Make an API Call and Make an GraphQL API Call can reach through the same connection. The VTEX documentation in Make carries a warning that it is AI-generated and may contain mistakes, so check anything critical against VTEX itself. If you hesitate between tools, the n8n vs Make comparison lays out the criteria, the Make review gives the full picture, and Make training helps a team get started.

Connect

How do you connect your VTEX account to Make?

  1. 01

    Generate an app key in VTEX

    You need an active VTEX account with API credentials. In the VTEX Admin panel, open Account settings, then Account management and Application keys. Click Generate app key, pick roles and resources, then copy the API key and the API token.

  2. 02

    Add a VTEX module to a scenario

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

  3. 03

    Paste your credentials

    Enter the credentials you copied from VTEX, or follow the on-screen instructions, and save. Make can now read your store. From here on, each VTEX module you add simply offers this connection in a dropdown.

First scenario

Your first scenario: invoice each new VTEX order

GoalWhen a new order is added in VTEX, Make fetches its details and invoices it with your billing information.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + in the middle of the canvas. Search for VTEX and pick Watch Orders, the module that starts everything.

  2. 02

    Set up the webhook

    Click Create a webhook, then Create a connection with your API key and token. From now on, VTEX calls Make whenever a new order is added to the store.

  3. 03

    Fetch the full order

    Click the + on the right of the trigger and add Get an Order. Map the order coming from Watch Orders so this module reads the complete record, not just the notification.

  4. 04

    Invoice the order

    Add Invoice an Order after it. Map the same order and fill in the billing information your team uses, pulling values from Get an Order wherever they already exist.

  5. 05

    Test, then switch it on

    Click Run once and read the bundles each module received to check the mapping. When the result looks right, switch the scenario on so it runs for every new order.

Triggers

What starts a VTEX scenario?

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

VTEX1Watch Orders

Watch Orders

Instant trigger

In Make“Triggers when a new order is added.”

Watch Orders gives your scenario a starting signal each time a new order is added to your VTEX store. Each order arrives as one bundle, so everything after it works on that single order.

How it fires
instant, VTEX calls Make through a webhook as soon as the order is added, with no schedule to set.
When to use it
when a sale should kick off a follow-up, like alerting the warehouse team or logging the order in a sheet.
Watch out
the webhook must exist before the connection, so click Create a webhook first when you add the module.
Modules

What else can Make do in VTEX?

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

VTEX1

Get an Order

Action

In Make“Returns info about an order.”

You get the full information of one order in a single step, so the next modules can use every detail VTEX keeps about that sale.

When to use it
right after Watch Orders, or when another app hands you an order reference and you need the whole record.
Watch out
it works on one order at a time; for several orders, List Orders is the better pick.
VTEX2

Invoice an Order

Action

In Make“Invoice an order by assigning billing information.”

This module assigns billing information to one order in VTEX, so the store and your accounting tell the same story.

When to use it
once your invoicing tool has produced the invoice, to report it back to the order in the store.
Watch out
it works on one order at a time, so map the order from the previous module and the billing details your invoicing tool produced.
VTEX3

Make an API Call

Action

In Make“Make an API VTEX Call.”

When no ready-made module does what you need, this one lets you call any endpoint of the VTEX API, using the connection you already set up.

When to use it
for a VTEX feature that none of the five listed modules reaches, while staying on the same connection.
Watch out
you write the request yourself, so keep the VTEX API reference open while you build it.
VTEX4

Make an GraphQL API Call

Action

In Make“Make an GraphQL API Call.”

This module sends a GraphQL request to VTEX, for the parts of VTEX that answer through GraphQL, with the connection you already have.

When to use it
when the VTEX feature you target is exposed through GraphQL rather than the classic API.
Watch out
you write the query yourself; test it with Run once and read the returned bundle before mapping anything further down.
VTEX5

List Orders

Search

In Make“Retrieves a list of orders according to the filters.”

List Orders hands you every order that matches the filters you set, which turns a store-wide question into a list Make can process.

When to use it
to build a report, review orders in bulk, or fill a sheet with past orders.
Watch out
a search returns zero, one or many bundles, and each bundle costs operations in the modules that follow.
Need help

Need help automating VTEX with Make?

A person reads every message.

FAQ

Questions about the VTEX Make integration

01Is the VTEX Make integration free?
Yes, on the Make side. VTEX is a standard app, available from the Free plan. That plan allows 2 active scenarios, runs scheduled scenarios every 15 minutes at the most frequent, caps a run at 5 minutes and limits files to 5 MB with 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) bring the interval down to 1 minute and count usage in operations per month. You still need your own active VTEX account with API credentials.
02What do you need to connect VTEX to Make?
An active VTEX account with API credentials. In the VTEX Admin panel, go to Account settings, Account management, then Application keys, generate an app key with the roles and resources your scenarios need, and copy both the API key and the API token. In Make, add a VTEX module, click Create a connection, optionally name it, and paste those credentials. For Watch Orders, click Create a webhook first, then create the connection.
03Does the VTEX Watch Orders trigger react in real time?
Yes. Watch Orders is an instant trigger: VTEX calls Make through a webhook as soon as a new order is added, so the scenario starts without waiting for a schedule. That is different from a scheduled trigger, which Make checks at intervals, every 15 minutes by default. The other five VTEX modules do not start a scenario on their own; they run after a trigger, whether it comes from VTEX or from another app.
04What if a VTEX module is missing in Make?
Use Make an API Call. It reaches any endpoint of the VTEX API with the connection you already have, so a feature outside orders stays within reach. When the data you need lives behind VTEX GraphQL, Make an GraphQL API Call does the same job with a query. Keep in mind that the VTEX documentation in Make is flagged as AI-generated and may contain mistakes, so confirm important details with VTEX before relying on them.
05Should you use Make or n8n for VTEX?
It depends on the tool your team already runs. VTEX often has an n8n node as well, so the choice comes down to your criteria rather than to the app. On Make, you get the six modules described here, including an instant trigger on new orders and two universal API modules, all built visually in the scenario editor. Compare how each tool fits your existing automations, then pick the one your team will maintain comfortably over time.
Same platform

Other docs you might need on this stack.

Browse all integrations