Overview
This node enables users to place spot trading orders on the Binance cryptocurrency exchange. It supports creating buy or sell orders for specified token trading pairs with configurable order types and parameters. This node is beneficial for automating trading strategies, managing portfolio allocations, or integrating Binance spot trading into broader workflows.
Practical examples include:
- Automatically placing limit buy orders when a certain market condition is met.
- Executing market sell orders to quickly liquidate positions.
- Setting up conditional orders with specific time-in-force policies to control order execution behavior.
Properties
| Name | Meaning |
|---|---|
| Token Trading Pair | The trading pair symbol on Binance (e.g., BTCUSDT) representing the tokens to trade. |
| Trade Side | Direction of the trade: either "Buy" or "Sell". |
| Order Type | Type of order to place: "Limit" (set price) or "Market" (execute immediately at market). |
| Time in Force | Order execution policy: "Good Till Cancel", "Immediate or Cancel", or "Fill or Kill". |
| Quantity | Amount of the asset to buy or sell. |
| Price | Price per unit for limit orders (ignored for market orders). |
Output
The node outputs an array of JSON objects, each representing the response from Binance after placing an order. The structure corresponds to Binance's API response for new spot orders, typically including details such as order ID, status, executed quantity, and other metadata about the placed order.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential with appropriate permissions to trade on Binance.
- Uses the official Binance Spot API client library (
@binance/connector). - The node expects valid credentials configured in n8n for authenticating requests to Binance.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Insufficient balance or incorrect trading pair symbols can lead to order rejections.
- Using a price parameter with market orders may be ignored or cause errors.
- Network or API rate limits might result in request failures.
Error messages:
- Authentication errors indicate problems with the provided API key or secret; verify and update credentials.
- Order validation errors often specify invalid parameters like quantity or symbol; check input values carefully.
- Timeout or connectivity errors suggest network issues; retry or check internet connection.