Cryptomus Payout icon

Cryptomus Payout

Working with the Cryptomus Payout API for processing cryptocurrency withdrawals

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, fetching detailed payout information, listing available payout services, and transferring funds between personal and business wallets.

A common use case is automating cryptocurrency withdrawal workflows in financial or trading platforms, where users need to programmatically initiate payouts or track their status. For example, a business could use this node to batch process multiple crypto withdrawals or reconcile payout histories for accounting.

Specifically, the Get Payout History operation allows users to retrieve a list of past payout transactions filtered by date range, which is useful for auditing or reporting purposes.

Properties

Name Meaning
Request Parameters Collection of optional filters to narrow down the payout history results:
- Date From Start date/time (format YYYY-MM-DD HH:mm:ss) to filter payouts from this point onward.
- Date To End date/time (format YYYY-MM-DD HH:mm:ss) to filter payouts up to this point.
Платежная система Payment system to filter payouts by. Options: Binance, BinanceP2p, Exmo, Kucoin.

Output

The node outputs an array of JSON objects representing the response from the Cryptomus API for the requested operation.

For Get Payout History, the output JSON contains the payout records matching the specified filters. Each record typically includes details such as payout ID, amount, currency, status, timestamps, and other metadata returned by the API.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for the Cryptomus service 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 n8n's HTTP request helper.

Troubleshooting

  • API Type Mismatch Error: If the configured API credential is not set for "Payout" type, the node throws an error indicating that only payout-type credentials are allowed. Ensure the correct API key with payout permissions is used.
  • Invalid Date Format: The date filters must be in YYYY-MM-DD HH:mm:ss format. Incorrect formatting may cause API errors or empty results.
  • Network or Authentication Errors: Standard HTTP errors may occur if the API key is invalid, expired, or network connectivity issues arise. Verify API credentials and network access.
  • Empty Results: If no payouts match the filter criteria, the output will be an empty list. Adjust date ranges or payment system filters accordingly.

Links and References

Discussion