Integration recipes

Wire VAT Tools into n8n, Zapier, Make, WooCommerce, or HubSpot.

The API is deliberately plain HTTP, so any automation platform that can send headers and a JSON body can use it. These recipes cover the platforms VAT.tools ships scaffolds for, and the request and UX rules every integration must honour.

Planned feature availability

Signed webhooks

Application unavailable. Signed outbound webhooks are planned for a later release and cannot be configured in this release.

Scheduled monitoring

Application unavailable. Scheduled monitoring is planned for a later release and cannot be configured in this release.

Third-party schedule and webhook triggers do not make VAT Tools native webhook or monitoring workflows available.

Before you start

Create a developer key in the workspace under Integrations → Developer keys. Keys are organization-owned, scoped, and bound to one environment.
Use {{BASE_URL}} for the origin that serves your API deployment. Start in sandbox: deterministic, no live capacity, and the right environment for review artifacts.
Call the API server-side or from the platform's secret store. Never embed a key in a URL or a client-side bundle.

One request every platform can reproduce

curl --fail-with-body --silent --show-error \
  {{BASE_URL}}/api/v2/validations \
  -H 'Authorization: Bearer vat_REPLACE_WITH_A_SANDBOX_KEY' \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: workflow-run-0001' \
  --data '{"countryCode":"FR","vatNumber":"FR40303265045","mode":"sandbox"}'

n8n

Three recipes. The first two need no review for self-hosted use; the community node is the packaged version of the same calls.

Community node

Install n8n-nodes-vat-tools from Settings → Community nodes, then use the VAT Tools node: resource VAT → Validate VAT ID, or resource Company → Search, Resolve, Verify, Discover VAT.

HTTP Request workflow

Trigger (webhook, schedule, or an app node) → HTTP Request node with method POST, the endpoint URL, generic header auth carrying Authorization: Bearer …, and an Idempotency-Key built from the run's stable ID. Branch on the VAT state: continue on valid, and route source_unavailable or unsupported to a review branch — never to a hard failure.

MCP tool

Add the MCP Client Tool node, point it at the VAT.tools Streamable HTTP MCP endpoint with bearer auth, and select the five tools for use inside an AI Agent workflow.

Zapier

The private integration scaffold ships five actions, typed output fields for state, legal name, address, evidence source, and observation time, plus a polling trigger over the history endpoint.

Auth — API key: the user pastes the developer key, which must be obtainable without human intervention.
Actions — one per operation, with honest output fields rather than a single success boolean.
Trigger — no outbound webhooks yet; poll GET /api/v2/verifications newest-first with a cursor.
Rate limits — honour the reported ceiling rather than assuming a fixed value.

Make

The custom app scaffold ships a base URL and API-key connection, a universal module, and five action modules with outcome mapping. Use the HTTP module against the same endpoints, and branch a scenario on state: update the record on valid, notify finance for source_unavailable and unsupported.

Microsoft Power Platform

Import openapi-v2.json as a custom connector and configure API-key auth for the bearer header. It is usable in Power Automate, Power Apps, and Logic Apps without Microsoft certification. Keep the connector's operations aligned to the five write operations plus history, and do not expose key management through the connector.

Bulk reconciliation

For supplier lists and account reconciliation, use bulk jobs rather than loops: create the job with a CSV, start it, poll rows, and export CSV or JSONL for the finance system. Surface unsupported and source_unavailable as their own columns; never map them to invalid.

Integration UX rules

Every surface that renders a VAT.tools result must:

Show source_unavailable and unsupported as distinct, non-blocking states.
Block or flag only on an explicit invalid authority outcome, under a policy the customer configured.
Never present a valid VAT identifier as proof of the counterparty, tax treatment, or company status.
Keep the evidence source and observation time attached to the displayed outcome.

Ready-made scaffolds

Field	Type	Description
`n8n`	integrations/n8n-nodes-vat-tools	Community node with all five operations and two importable workflow templates.
`Zapier`	integrations/zapier-vat-tools	Private integration: five actions and a polling trigger, with offline tests.
`Make`	integrations/make-vat-tools	Custom app with a connection, universal module, and five action modules.
`WooCommerce`	integrations/woocommerce-vat-tools	Checkout VAT validation for classic and block checkout, with evidence on the order.
`HubSpot`	integrations/hubspot-vat-tools	Company-record app card backed by a serverless function.

Every scaffold follows the same rules: sandbox by default, live required for company resolution, and outcome states that never turn source_unavailable or unsupported into invalid.