Zapier

Connect Beliq to thousands of apps with the Zapier integration. Generate, validate, parse, and convert e-invoices in your Zaps.

Listing pending

A Zapier integration for Beliq. Wire e-invoice steps into a Zap and connect them to the thousands of apps Zapier already supports (Gmail, Drive, Slack, Stripe, and more).

• Source: github.com/beliq-eu/zapier-beliq

Create an API key in the Beliq dashboard under Integration → API Keys, then paste it into the API Key field when connecting. The connection test calls GET /v1/me, which returns your account context and consumes no quota.

• Generate Invoice: build an EN 16931 e-invoice from structured JSON, as XML or a PDF (a hybrid PDF/A-3 for Factur-X and ZUGFeRD).
• Validate Invoice: check a document against the rule packs and schemas Beliq lists for its format.
• Parse Invoice: extract structured fields from an invoice document.
• Convert Invoice: convert between EN 16931 formats (CII, UBL, XRechnung, ZUGFeRD, Factur-X, Peppol BIS Billing 3.0).

• Generate Invoice returns the XML text (for XML output) or a Zapier File plus metadata (for PDF output), with the Summary and Check Depth of the document’s verdict. With Verify off no ruleset runs: Summary says NOT VALIDATED, and valid then says nothing about the document. For a PDF, Summary also says which XML the verdict is about: the one embedded in a hybrid PDF, or, for a visualization PDF, the XML it was rendered from, which the step does not return.
• Validate Invoice returns every field of the API’s verdict as it came (valid, format, verificationBadgeLabel, the rule packs with their versions, errors, warnings, and the rest), plus Summary and Check Depth. Check Depth is verificationBadgeLabel as the API sent it, or check depth not stated when it sent none. Summary leads with the France CTC block when the answer has franceCtcBlockingRuleIds; the API reports such a block apart from valid, so a filter on Valid alone does not catch it. valid means the document passed the rule packs and schemas Beliq lists for its format, in the stated versions. It does not mean every recipient, validation tool or tax authority accepts it.
• Parse Invoice returns the structured invoice fields the parser read, and warnings naming what the document holds that the answer does not return. A field the parser read no value for is left out, not filled.
• Convert Invoice returns a Zapier File with the converted document, plus lostElementsCount and lostElements. An XML source sent to Factur-X or ZUGFeRD comes back as CII XML. A PDF comes back only when a hybrid PDF source is converted to Factur-X or ZUGFeRD: the PDF as sent when its embedded XML already is the target, otherwise that PDF re-wrapped around the converted XML. A PDF answer carries a PDF Note that says what the PDF is.

A returned File is ready to attach or upload in a downstream Gmail, Drive, or Slack step.

Validate, Parse, and Convert take a document either as pasted Document Text (the invoice XML) or as a Document File mapped from a previous step. Beliq detects CII versus UBL from the content, or you can set the format explicitly.

• Quickstart: the underlying API in five minutes.
• Authentication: keys, quotas, and rate limits.
• API reference: the operations this integration calls.