Actions11
Overview
The node integrates with the CoreSense platform to perform various operations on different resources. Specifically, for the Customer resource with the Search operation, it allows users to search for customers in the CoreSense system based on optional criteria such as Customer ID and ordering preferences. This is useful in scenarios where you want to retrieve customer data programmatically, for example, to sync customer information, generate reports, or trigger workflows based on customer attributes.
Practical examples:
- Retrieve a list of customers ordered by their Client ID.
- Search for a specific customer by their Customer ID.
- Fetch all customers without limiting the number of results.
Properties
| Name | Meaning |
|---|---|
| Customer ID | (Optional) Specify a numeric ID to search for a particular customer. Can also use expressions. |
| Order By | (Optional) Choose how to order the search results. Options: Billing Contact ID, Client (Customer) ID, Originating Brand ID, Shipping Contact ID. |
| Return All | Whether to return all matching results or limit the output to a specified number. |
| Limit | Maximum number of results to return when "Return All" is false. Minimum value is 1. |
Output
The node outputs JSON data representing the customers found by the search query. The structure typically includes an array of customer objects with their associated fields as provided by the CoreSense API. If binary data were involved, it would be summarized here, but this operation deals only with JSON customer data.
Dependencies
- Requires an active connection to the CoreSense API via an API key credential configured in n8n.
- The node depends on internal routing and action modules to handle requests to CoreSense.
- No additional external dependencies are indicated beyond the CoreSense API access.
Troubleshooting
- Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing an invalid Customer ID or unsupported order option may result in empty results or errors.
- Exceeding API rate limits could cause request failures.
- Error messages:
- Authentication errors indicate problems with the API key setup; verify credentials.
- Validation errors on input properties suggest incorrect types or values; ensure Customer ID is numeric and options are valid.
- Network or timeout errors require checking connectivity to the CoreSense service.
Links and References
- CoreSense API Documentation (hypothetical link)
- n8n Expressions Documentation – for using expressions in input fields.