Actions10
Overview
The node integrates with the Cryptomus API to manage cryptocurrency payments and related operations. It supports creating payments, retrieving payment details and history, refunding payments (including blocked funds), resending webhooks for payments, testing webhook delivery, checking balances, and listing supported currencies.
The Resend Webhook operation specifically allows users to trigger a resend of the webhook notification for a particular payment. This is useful if the original webhook notification was missed or failed to be processed by the receiving system. For example, if your system did not receive a payment confirmation due to network issues, you can use this operation to request Cryptomus to resend the webhook and ensure your system stays synchronized.
Properties
| Name | Meaning |
|---|---|
| Identifier Type | The type of identifier used to find the payment. Options: Payment UUID, Order ID. |
| Payment ID | The actual identifier value of the payment, corresponding to the selected Identifier Type. |
| Test Payment | Boolean flag indicating whether the payment is for testing purposes (true or false). |
Output
The output is a JSON object containing the response from the Cryptomus API for the resend webhook request. Typically, this will include status information about the webhook resend action, such as success confirmation or error details.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential configured in n8n with access to the Cryptomus Payment API.
- The node uses HTTP requests to communicate with the Cryptomus API endpoints.
- No additional external dependencies are required beyond the configured API credentials.
Troubleshooting
- Invalid Credentials Error: If the provided API credentials do not have the correct API type (must be "Payment"), the node will throw an error indicating the mismatch. Ensure that the API key used is authorized for payment operations.
- Payment Not Found: If the payment identifier does not match any existing payment, the API may return an error. Verify that the correct identifier type and value are used.
- Webhook Resend Failure: Network issues or invalid webhook URLs on the receiver side might cause webhook resend failures. Check the webhook endpoint's availability and correctness.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if one fails, returning the error message in the output JSON.
Links and References
- Cryptomus API Documentation — Official API docs for detailed endpoint descriptions and parameters.
- n8n Documentation — General guidance on using credentials and HTTP request nodes.