Actions11
Overview
The node integrates with the CoreSense platform to perform various operations on different resources. Specifically, for the Contact resource with the Search operation, it allows users to search for contacts within CoreSense based on optional criteria such as Contact ID and ordering preferences. This is useful in scenarios where you need to retrieve contact information programmatically, for example, syncing contacts from CoreSense into another system, filtering contacts for marketing campaigns, or verifying contact details before processing orders.
Properties
| Name | Meaning |
|---|---|
| Contact ID | (Optional) Specify a particular contact's ID to search for. Can also use expressions to dynamically set this value. |
| Order By | (Optional) Choose how to order the search results. Options include: Active, Customer ID, Email, First Name, ID, Last Name, Phone, Postal Code, State ID. |
| Return All | Whether to return all matching contacts or limit the number of results. |
| Limit | Maximum number of contacts to return if "Return All" is false. Minimum value is 1, default is 50. |
Output
The node outputs JSON data representing the contacts found by the search query. Each item in the output corresponds to a contact record retrieved from CoreSense, containing fields such as contact ID, name, email, phone, and other relevant contact details depending on CoreSense's API response structure.
If binary data were involved (e.g., contact images), it would be included in the binary output field, but this operation focuses on JSON data only.
Dependencies
- Requires an active connection to the CoreSense API via an API key credential configured in n8n.
- The node depends on CoreSense's REST API endpoints for searching contacts.
- Proper network access and authentication credentials must be set up in n8n for successful API communication.
Troubleshooting
- No results returned: Verify that the Contact ID or search parameters are correct and that the CoreSense account contains matching contacts.
- Authentication errors: Ensure the API key credential is valid and has sufficient permissions.
- Limit ignored or too many results: If "Return All" is false but more results are expected, check the "Limit" property and increase it if necessary.
- API rate limits: If requests fail due to rate limiting, consider adding delays or reducing request frequency.
- Invalid property values: Make sure numeric fields like Contact ID and Limit are numbers and within allowed ranges.
Links and References
- CoreSense API Documentation (example placeholder link)
- n8n Expressions Documentation
- n8n Node Development Guide