VAT Validation with Zapier

Zapier does not have a native VAT validation app. You can connect Vatly to any Zapier workflow using the Webhooks by Zapier action, which calls any REST API with custom headers. No code required.

This guide walks through setting up a Zap that validates a VAT number and uses the result in downstream steps.

When to use this

Zapier is a good fit when you want to validate VAT numbers as part of an existing automation, without writing code. Common use cases:

• Validate a VAT number when a new HubSpot contact or company is created
• Validate when a Typeform, JotForm, or Google Forms submission includes a VAT number
• Validate when a new row appears in a Google Sheet (e.g., a partner onboarding spreadsheet)
• Validate when a new Salesforce Account is created (if you prefer no-code over Apex)

Setting up the Zap

The Zap has two parts: a trigger (the event that starts it) and an action (the Vatly API call). You then add more steps to use the result.

1. Choose your trigger

Pick the event that should start the validation. For example, "New Contact" in HubSpot, "New Response" in Typeform, or "New Spreadsheet Row" in Google Sheets. The trigger must provide a field that contains the VAT number.

2. Add the Webhooks by Zapier action

Add a new action step. Search for "Webhooks by Zapier" and select "Custom Request" as the action event. This gives you full control over the HTTP request.

• Method: GET
• URL: https://api.vatly.dev/v1/validate?vat_number={{vat_number_field}} (map the VAT number field from your trigger)
• Headers: add a header with key Authorization and value Bearer vtly_live_your_api_key

When you test the step, Zapier sends the request and displays the parsed JSON response. Each field in the response (like data__valid and data__company__name) becomes available as a variable in subsequent steps.

Using the result

After the webhook step, you can use the validation result in downstream actions:

• Update a CRM record: add a HubSpot or Salesforce update step that writes the validated company name (data__company__name) back to the contact or account record.
• Filter the Zap: add a Filter step that continues only if data__valid is true. This lets you skip downstream steps for invalid numbers.
• Send a notification: if the number is invalid, send a Slack message or email to the responsible sales rep so they can follow up.

Limitations

Zapier processes Zaps one at a time and is designed for event-driven automation, not bulk data processing. If you need to validate thousands of existing VAT numbers in your CRM, the Vatly batch endpoint is a better fit. It accepts up to 50 numbers per request on Pro and Business plans.

The Webhooks by Zapier action is available on Zapier's paid plans. It is not included in the free tier.

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.