n8n-nodes-billabex

n8n community node for the Billabex public API. Generic over
actions.json, adding an action to the manifest adds it to the node with no
code change. The node exposes 11 actions.

Usage in n8n

Here is an end-to-end example for listing an organization's accounts:

1. In Settings → Community Nodes, install n8n-nodes-billabex.
2. Create a workflow, add a Billabex node, then select List Accounts as the action.
3. In the node credentials, create or select a Billabex OAuth2 API credential. Enter its
   client ID and client secret, then authorize the connection to Billabex.
4. Enter your Billabex organization identifier in the required Organization ID field.
   First and After are optional pagination fields.
5. Click Execute step. The node returns one item containing the API JSON response, for
   example:

{
  "nodes": [
    {
      "id": "123e4567-e89b-12d3-a456-426614174000",
      "organizationId": "123e4567-e89b-12d3-a456-426614174001",
      "fullName": "Acme Corporation",
      "siren": null,
      "vatNumber": null,
      "currency": {
        "code": "EUR"
      },
      "billingAddress": {
        "street": "123 Main Street",
        "city": "Paris",
        "postalCode": "75001",
        "country": "FR",
        "stateOrProvince": null
      },
      "contacts": [],
      "hasValidEmailContact": false,
      "source": null
    }
  ],
  "pageInfo": {
    "endCursor": "eyJpZCI6IjEyM2U0NTY3LWU4OWItMTJkMy1hNDU2LTQyNjYxNDE3NDAwMCJ9"
  }
}

Use pageInfo.endCursor as After to retrieve the next page.

Setup

nvm use
npm ci
npm run lint
npm test

This is a standalone npm package (not an Nx project), no pnpm/workspace wiring.

Local testing in n8n

npm run dev

The official n8n CLI builds the package and starts a local n8n instance. Add a "Billabex" node,
create a "Billabex OAuth2 API" credential, and authorize.
The credential targets production at https://next.billabex.com by default. Set Base URL to
https://next.staging.billabex.com only when testing against staging.

OAuth client

n8n displays its redirect URI as
https://<instance>/rest/oauth2-credential/callback. Register that exact URI either from the
Billabex developer portal at /oauth-clients or with POST /api/oauth/register. Dynamic
registration needs this payload shape:

{
  "client_name": "n8n - Billabex",
  "redirect_uris": ["https://<instance>/rest/oauth2-credential/callback"],
  "grant_types": ["authorization_code", "refresh_token"],
  "scope": "<space-separated scopes from actions.json>",
  "token_endpoint_auth_method": "client_secret_post"
}

Enter the returned client_id and client_secret in the n8n credential. Keep PKCE enabled.

Publishing

Verified community nodes must be published from GitHub Actions with npm provenance. The
.github/workflows/publish.yml workflow publishes version tags, for example v0.1.0.

For the first publication, add a package-scoped npm granular token as the GitHub Actions secret
NPM_TOKEN. Once the package exists, configure npm Trusted Publishing for repository
billabex/n8n-nodes-billabex and its publication workflow, then remove the secret. Run
npx @n8n/scan-community-package n8n-nodes-billabex against the published version, then submit
the package through n8n's
Creator Portal.

Structure

• credentials/BillabexOAuth2Api.credentials.ts, extends n8n's generic oAuth2Api credential,
  hardcodes the scope list and PKCE requirement from actions.json.
• nodes/Billabex/Billabex.node.ts, one programmatic node; operation dropdown lists every
  action in actions.json, fields are generated from each action's pathParams/query/body.
  Dates use n8n's native picker. Address and source objects use explicit sub-fields, while
  country, currency and language use static options. File upload fields (create_invoice,
  create_credit_note) expect a binary property name from a prior node.
• npm run lint, npm run build, npm run dev, and npm run release use the official
  @n8n/node-cli. The package ships light and dark Billabex icons and can be used as an AI tool.