Invoice Ninja MCP integration for AI agents.
Connect AI agents to Invoice Ninja through 11 structured actions, including get client, create client, and create invoice. Review authentication, inputs, wor…
- ACTION CONTRACTS
- 11
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Invoice Ninja integration exposes
The Invoice Ninja Agent App exposes 11 provider-backed actions for finance and productivity work. Its current contract lets an authorized agent retrieve one invoice ninja client by hashed id, create an invoice ninja client, and create an invoice ninja invoice for a client. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Invoice Ninja account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Invoice Ninja capabilities.
Showing 11 of 11 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_clientREADRetrieve one Invoice Ninja client by hashed ID.
INPUTS: clientId / include
create_clientWRITECreate an Invoice Ninja client.
INPUTS: name / contacts / website / phone / privateNotes
create_invoiceWRITECreate an Invoice Ninja invoice for a client.
INPUTS: clientId / lineItems / date / dueDate / number
create_paymentWRITERecord a payment in Invoice Ninja and optionally apply it to invoices.
INPUTS: clientId / amount / paymentTypeId / date / transactionReference
get_invoiceREADRetrieve one Invoice Ninja invoice by hashed ID.
INPUTS: invoiceId / include
get_paymentREADRetrieve one Invoice Ninja payment by hashed ID.
INPUTS: paymentId / include
list_clientsREADList Invoice Ninja clients with optional search and pagination filters.
INPUTS: page / perPage / include / filter / sort
list_invoicesREADList Invoice Ninja invoices with optional client, status, date, and search filters.
INPUTS: page / perPage / include / filter / sort
list_paymentsREADList Invoice Ninja payments with optional client and search filters.
INPUTS: page / perPage / include / filter / sort
update_clientWRITEUpdate an Invoice Ninja client while replacing its complete contact list.
INPUTS: clientId / name / contacts / website / phone
update_invoiceWRITEUpdate documented fields or status actions on an Invoice Ninja invoice.
INPUTS: invoiceId / clientId / lineItems / date / dueDate
INPUT CONTRACTS
Know what the action needs before it runs.
get_client
clientIdREQUIRED- The Invoice Ninja hashed resource ID.
includeOPTIONAL- Comma-separated related resources to include in the response.
create_client
nameOPTIONAL- The client company or organization name.
contactsOPTIONAL- The complete client contact list.
websiteOPTIONAL- The client website URL.
phoneOPTIONAL- The client phone number.
privateNotesOPTIONAL- Notes visible only to Invoice Ninja users.
create_invoice
clientIdREQUIRED- The Invoice Ninja hashed resource ID.
lineItemsOPTIONAL- The invoice line items.
dateOPTIONAL- The invoice date.
dueDateOPTIONAL- The invoice due date.
numberOPTIONAL- A custom invoice number.
create_payment
clientIdREQUIRED- The Invoice Ninja hashed resource ID.
amountOPTIONAL- The total payment amount.
paymentTypeIdOPTIONAL- The Invoice Ninja payment type ID from 1 through 33.
dateOPTIONAL- The payment date.
transactionReferenceOPTIONAL- The payment gateway or bank transaction reference.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Client
Retrieve one Invoice Ninja client by hashed ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_clientControl Create Client
Create an Invoice Ninja client. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_clientVerify with Get Invoice
Retrieve one Invoice Ninja invoice by hashed ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_invoiceSAFETY BOUNDARY
Operate Invoice Ninja with explicit limits
- Authorize Invoice Ninja with API key and grant only the provider access required by the selected actions.
- 5 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Invoice Ninja rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Invoice Ninja task completed successfully.
CONNECTION MODEL
API key
Invoice Ninja uses API key. Connection requirements and availability are determined by the provider and the Working Machines deployment.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 6
- WRITE SIGNALS
- 5
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Invoice Ninja.