Developer Platform: MCP server availableDeveloper Platform: MCP server available, App SDK from Q4 2026

[ Accounting ]

Invoice Ninja integration for your workflows.

Connect Invoice Ninja to Collabase once and use 10 actions in your workflows. No code needed, hosted in Switzerland.

Sign-inCustom credentials
CategoryAccounting
UpdatedOctober 2026
LicenceOpen source (MIT)
Back to the directory

Invoice Ninja in Collabase

Connect Invoice Ninja to Collabase once and use 10 actions in your workflows. No code needed, hosted in Switzerland.

[ About the service ]

Free open-source invoicing tool

How to connect it

  1. Open the integrations in the workspace settings.
  2. Choose Invoice Ninja and connect your account.
  3. Add a trigger or an action to the workflow.
  • Log in to Invoice Ninja (https://invoicing.co or your self-hosted server).
  • Open Settings > Account Management > API Tokens and create a token.
  • Paste the token below. Base URL is https://invoicing.co for the hosted service, or the address of your own server (for example https://invoices.example.com).

[ Accounting ]

Related integrations

All integrations

Tools that often share a workflow.

Questions about Invoice Ninja

What can I automate with Invoice Ninja in Collabase?

Invoice Ninja brings 10 actions and 0 triggers, for example Create Task, Check Task Existence, Get Client Details from e-mail, Get Invoices and 6 more. You combine them in a workflow without code and mix them with every other integration.

How do I connect Invoice Ninja to Collabase?

You open the integrations in the workspace settings, choose Invoice Ninja and connect your account once, using custom credentials. After that all triggers and actions are available in the workflow.

Does the Invoice Ninja integration cost extra?

No. All integrations are included in every licence, in the Isolated Cloud and in Self-Hosted operation. There is no module price.

Test it against your own content. A proof of concept is ready within days.

We set up an instance with your content and you test it against real workflows. In a first conversation we clarify scope, operating model and timing.