Resources · Make integration

Vertex Make integrationAutomate Vertex with Make.

Can Make keep your Vertex rows up to date without anyone copying data by hand? The Vertex Make integration gives you 7 action modules to create, read, update, upsert and delete rows. This page shows how to link your account, build a first scenario and pick the right module.

Try the Vertex integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Vertex Make integration do?

The Vertex Make integration lets a Make scenario, the automation you build in Make, write to and read from rows in Vertex. Every piece of the integration is an action module, one brick of the scenario, so the scenario starts from another app or from a schedule you set, then hands the work to Vertex.

A lead list that never duplicates. A form tool or CRM sends a new contact, and Upsert a Row either adds it or refreshes the existing row. Sales sees one line per contact, not three.

A status that follows the real work. When a ticket closes in your helpdesk, Get a Row finds the matching record and Update a Row changes its status, so the ops team reads the truth in Vertex.

A filtered list pushed where people look. Get Rows from a View pulls the rows a view already filters, and the next module posts them to chat or email for a manager.

What Make does not give you here: the Vertex app has no trigger, so nothing starts on its own when a row changes in Vertex. Make also flags its Vertex documentation as limited, so what each module does is read here from its name. When a listed module falls short, Make an API Call reaches the rest of the Vertex API with the same account link. Vertex may also exist as an n8n node; the n8n vs Make comparison helps you pick a tool, and the Make pricing page explains what each plan counts. For hands-on help, the Make training walks through scenarios step by step.

Connect

How do you connect Vertex to Make?

  1. 01

    Open a Vertex module

    In your scenario, add any Vertex module, for example Create a Row, then click Create a connection. A connection is your Vertex account linked to Make once and reused by every Vertex module afterward.

  2. 02

    Name it and authorize

    Give the connection a name you will recognize later, such as the workspace it points to. Then either approve Make on the Vertex page that opens, or paste the key Vertex gives you, depending on what Make asks for.

  3. 03

    Save and check the list

    Click Save. Back in the module, Make now lists the objects it can read from your account, which is the quickest sign that the link works before you fill any field.

First scenario

Your first scenario with Vertex

GoalWhen a new contact arrives in another app, Make adds it to Vertex or updates the row that already exists.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Since Vertex has no trigger, pick the app where contacts arrive, like your form tool.

  2. 02

    Set the starting module

    Choose that app's module for new entries, link its account, and fill its fields. This first module feeds the scenario with bundles, one item per new contact.

  3. 03

    Add Upsert a Row

    Click the + to the right of the first module, search for Vertex and pick Upsert a Row. Link your connection, then map the contact data from the first module into the Vertex fields Make shows.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open the bubble above each module to read the bundles it received, then check in Vertex that the row landed where you expected.

  5. 05

    Schedule and switch on

    On the first module, open the clock to set the schedule; a new scenario runs every 15 minutes by default. Switch the scenario on, and each run now keeps Vertex in step with the source app.

Modules

What can Make do in Vertex?

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

Vertex1

Create a Row

ActionIn the docs only

Adds a brand new row to Vertex from data another module passes along, so each new order or sign-up becomes a line without anyone typing it.

When to use it
choose it when every incoming item is truly new, such as a fresh form submission that should always produce its own record.
Watch out
it never checks whether the row already exists, so a repeated input leaves duplicates; Upsert a Row avoids that.
Vertex2

Delete a Row

ActionIn the docs only

Removes one row from Vertex, which keeps a list clean once a record no longer belongs there, like a cancelled booking or a lead that asked to be forgotten.

When to use it
place it after a module that tells you exactly which row to drop, often a Get a Row step.
Watch out
the row leaves Vertex for good as far as your scenario knows, so run it once on a test row before switching it on.
Vertex3

Get Rows from a View

ActionIn the docs only

Reads the rows that a Vertex view already shows, letting you reuse filters your team built in Vertex instead of rebuilding them in Make.

When to use it
pick it for a digest or a follow-up list, for instance every open request in a view named for the support team.
Watch out
if the view returns many rows and each comes out as its own bundle, as the name suggests, every later module runs once per row and counts operations.
Vertex4

Get a Row

ActionIn the docs only

Fetches one specific row so later modules can use its values, for example to read a customer's current plan before sending them a message.

When to use it
reach for it when you already know which row you need and want its full content, not a filtered list.
Watch out
it returns a single record; when you need several rows at once, a view read with Get Rows from a View fits better.
Vertex5

Make an API Call

ActionIn the docs only

Sends your own request to the Vertex API through the connection you already set up, which covers what the six ready-made modules leave out.

When to use it
turn to it when a Vertex feature you need has no dedicated module in Make, and you know which endpoint handles it.
Watch out
Make documents Vertex only lightly, so you will need the Vertex API reference itself to write the request correctly.
Vertex6

Update a Row

ActionIn the docs only

Changes values in a row that already exists, so a status, an owner or an amount in Vertex follows what just happened in another tool.

When to use it
use it when you are sure the row is there, such as marking an invoice paid after your billing app confirms payment.
Watch out
it needs the right row to act on; pair it with Get a Row or data mapped from an earlier step.
Vertex7

Upsert a Row

ActionIn the docs only

Writes a row whether or not it exists yet: as the word upsert means, the match is updated or a new row is created, so you keep one record per item.

When to use it
it suits syncs where the same contact or product may come back several times, like a CRM that resends edited records.
Watch out
test it with Run once on a known record first, to confirm Vertex matches the row you expect rather than adding a second one.
Need help

Need help automating Vertex with Make?

A person reads every message.

FAQ

Vertex and Make: common questions

01Is the Vertex Make integration free?
Yes, Vertex is a standard app in Make, available from the Free plan onward. The Free plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, lift the cap on active scenarios and allow 40 minutes per execution. Usage is counted in credits, where each module run on one bundle uses an operation.
02What do you need to connect Vertex to Make?
You need a Vertex account and a Make account. Make does not list any other prerequisite for Vertex. Add a Vertex module to a scenario, click Create a connection, optionally name it, then either authorize Make on the Vertex page or paste the key Vertex provides, and click Save. The same connection then serves all seven Vertex modules, including Make an API Call, so you only set it up once per account.
03Does the Vertex integration react in real time?
No, because the Vertex app in Make has no trigger at all. A scenario that uses Vertex starts from somewhere else: a trigger from another app, such as a form tool that sends new entries, or the schedule on the first module, which runs every 15 minutes by default. The Free plan cannot go below 15 minutes; paid plans go down to 1 minute. Vertex modules then act on each bundle that the first module passes along.
04What if a Vertex module is missing in Make?
It depends on what you need. The six ready-made modules cover creating, reading, updating, upserting and deleting rows. For anything else, the Make an API Call module lets the scenario call any endpoint of the Vertex API with the connection you already use. Keep in mind that Make marks its Vertex documentation as limited for lack of public information, so the Vertex API reference becomes your main guide when you write a custom request.
05Should you use Make or n8n for Vertex?
It depends on which tool your team already works in. Make offers Vertex as a standard app with seven modules and a Make an API Call module for the rest of the API. The same app often has an n8n node too, so check the n8n side before you decide. The deciding factor is usually where your other scenarios live, since keeping one automation tool means one set of connections to maintain and one place to debug.
Same platform

Other docs you might need on this stack.

Browse all integrations