Actions21
Overview
This node interacts with the Financial Cents API to manage contacts associated with clients. Specifically, the Contact - List operation retrieves a list of contacts for a specified client. It supports pagination and can return either a single page or all contacts by auto-paginating through the results.
Typical use cases include:
- Fetching all contacts related to a particular client for reporting or synchronization.
- Retrieving a subset of contacts with control over page size and number.
- Debugging API responses by optionally including raw JSON data.
For example, you might use this node to pull all contacts for a client before sending them an email campaign or updating their information in another system.
Properties
| Name | Meaning |
|---|---|
| Debug: Include Raw Response | If enabled, each returned item will include the full raw API JSON response under __raw. Useful for debugging. |
| Client | The parent client whose contacts you want to list. Select from available clients. |
| Page | The page number of results to fetch (minimum 1). |
| Per Page | Number of contacts per page to retrieve (between 1 and 200). |
| Return All | If true, the node will automatically paginate through all pages to return all contacts. |
| Limit | When "Return All" is enabled, limits the maximum number of contacts to return (0 means no limit). |
Output
The output is an array of JSON objects, each representing a contact belonging to the specified client. Each contact object contains fields as returned by the Financial Cents API, such as contact name, email, address, notes, and IDs.
If "Debug: Include Raw Response" is enabled, each item also includes a __raw field containing the full raw API response for that request, which can be useful for troubleshooting or accessing additional metadata not mapped directly.
No binary data is output by this node.
Dependencies
- Requires an API key credential for the Financial Cents API configured in n8n.
- The node makes authenticated HTTP requests to the Financial Cents API endpoints.
- Pagination parameters (
page,per_page) are used to control API queries. - The client list must be loaded beforehand to select the correct client ID.
Troubleshooting
- Missing Client ID: The "Client" property must be set to a valid client ID; otherwise, the API call will fail or return no contacts.
- Empty Results: If no contacts are returned, verify that the client actually has contacts in Financial Cents.
- API Rate Limits: Auto-pagination with "Return All" may hit API rate limits if many pages exist; consider using the "Limit" property to restrict results.
- Invalid Page or Per Page Values: Ensure "Page" is at least 1 and "Per Page" is between 1 and 200 to avoid API errors.
- Error on Delete or Update Operations: Although not relevant here, other operations require specific IDs; missing these will cause errors.
Common error messages typically relate to authentication failures, invalid client IDs, or exceeding API limits. Checking the raw response (__raw) can help diagnose issues.
Links and References
- Financial Cents API Documentation (general reference)
- n8n documentation on HTTP Request Authentication
- n8n community forums for Financial Cents integration tips and troubleshooting