CI/CD integration

Two ways to run FactureCheck as part of a pipeline instead of one file at a time by hand. Both call the same public POST /api/v1/validate endpoint — nothing new to trust, and neither one repairs or mutates the files it checks.

GitHub Action

A composite (no Docker) action that validates every file matching a glob, writes a Markdown summary to the job, and fails the build on the verdict. Not yet published to the GitHub Marketplace — use it today via a local path reference, or by copying action.yml and validate.sh into your own repository's .github/actions/facturecheck/.

- uses: ./integrations/github-action
  with:
    files: 'invoices/*.xml'
    api_key: ${{ secrets.FACTURECHECK_API_KEY }}
    fail_on: error

Inputs: files, api_key (pass as a repository secret, never hardcode it), api_url, fail_on (error or warning). Output: verdict (acceptable or rejected).

n8n node

n8n-nodes-facturecheck adds a FactureCheck node with three operations — Validate (POST /api/v1/validate), Repair (POST /api/v1/repair), and Batch (POST /api/v1/validate/batch) — reading the invoice from a binary input property and returning the API's JSON as the item's output. Not yet published to the n8n community node registry — build it locally (npm ci && npm run build) until it is. A dedicated FactureCheck API credential holds the API key; it is never placed in a node parameter.

Need this from inside an agent conversation instead of a pipeline step? See the MCP server.

Validate your invoice free