Skip to content
← Back to documentation
Technical Reference

Invoice Ninja

Free open-source invoicing tool

CategoryAccounting
Authenticationcustom
Version0.4.0
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Invoice Ninja with Flows360

Free open-source invoicing tool

Use the Invoice Ninja connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 10 actions and no declared triggers.

Available actions

  • Create Task
  • Check Task Existence
  • Get Client Details from e-mail
  • Get Invoices
  • Get Report
  • Create Invoice
  • Create Client
  • Create Recurring Invoice
  • Plus 2 additional declared actions.

Available triggers

  • No triggers are declared in this pinned package.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Invoice Ninja
  • Package: @activepieces/piece-invoiceninja@0.4.0
  • Exact artifact digest: sha256:5f60e6ad269b03e0139f01c1f9a7e8a0b5cfb0f5797414b058b761e709ce746b
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Task (create_task), Creates a task instance in Invoice Ninja for billing purposes. Classification: read.
  • Check Task Existence (exists_task), Verify if a Task Already Exists Classification: read.
  • Get Client Details from e-mail (getclient_task), Gets the client details if they exist by e-mail. Classification: read.
  • Get Invoices (getinvoices_task), Gets data for invoices. Classification: read.
  • Get Report (getreport_task), Gets report data from InvoiceNinja. Classification: read.
  • Create Invoice (create_invoice), Creates an invoice in Invoice Ninja for billing purposes. Classification: read.
  • Create Client (create_client), Creates a new client in InvoiceNinja. Classification: read.
  • Create Recurring Invoice (create_recurring_invoice), Creates a recurring invoice in Invoice Ninja for billing purposes. Classification: read.
  • Perform Action on Recurring Invoice (action_recurring_invoice), Actions include: start, stop, send_now, restore, archive, delete. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • No trigger delivery contracts are declared.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects10
Supported actionsNot published
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Base URL Required
  • API Token Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Task Yes No Creates a task instance in Invoice Ninja for billing purposes.
Check Task Existence Yes No Verify if a Task Already Exists
Get Client Details from e-mail Yes No Gets the client details if they exist by e-mail.
Get Invoices Yes No Gets data for invoices.
Get Report Yes No Gets report data from InvoiceNinja.
Create Invoice Yes No Creates an invoice in Invoice Ninja for billing purposes.
Create Client Yes No Creates a new client in InvoiceNinja.
Create Recurring Invoice Yes No Creates a recurring invoice in Invoice Ninja for billing purposes.
Perform Action on Recurring Invoice Yes No Actions include: start, stop, send_now, restore, archive, delete.
Custom API Call Yes No Make a custom API call to a specific endpoint

Setup

Setup

  1. Add the Invoice Ninja connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • Base URL (base_url), required.
  • API Token (access_token), required; stored as a sensitive connection value.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-invoiceninja@0.4.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 10 actions and 0 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Invoice Ninja connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-invoiceninja@0.4.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.