Integrations

Activepieces

Add Beliq to Activepieces flows with the community piece. Generate, validate, parse, and convert e-invoices.

Available

An Activepieces community piece for Beliq: one piece, four actions for building e-invoice steps in a self-hosted or cloud Activepieces flow.

Package: activepieces-beliq on npm
Source: github.com/beliq-eu/activepieces-beliq

Install

In Activepieces, go to Settings → My Pieces → Install Piece and enter the npm package name:

activepieces-beliq

For a self-hosted instance you can also upload a built tarball via Platform Admin → Setup → Pieces.

Connection

Create a beliq connection with an API key from the Beliq dashboard (Integration → API Keys). The connection test calls GET /v1/me, a no-quota credential check, so validating the connection never touches your monthly quota. Leave Base URL at the default unless you run a self-hosted deployment.

Actions

Generate Invoice: build a document (XML or PDF) from an EN 16931 invoice object, with the API’s verdict on its invoice XML.
Validate Invoice: check an XML or PDF invoice against the rule packs and schemas Beliq lists for its format and get a structured verdict. For a PDF, the verdict is about the embedded invoice XML; the PDF itself is not checked.
Parse Invoice: extract a structured EN 16931 invoice object from an XML or PDF document.
Convert Invoice: convert a document from one EN 16931 format to another.

Validate, Parse, and Convert read the document from either a pasted Text field (the invoice XML) or a File from a previous step; the Content Type auto-detects PDF versus XML from the bytes. Generate and Convert return the produced document as a File for the next step, alongside metadata (content type, size, Schematron version, PDF kind, source/target format, lost elements). Generate also returns sha256 of the document and the API’s verdict in validationResult. 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.

The verdict

Validate returns the API’s verdict as it came, and Generate returns it in validationResult. Generate’s verdict is on the invoice XML: the XML returned, or the XML embedded in a hybrid PDF; for a visualization PDF, the XML it was rendered from, which is not returned.

verified: whether a ruleset ran. With Validate Result off, Generate’s validationResult has verified: false: nothing was checked, and valid says nothing about the document.
valid: whether 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.
verificationBadgeLabel: the check depth the API states for this verdict. A verdict without it states none. How verification works explains each depth, and the rulesets catalog lists each format Beliq offers with its badge.
franceCtcBlockingRuleIds: the French CTC (Flux 2) rule ids the document trips, when that rule pack ran. It is a separate answer from valid and can come with valid: true (validate reference).

Every action has an Advanced (JSON) field that is deep-merged into the request, so any API option not surfaced as a control stays reachable.

Example flows

Importable templates live in the repo’s examples/ (import via Flows → Import Flow):

validate-xml-from-webhook.json: validate an XML invoice received on a webhook.
generate-xrechnung-scheduled.json: generate an XRechnung on a schedule.
convert-ubl-to-zugferd.json: convert a UBL invoice from a webhook into ZUGFeRD (EN 16931) CII XML.