Actions11
Overview
The node integrates with the CoreSense system to perform various operations on different resources. Specifically, for the Payment resource and the Search operation, it allows users to query payment records based on optional filters such as Payment ID, and control the ordering and number of results returned.
This node is beneficial in scenarios where you need to retrieve payment data from CoreSense for reporting, reconciliation, or further processing within an n8n workflow. For example, you might want to fetch all payments related to a specific order or within a certain date range, then use that data to update another system or generate invoices.
Properties
| Name | Meaning |
|---|---|
| Payment ID | (Optional) Filter by a specific payment ID. Can also be set dynamically using expressions. |
| Order By | (Optional) Choose how to order the search results. Options: Assoc Entity, Assoc Entity ID, ID, POS ID, Receivable Type ID, Stamp, Void. |
| 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, default 50. |
Output
The node outputs JSON data representing the payment records retrieved from CoreSense according to the search criteria. Each item in the output corresponds to a payment entry with its associated fields as provided by the CoreSense API.
There is no indication that this node outputs binary data; the focus is on structured JSON payment information.
Dependencies
- Requires an active connection to CoreSense via an API key credential configured in n8n.
- The node depends on CoreSense's API being accessible and properly authenticated.
- No additional external dependencies are indicated beyond the CoreSense API integration.
Troubleshooting
Common Issues:
- Authentication failures due to missing or invalid API credentials.
- Network connectivity problems preventing access to CoreSense API.
- Invalid input parameters causing the API to reject the request.
Error Messages:
- Errors related to authentication typically indicate misconfigured or expired API keys; verify and update credentials.
- Rate limiting or quota exceeded errors suggest too many requests; consider adding delays or reducing frequency.
- Validation errors on input properties (e.g., invalid Payment ID format) require correcting the input values.
Links and References
- CoreSense API Documentation (hypothetical link for reference)
- n8n Expressions Documentation – for dynamic property values
Note: This summary is based solely on static analysis of the provided source code and property definitions without runtime execution or internal credential details.