VAT Validation with Make

Make (formerly Integromat) does not have a native VAT validation module. You can call Vatly from any Make scenario using the HTTP module, which supports custom headers and JSON response parsing. No code required.

This guide walks through setting up a Make scenario that validates a VAT number and routes the result to different actions.

When to use this

Make is a good fit when you want to validate VAT numbers as part of a multi-step automation. Common use cases:

  • Validate a VAT number when a new CRM record is created (HubSpot, Salesforce, Pipedrive)
  • Validate when a form submission comes in (Typeform, Google Forms, Tally)
  • Validate as part of a customer or partner onboarding scenario
  • Periodic revalidation of existing records using a scheduled scenario

Setting up the HTTP module

Add an HTTP module to your scenario and configure it to call the Vatly API.

1. Add the module

In your scenario, add a new module. Search for "HTTP" and select "Make a request" as the action.

2. Configure the request

  • URL: https://api.vatly.dev/v1/validate?vat_number={{vat_number}} (map the VAT number from a previous module)
  • Method: GET
  • Headers: add a header with name Authorization and value Bearer vtly_live_your_api_key
  • Parse response: set to Yes so Make exposes the JSON response fields as variables in subsequent modules

3. Test the module

Run the module once with a real or test VAT number. Make will display the parsed response. You should see data.valid, data.company.name, and data.country_code as available fields.

Using the result

After the HTTP module, use a Router to branch the scenario based on the validation result.

  • Valid branch: add a filter that checks data.valid equals true. In this branch, update the CRM record with the registered company name from data.company.name.
  • Invalid branch: add a filter that checks data.valid equals false. Send a notification (Slack, email, or a task in your project management tool) so someone can follow up.

You can also skip the Router and use a single Filter module if you only need to act on one outcome (e.g., only notify on invalid numbers).

Limitations

Make scenarios are designed for event-driven and scheduled automation. While Make supports iterators and aggregators for processing multiple items within a scenario, it is not the most efficient tool for validating very large backlogs. For bulk validation of thousands of records, the Vatly batch endpoint accepts up to 50 numbers per request and the async endpoint handles even larger volumes via webhooks.

Get started

Create a free Vatly account →

Read the API documentation for the full endpoint reference. For a broader overview of CRM integration patterns, see the CRM validation guide.

Frequently asked questions

Does Make have a native VAT validation module?

No. You call Vatly from Make using the HTTP module, which supports custom headers and JSON response parsing.

How do I route a Make scenario based on whether a VAT number is valid?

After the HTTP module, add a Router or Filter module that checks the value of the data.valid field in the parsed response. Route valid numbers to one path and invalid numbers to another.

Is Make suitable for validating large numbers of VAT records?

Make supports iterators and aggregators for batch-style processing within a scenario, which gives it more flexibility than Zapier for larger volumes. For very large backlogs, the Vatly batch endpoint is more efficient.