Actions68
- Client Actions
- Agent Actions
- Asset Actions
- Field Info Actions
- Invoice Actions
- Site Actions
- Ticket Actions
- Ticket Status Actions
- Ticket Type Actions
- Timesheet Actions
- Timesheet Event Actions
- Webhook Actions
- Webhook Event Actions
Overview
This node integrates with the HaloPSA API to update existing invoices. It allows users to modify various invoice details such as client association, due date, invoice date, notes, posting status, reference, and site number. This is useful in scenarios where invoice information needs correction or updating after creation, for example, changing the payment due date, adding additional notes, or marking an invoice as posted.
Practical examples:
- Updating the due date of an invoice when a payment extension is granted.
- Adding internal notes to an invoice for record-keeping.
- Changing the client associated with an invoice if it was assigned incorrectly.
Properties
| Name | Meaning |
|---|---|
| Invoice ID | The unique numeric identifier of the invoice to update. |
| Update Fields | A collection of fields to update on the invoice. Options include: |
| - Client ID | Numeric ID of the client associated with the invoice. |
| - Due Date | The new due date for the invoice payment (date-time format). |
| - Invoice Date | The date the invoice was issued (date-time format). |
| - Notes 1 | Additional textual notes related to the invoice. |
| - Posted | Boolean flag indicating whether the invoice has been posted. |
| - Reference | A string reference identifier for the invoice. |
| - Site Number | Numeric identifier for the site related to the invoice. |
Output
The node outputs JSON data representing the updated invoice object returned by the HaloPSA API. This typically includes all invoice fields reflecting the changes made. There is no indication that binary data is output by this node.
Dependencies
- Requires an active connection to the HaloPSA API.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The node relies on the external HaloPSA service being available and responsive.
Troubleshooting
Common issues:
- Invalid or missing Invoice ID will cause the update to fail.
- Providing invalid field values (e.g., wrong date format) may result in API errors.
- Network or authentication failures can prevent successful updates.
Error messages and resolutions:
- "Invoice not found" — Verify the Invoice ID exists in HaloPSA.
- "Unauthorized" — Check that the API credentials are correctly set up and valid.
- "Invalid input" — Ensure all update fields conform to expected types and formats.
- Timeouts or network errors — Confirm network connectivity and HaloPSA service status.
Links and References
- HaloPSA API Documentation (for detailed API endpoints and data models)
- n8n documentation on creating custom nodes