Invoice Ninja

Business appsAPI keyConnection test available

Read and write Invoice Ninja clients, invoices, payments, quotes, tasks and expenses, and run bulk invoice actions such as mark sent or email.

OCNORA ships 6 typed Invoice Ninja operations and 1 trigger. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run. Endpoints not covered by a typed node are called at https://invoicing.co/api/v1 through the HTTP node with the same credential.

Before you connect Invoice Ninja

Authentication
API key
Credential
the API token, or {"api_token", "api_secret"}the API token, or {"api_token": "…", "api_secret": "…"}
Connection test
Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
Prerequisites
  • The token must belong to an admin user on an account with the API feature — Invoice Ninja authorises webhook creation on isAdmin(), so a token that can read invoices can still fail to publish. A self-hosted install puts its own origin on the connection's base_url. Publishing also needs MANTLE_APP_PUBLIC_BASE_URL set to a URL the install can reach.

Prerequisites are taken from the connection notes in this provider’s node contracts; each node’s reference page says which apply to it.

What you can do with Invoice Ninja

Operations, grouped by what they do to your data, plus 1 trigger that start a run.

Create and send 1

Read and search 2

Update 1

Delete and cancel 1

Other operations 1

A sample Invoice Ninja workflow

  1. 1
    Eventtrigger.invoiceninja_event
    Start a run when Invoice Ninja emits an event (invoice, quote, payment, client, task, expense…).
  2. 2
    Get Recordinvoiceninja.get_record
    Fetch one client, invoice, payment, quote, task or expense by its id, optionally with its related records embedded.
  3. 3
    Create Recordinvoiceninja.create_record
    Create a client, invoice, payment, quote, task or expense from a JSON body, and return the record Invoice Ninja stored.

An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.

Invoice Ninja questions

How does OCNORA authenticate with Invoice Ninja?
With a stored API key credential, shaped the API token, or {"api_token", "api_secret"} or the API token, or {"api_token": "…", "api_secret": "…"}. A connection test can check it when you add it.
What can I automate with Invoice Ninja?
6 typed operations and 1 trigger, each with a reference page listing its config fields and the shapes it emits.
What if the Invoice Ninja operation I need is not listed?
Call https://invoicing.co/api/v1 from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
Are there templates that use Invoice Ninja?
Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
How are Invoice Ninja calls controlled?
Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.

See your first Invoice Ninja workflow run.

Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.