Actions21
Overview
This node operation updates an existing client record in the Financial Cents system via its API. It allows users to modify the client's display name and additional contact-related fields such as contact name, email, address, and notes.
Typical use cases include:
- Correcting or updating client information after initial creation.
- Adding or changing contact details associated with a client.
- Automating client data maintenance workflows within n8n.
For example, you might use this node to update a client's display name and contact email after receiving new information from your sales team.
Properties
| Name | Meaning |
|---|---|
| Debug: Include Raw Response | If enabled, the raw JSON response from the API will be included under the __raw property in each output item. |
| Client | Select the client to update by choosing from a list or using an expression for the client ID. |
| Display Name | The new display name for the client. If left empty, the current client name is retained (required by API for update). |
| Additional Fields | Optional collection of additional contact-related fields to update: |
| - Contact Name: Name of the contact person. | |
| - Contact Email: Email address of the contact person. | |
| - Contact Address: Physical address of the contact. | |
| - Contact Notes: Any notes related to the contact. |
Output
The node outputs JSON objects representing the updated client data returned by the Financial Cents API. Each output item corresponds to one updated client record.
If "Debug: Include Raw Response" is enabled, the raw full API response JSON is also included under the __raw key in each output item.
No binary data is produced by this operation.
Dependencies
- Requires an API key credential configured in n8n to authenticate with the Financial Cents API.
- The node uses the Financial Cents REST API endpoint for clients (
/clients/{clientId}) with HTTP PUT method to perform updates.
Troubleshooting
- Missing Client ID: Ensure that the "Client" property is set correctly; otherwise, the API call will fail because it needs a valid client identifier.
- Empty Display Name: If the "Display Name" field is left empty, the node fetches the current client name before updating. If the client does not exist or cannot be fetched, the update may fail.
- API Errors: Common API errors like authentication failures or invalid data will be returned by the API. Check that the API key credential is valid and that all required fields meet the API's validation rules.
- Network Issues: Connectivity problems can cause request failures. Verify network access to the Financial Cents API endpoint.
Links and References
- Financial Cents API Documentation (general reference for API endpoints and data formats)
- n8n documentation on HTTP Request Node for understanding underlying HTTP calls (conceptual)