Resources · Make integration

VIES API Make integrationAutomate VIES API with Make.

Need VIES data inside your workflows without copying it by hand? The VIES API Make integration gives you 4 action modules and no trigger. This page shows how to link your account, which module to pick, and how to build a first scenario you can test right away.

Try the VIES API integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the VIES API Make integration let you automate?

The VIES API Make integration links your VIES API account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that does one job. With it, a scenario can ask VIES API for data and pass the answer to the next app, with no manual lookup.

Enrich a record as soon as it lands. Because VIES API has no trigger, another app starts the flow: a new row, a new form entry, a new deal. Get VIES Data Parsed then fetches the VIES answer, and the next module writes it where your team works. Forms are a common starting point, as the 123FormBuilder Make integration shows.

Keep the raw answer when you need it. Get VIES Data is the sibling module. Judging by the two names, it should hand you the response unprocessed, as VIES API sends it. Test both with Run once and keep the one whose output fits your next step.

Watch your own account. Get Account Status reads the state of your VIES API account, which helps before a large batch. And when a need falls outside those three, Make an API Call reaches any endpoint of the API with the same connection.

Know the limits: the official documentation for this app is AI-generated and flags that it may contain mistakes, so check important details with VIES API itself. The same app may also exist as an n8n node; the n8n vs Make comparison lays out how the two tools differ, and the Make pricing page covers plans.

Connect

How do you connect VIES API to Make?

  1. 01

    Get your identifier and API key

    You need an active account on VIES API first. Log in, open the account dashboard, then find the section for API keys or authentication management. Copy the Identifier and the API key shown there and keep them at hand.

  2. 02

    Add a VIES API module in Make

    In your scenario, add any VIES API module and click Create a connection. A connection is your VIES API account linked to Make once, then reused by every module of the app. You can type a label in the Connection name field if you like.

  3. 03

    Paste your credentials and save

    Paste the identifier and the API key you copied, or follow the on-screen instructions, then confirm. Make stores the connection, and the module fields open so you can fill them in.

First scenario

Your first scenario with VIES API

GoalWhen a new record shows up in another app, Make asks VIES API for its data and hands the parsed result to the next step.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. VIES API has no trigger, so this first module comes from the app that holds your records.

  2. 02

    Pick the starting app

    Search for the app where new records appear, choose its module and link the account with Create a connection. Fill its fields; Make lists what it can read once the connection exists.

  3. 03

    Add Get VIES Data Parsed

    Click the + on the right of the first module, search for VIES API and pick Get VIES Data Parsed. Connect your account, then map the value it needs from the first module.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time, and you can open each module to read the bundles it received. A bundle is one item passed from a module to the next.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module with the clock icon; a new scenario runs every 15 minutes by default. Then switch the scenario on so it keeps working without you.

Modules

What can the VIES API modules do?

VIES API gives you 4 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

VIES API1

Get Account Status

ActionIn the docs only

This module gives you the current status of your own VIES API account, so a scenario can read it instead of you opening the dashboard. It is an action module, which means it runs once for each bundle it receives.

When to use it
put it at the start of a flow that is about to send many lookups, and route the scenario based on what it returns.
Watch out
the documentation lists no fields for it, so run it once and read the bundle before relying on any value.
VIES API2

Get VIES Data

ActionIn the docs only

Here you get the VIES answer for the value you send, and the next modules of the scenario can reuse it. Each run of the module counts as one operation, the unit Make tallies on your plan.

When to use it
pick it over the parsed version when, after a Run once, its unprocessed output suits you better, for instance to store it untouched.
Watch out
the documentation says nothing about its output, so test it with Run once and compare it with the parsed module.
VIES API3

Get VIES Data Parsed

ActionIn the docs only

Pick this one to receive VIES data that, as the module name indicates, comes back parsed, which should make mapping into the next app simpler. It is the natural choice for a first scenario.

When to use it
when a new customer record needs the VIES answer written straight into your CRM or spreadsheet.
Watch out
the exact shape of the parsed result is not documented; open the bundle after Run once before you map its values.
VIES API4

Make an API Call

ActionIn the docs only

With this module you can call any endpoint of the VIES API yourself, using the connection you already created. It covers whatever the three ready-made modules leave out.

When to use it
once you know the VIES API endpoint you need and none of the other modules reaches it.
Watch out
you build the request yourself, so check the vendor documentation first, since the Make documentation for this app warns it may contain mistakes.
Need help

Need help automating VIES API with Make?

A person reads every message.

FAQ

VIES API and Make: frequently asked questions

01Is the VIES API Make integration free?
Yes, on the Make side. VIES API is a standard app, so it is available from the Free plan. That plan allows 2 active scenarios, a minimum interval of 15 minutes between scheduled runs, runs of up to 5 minutes, files up to 5 MB and 512 MB of data transfer. Paid plans drop the interval to 1 minute and lift the limit on active scenarios. Your VIES API subscription is separate: the vendor documentation points to the VIES API pricing page for that part.
02What do you need to connect VIES API to Make?
You need an active account on VIES API, with an API key and a key identifier. Both are in the account dashboard, in the section for API keys or authentication management. In Make, add a VIES API module, click Create a connection, give it a name if you wish, then paste the identifier and the key. The connection is then shared by every VIES API module in your scenarios, so you only do this once.
03Does the VIES API Make integration react in real time?
No, because VIES API has no trigger module in Make. Every module is an action, so the scenario has to be started by something else. You can open it with a trigger from another app, such as a new form entry or a new row, or run it on a schedule set with the clock on the first module. A new scenario runs every 15 minutes by default, and the Free plan does not go below 15 minutes.
04What if a VIES API module is missing in Make?
Use Make an API Call. This module reaches any endpoint of the VIES API with the connection you already set up, so you are not limited to Get Account Status, Get VIES Data and Get VIES Data Parsed. Keep in mind that the Make documentation for this app is AI-generated and may contain mistakes. Before building a request, check the endpoint in the vendor documentation, and contact VIES API directly if something is unclear.
05Should you use Make or n8n for VIES API?
It depends on the tool your team already uses. In Make, VIES API comes with 4 action modules and a Make an API Call module for everything else, and the app is available from the Free plan. The same app may also exist as an n8n node. Compare what each tool offers for your exact case, test the modules you need, and keep the one that fits the rest of your automations.
Same platform

Other docs you might need on this stack.

Browse all integrations