Actions6
Overview
This node integrates with the Cryptomus Payout API to manage cryptocurrency withdrawals and related operations. It supports creating new payouts, retrieving payout history and information, listing available payout services, and transferring funds between personal and business wallets.
A common use case is automating crypto withdrawal workflows in financial or trading platforms, where users need to programmatically initiate payouts or check their status. For example, a business could automatically pay out earnings to users' crypto wallets or reconcile payout histories for accounting.
The "Get Payout Services" operation specifically fetches a list of available payout services supported by the Cryptomus platform, which helps users understand which payment systems they can use for withdrawals.
Properties
| Name | Meaning |
|---|---|
| Платежная система | The payment system to query payout services for. Options: Binance, BinanceP2p, Exmo, Kucoin |
(Note: This property corresponds to the user-provided input properties for the "Get Payout Services" operation.)
Output
The node outputs an array of JSON objects, each representing the response from the Cryptomus API for the requested operation.
For the "Get Payout Services" operation, the output JSON contains the list of payout services available through the Cryptomus API. The exact structure depends on the API response but typically includes service names, identifiers, and possibly supported currencies or networks.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for the Cryptomus API configured in n8n.
- The node uses HTTP requests to communicate with the Cryptomus Payout API endpoints.
- No additional external dependencies beyond the Cryptomus API and its authentication are needed.
Troubleshooting
- API Type Mismatch: If the configured API credential is not set for the "Payout" type, the node throws an error indicating that only payout-type API credentials are allowed.
- HTTP Request Failures: Network issues or invalid parameters may cause HTTP request errors. The node will throw these errors unless "Continue On Fail" is enabled, in which case it returns the error message in the output JSON.
- Invalid Parameters: Providing incorrect or missing required parameters (e.g., amount, currency) for other operations will result in API errors.
- To resolve errors, verify API credentials, ensure correct parameter values, and check network connectivity.
Links and References
- Cryptomus API Documentation (general reference for API endpoints)
- n8n Documentation on Creating Custom Nodes