Actions6
Overview
The node "Cryptomus Payout" integrates with the Cryptomus Payout API to facilitate cryptocurrency withdrawals and wallet transfers. It supports multiple operations including creating payouts, retrieving payout history or information, listing available payout services, and transferring funds between business and personal wallets.
The "Transfer to Personal Wallet" operation specifically allows transferring a specified amount of cryptocurrency from a business wallet to a personal wallet within the Cryptomus system. This is useful for businesses managing crypto funds who want to move assets back to their personal wallets securely and efficiently.
Practical examples:
- A company paying out employee bonuses in cryptocurrency can transfer funds from its business wallet to employees' personal wallets.
- A crypto exchange or service provider moving funds internally between wallets for accounting or operational purposes.
Properties
| Name | Meaning |
|---|---|
| Amount | The amount of cryptocurrency to transfer (e.g., "10.50"). |
| Currency | The type of cryptocurrency to transfer (e.g., "USDT", "BTC", "ETH"). |
| Платежная система | The payment system used for the transaction. Options: Binance, BinanceP2p, Exmo, Kucoin. |
Note: The property "Платежная система" means "Payment System" in Russian.
Output
The node outputs an array of JSON objects, each representing the response from the Cryptomus API for the executed operation.
For the "Transfer to Personal Wallet" operation, the output JSON contains the API response confirming the transfer details such as transaction status, transferred amount, currency, and any relevant identifiers returned by the Cryptomus API.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for the Cryptomus Payout API configured in n8n.
- 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
- API Type Mismatch: If the provided API credentials are not for the Payout API type, the node will throw an error indicating that only Payout API credentials are supported.
- Invalid Parameters: Missing or incorrect parameters like amount, currency, or invalid payment system options may cause API errors.
- Network Issues: Connectivity problems with the Cryptomus API endpoint can result in request failures.
- Error Handling: If
continueOnFailis enabled, errors will be captured in the output JSON under anerrorfield instead of stopping execution.
To resolve common errors:
- Verify that the API credentials are correctly set up and correspond to the Payout API.
- Ensure all required fields (amount, currency) are provided and valid.
- Check network connectivity and Cryptomus API status.
- Review error messages returned in the output JSON for specific API error details.
Links and References
- Cryptomus API Documentation (general reference for API endpoints and parameters)
- n8n Documentation on Creating Custom Nodes