Power Automate
Use Beliq from Power Automate, Power Apps, and Copilot Studio with the custom connector. Generate, validate, parse, and convert EN 16931 e-invoices.
Listing pending
A Microsoft Power Platform custom connector for Beliq. It works across Power Automate, Power Apps, and Copilot Studio, and is the Microsoft counterpart of the n8n node, built from the same product model.
- Source: github.com/beliq-eu/power-automate-beliq
- Definition: OpenAPI 2.0 (Swagger) at
Beliq/apiDefinition.swagger.json
Install (custom connector)
- Download
apiDefinition.swagger.jsonfrom the repo. - In make.powerautomate.com, open Data → Custom connectors → + New custom connector → Import an OpenAPI file.
- Select the downloaded file and create the connector.
Authentication
Create an API key in the Beliq dashboard under Integration → API Keys. Each connection collects only the API key; the connector’s policy adds the Authorization: Bearer header for you, so you paste the key without the Bearer prefix.
Actions
- Generate e-invoice →
POST /v1/generate(JSON body, returns XML or a hybrid PDF). - Validate e-invoice →
POST /v1/validate(raw XML/PDF body, returns JSON). - Parse e-invoice →
POST /v1/parse(raw XML/PDF body, returns JSON). - Convert e-invoice →
POST /v1/convert(raw XML/PDF body, returns the converted document). - Check API key →
GET /v1/me(no quota cost).
The Generate body models the core EN 16931 invoice (seller, buyer, lines, tax summary, payment means, totals) as typed fields, so flow authors get rich field mapping. Validate, Parse, and Convert take the document as the raw request body.
See also
- Quickstart: the underlying API in five minutes.
- Authentication: keys, quotas, and rate limits.
- API reference: the operations this connector calls.