Resources · Make integration

VIESAC Make integrationAutomate VIESAC with Make.

Stop copying VAT audit results out of VIESAC by hand. The VIESAC Make integration gives you 7 modules: 6 actions and 1 search. This guide shows what they do, how to link your account, and how to build a first scenario that files a certificate for you.

Try the VIESAC integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the VIESAC Make integration do?

The VIESAC Make integration lets a Make scenario (the automation you build, a chain of modules) start VAT audits in VIESAC, read their results and download the matching certificates. A module is one brick of that chain. You pick the bricks, Make runs them in order, and nobody has to open VIESAC to copy anything. One caveat: Make describes none of these modules, so their roles here are read from their names.

A certificate filed with every new client. When a client is added in another tool, Create VAT audit starts the check and Download VAT certificate (PDF) fetches a document you can store next to the contract.

A readable export for your accounting tool. If the tool that receives the data prefers structured files, Download VAT certificate (XML) gives you the machine version of the same certificate.

A review of past checks. List VAT audits returns the audits already in your account, one bundle (one item passed to the next module) per audit, so you can copy them into a sheet or a report.

Keep expectations modest: Make publishes only limited documentation for VIESAC, with no field list and no troubleshooting notes, so test each module with your own account before you rely on it. If a module is missing, Make an API call reaches the rest of the VIESAC API. New to the editor? The Make training covers the basics, and n8n vs Make helps if you are still choosing a platform. Plan limits are detailed on Make pricing.

Connect

How do you connect VIESAC to Make?

  1. 01

    Add a VIESAC module

    In your scenario, click the +, search for VIESAC and pick any of its modules. Then click Create a connection. A connection is your VIESAC account linked to Make once and reused by every VIESAC module afterwards.

  2. 02

    Name the connection

    Give it a name you will recognize later, such as the company or the team it belongs to. This step is optional, but it saves guesswork the day you run several VIESAC accounts side by side.

  3. 03

    Authorize and save

    Depending on what Make asks for, either approve access on the VIESAC page that opens or paste the key VIESAC gives you. Click Save, and the module can now read your account.

First scenario

Your first scenario with VIESAC and Make

GoalWhen a new client arrives in another app, Make starts a VIESAC VAT audit and downloads the PDF certificate.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Your first module comes from the app where new clients show up: a CRM, say, or a form.

  2. 02

    Start the audit

    Click the + on the right of that module, search for VIESAC and choose Create VAT audit. Create the connection, then map the client data from the first module into the fields Make shows.

  3. 03

    Fetch the certificate

    Add Download VAT certificate (PDF) after it and map the audit it should read from the previous module. The file can then go to a storage app of your choice.

  4. 04

    Test with Run once

    Click Run once and let one real client go through. Then open each module's bubble to read the bundles it received and check that the certificate really came back.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default for a new scenario), then switch the scenario on. Each module run counts as one operation on your plan.

Modules

What each VIESAC module does

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

VIESAC1

Create VAT audit

ActionIn the docs only

Starts a new VAT audit in your VIESAC account from data another module hands over, so the check begins without anyone typing it in.

When to use it
right after a new supplier or client is recorded somewhere else, as the first VIESAC step of the flow.
Watch out
Make lists no fields for it, so run it once and inspect what it expects before mapping.
VIESAC2

Download VAT certificate (PDF)

ActionIn the docs only

Gives you the certificate of an audit as a PDF file that people can open, print or attach to an email.

When to use it
when the proof ends up in a client folder, a shared drive or a message to a colleague rather than in software.
Watch out
on the Free plan Make handles files up to 5 MB, so check the size of a real certificate with Run once.
VIESAC3

Download VAT certificate (XML)

ActionIn the docs only

Returns the same certificate as structured XML, which another app can parse field by field instead of storing a picture of it.

When to use it
when the next step is an accounting or archiving tool that imports data rather than documents.
Watch out
pick the PDF module instead if a human is going to read the result; XML is meant for machines.
VIESAC4

Get VAT audit

ActionIn the docs only

Reads one audit you already know and brings its current details into the scenario, ready to map into the next module.

When to use it
when an earlier step stored the audit reference and you now want its result, for instance to update a client record.
Watch out
it needs one specific audit; to go through many at once, start from List VAT audits.
VIESAC5

Get account info

ActionIn the docs only

Returns the details of the VIESAC account behind your connection, which is the quickest way to confirm Make can talk to it.

When to use it
as a test after creating the connection, or at the start of a scenario that must stop when the account is unreachable.
Watch out
it tells you nothing about audits themselves, so it never replaces Get VAT audit.
VIESAC6

List VAT audits

SearchIn the docs only

Searches your account and returns the audits it finds, each one as its own bundle that the following modules handle in turn.

When to use it
to fill a spreadsheet with past checks or to download certificates for audits created before the scenario existed.
Watch out
a search can return zero, one or many audits, and every module after it runs once per audit, which adds operations.
VIESAC7

Make an API call

ActionIn the docs only

Sends your own request to the VIESAC API through the connection you already set up, so there is no second login to manage.

When to use it
when you need something the six other modules do not cover and the VIESAC API offers it.
Watch out
you write the request yourself, so check what VIESAC documents about its API and test the request with Run once before switching on.
Need help

Need help automating VIESAC with Make?

A person reads every message.

FAQ

VIESAC and Make: common questions

01Is the VIESAC Make integration free?
Yes, on the Make side. VIESAC is a standard app, so its modules are available from the Free plan. That plan gives you 2 active scenarios, a minimum of 15 minutes between scheduled runs, runs of 5 minutes at most, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and allow unlimited active scenarios. Usage is counted in operations each month. Your VIESAC subscription is a separate matter that Make does not cover.
02What do you need to connect VIESAC to Make?
A VIESAC account and a Make account. The Make documentation lists no prerequisite for this app. You add any VIESAC module, click Create a connection, optionally name it, then either authorize Make on the VIESAC page or paste the key VIESAC gives you, and click Save. The connection is then shared by all 7 modules. Running Get account info once is a simple way to confirm it works before you build further.
03Can a VIESAC Make integration start a scenario in real time?
No, not on its own. VIESAC has no trigger module in Make, so it cannot start a scenario when something happens in VIESAC. You have two options. Open the scenario with an instant trigger from another app, such as a form or a CRM, so VIESAC steps run as soon as that app calls Make. Or open it with a schedule, every 15 minutes by default, and let List VAT audits go through the audits already in your account.
04What if a VIESAC module you need is missing in Make?
Use Make an API call. It reaches any endpoint of the VIESAC API with the connection you already have, so you are not limited to the 6 other modules. Be aware that Make only offers limited documentation for VIESAC, with no field list and no troubleshooting section, so count on test runs with Run once, plus whatever API reference VIESAC gives you, to see exactly what each request sends back to your scenario.
05Should you use Make or n8n for VIESAC?
It depends on the tool you already use. In Make, VIESAC comes with 7 ready modules covering audits, certificates in PDF or XML and account details, plus a generic API call for the rest. The same app may also exist as an n8n node, so check what that platform offers before deciding. Base the choice on the modules you actually need and on where your other automations and your team already live today.
Same platform

Other docs you might need on this stack.

Browse all integrations