Actions10
Overview
The node integrates with the Cryptomus API to manage cryptocurrency payments and related operations. It supports various payment-related actions such as creating payments, retrieving payment history, checking balances, refunding payments, and testing webhooks.
Specifically, the Get Payment History operation fetches a list of past payments filtered by parameters like date range, status, order ID, pagination size, and page number. This is useful for businesses or services that need to track and analyze their cryptocurrency payment transactions over time.
Practical examples:
- Retrieve all confirmed payments made in the last month to reconcile accounts.
- Fetch pending payments to follow up on incomplete transactions.
- Paginate through large payment histories for reporting or auditing purposes.
Properties
| Name | Meaning |
|---|---|
| Date From | Filter payments starting from this date (format: YYYY-MM-DD). |
| Date To | Filter payments up to this date (format: YYYY-MM-DD). |
| Filter by Status | Filter payments by their status. Options: Confirmed, Error, Expired, Payment Received, Pending Payment. |
| Items per Page | Number of payment records to return per page (pagination size). |
| Order ID | Filter payments by a specific order identifier. |
| Page Number | The page number of results to retrieve (for pagination). |
| Test Payment | Boolean flag indicating whether to include test payments. |
Output
The output is an array of JSON objects representing the response from the Cryptomus API for the payment history request. Each object contains details about payments matching the specified filters, including metadata such as amount, currency, status, order ID, timestamps, and other payment-specific information.
If the API returns binary data (not typical for this operation), it would represent raw payment-related files or documents, but this operation primarily outputs structured JSON data.
Dependencies
- Requires an API key credential configured with access to the Cryptomus Payment API.
- The node uses HTTP requests to communicate with the Cryptomus API endpoints.
- No additional external dependencies beyond the Cryptomus API and n8n's HTTP request helper.
Troubleshooting
- Invalid Credentials Error: If the provided API credentials are not of the required "Payment" type, the node will throw an error indicating the mismatch. Ensure you use credentials authorized for payment operations.
- API Request Failures: Network issues or incorrect parameter formats (e.g., invalid dates) may cause API errors. Verify parameter correctness and network connectivity.
- Empty Results: If no payments match the filters, the returned JSON array may be empty. Adjust filters or check if payments exist for the given criteria.
- Pagination Issues: Requesting pages beyond available data will result in empty responses. Use the total count from previous responses to guide pagination.
Links and References
- Cryptomus API Documentation — Official API docs for detailed endpoint descriptions and parameters.
- n8n HTTP Request Node Documentation — For understanding how HTTP requests are handled within n8n nodes.