Update Record
invoiceninja.update_record
ActionBusiness appsconnection required
Calls the Invoice Ninja API with the connection's credentials.
Update a client, invoice, payment, quote, task or expense by id. Send every child record you want to keep: omitted contacts or line items are dropped, because Invoice Ninja treats an update as a whole-entity write.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Invoice Ninja
- Secret shape
- the API token, or {"api_token": "…", "api_secret": "…"}
- Config it needs
- base_url
- Resolved by
- config.connection_id, else node.connection_id
Configuration
3 fields, 3 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
resource Which Invoice Ninja entity to act on. | string | Yes | — | one of "clients", "invoices", "payments", "quotes", "tasks", "expenses" | — |
record_id The record's Invoice Ninja id, which is a hashed string and not a number. | string | Yes | — | — | Opnel5aKBz |
data The fields to write, as Invoice Ninja names them, including every child record that should survive the update. | object | Yes | — | ≥ 1 characters | {"name":"Acme Corporation"} |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"data": {
"name": "Acme Corporation"
},
"record_id": "Opnel5aKBz"
}Output
One shape.
result
The provider's response object, as returned.
Extra keys beyond the ones listed can appear.
{}Related Invoice Ninja nodes
See Update Record run in a workflow.
In a technical demo we add the Invoice Ninja connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.