Actions10
Overview
The node provides integration with the Cryptomus API to manage cryptocurrency payments and related operations. It supports various payment-related actions such as creating payments, retrieving payment information, refunding payments, testing webhooks, and more.
The Test Webhook operation specifically allows users to send a test webhook notification to a specified URL with a chosen event status. This is useful for verifying that your system correctly receives and processes webhook events from Cryptomus without needing an actual payment event to occur.
Common scenarios:
- Testing webhook endpoints during development or integration setup.
- Simulating different payment statuses (e.g., confirmed, error, expired) to verify handling logic.
- Ensuring that webhook URLs are reachable and respond correctly before going live.
Example:
You want to confirm that your webhook listener correctly handles a "Payment Received" event. Using this node's Test Webhook operation, you specify your webhook URL and select the "Payment Received" status. The node sends a simulated webhook payload to your endpoint, allowing you to validate your processing logic.
Properties
| Name | Meaning |
|---|---|
| Webhook URL | The URL where the test webhook will be sent. |
| Event Type | The status of the test webhook event to simulate. Options: Confirmed, Error, Expired, Payment Received, Pending Payment. |
| Test Payment | Boolean flag indicating whether the payment is for testing purposes (true/false). |
Output
The node outputs a JSON object representing the response from the Cryptomus API after sending the test webhook request. This typically includes confirmation details about the webhook dispatch or any error messages returned by the API.
No binary data output is involved in this operation.
Dependencies
- Requires valid Cryptomus API credentials with permission for payment operations.
- Needs network access to the specified webhook URL to successfully deliver the test webhook.
- Uses HTTP POST requests to communicate with the Cryptomus API endpoints.
Troubleshooting
- Invalid Credentials Error: If the provided API credentials do not have the required "Payment" API type, the node throws an error indicating the mismatch. Ensure you use credentials configured for payment operations.
- Webhook Delivery Failures: If the webhook URL is unreachable or returns errors, the test webhook may fail. Verify the URL is correct, publicly accessible, and able to accept POST requests.
- API Errors: Any errors returned by the Cryptomus API during the test webhook call will be surfaced. Check the error message for details and ensure all parameters are valid.
- Continue on Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output JSON.
Links and References
- Cryptomus API Documentation — Official API docs for detailed endpoint descriptions.
- Webhook Integration Guide — How to set up and handle Cryptomus webhooks effectively.