Overview
This node integrates with the Binance API to manage futures orders. It allows users to perform various actions on futures trading such as placing, updating, canceling, listing, and clearing orders, as well as closing positions. This node is beneficial for automating futures trading workflows, managing open orders programmatically, or integrating Binance futures trading into larger automation pipelines.
Practical examples include:
- Automatically placing buy or sell orders based on market signals.
- Canceling specific futures orders when certain conditions are met.
- Listing all current futures orders to monitor trading activity.
- Closing positions automatically to manage risk.
Properties
| Name | Meaning |
|---|---|
| Action | The operation to perform on futures orders. Options: CANCEL (cancel a future), CLEAR (clear orders), GET (list orders), PUT (place orders), SMART (place smart orders), POSITION_CLOSE (close a position), UPDATE (update an order). |
| Side | The side of the order, either BUY or SELL. Shown only for actions other than CANCEL, CLEAR, GET, POSITION_CLOSE. |
| Order ID | The identifier of the order to act upon. Required except for actions CLEAR, GET, CANCEL, POSITION_CLOSE. |
| Symbol Name or ID | The symbol representing the futures contract. Can be selected from a list or specified via expression. |
| Quantity | The amount of the asset to trade. Required except for CLEAR, GET, CANCEL, POSITION_CLOSE actions. |
| Price | The price at which to place or update the order. Required except for CLEAR, GET, CANCEL, POSITION_CLOSE actions. |
| Reduce Only | Boolean flag indicating if the order should only reduce an existing position. Not shown for CLEAR, GET, CANCEL, POSITION_CLOSE actions. |
Output
The node outputs JSON data representing the response from the Binance API related to the futures order action performed. This typically includes details about the order status, order IDs, execution results, or lists of orders depending on the action chosen.
If binary data were involved (not indicated here), it would represent associated files or media, but this node focuses on JSON responses from the API.
Dependencies
- Requires an API key credential for authenticating with the Binance API.
- Depends on the Binance API being accessible and the user having appropriate permissions for futures trading.
- Uses internal methods and properties loaded from bundled dependencies for symbol loading and executing API calls.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Using incorrect or unsupported symbols may result in errors from the Binance API.
- Attempting to cancel or update non-existent orders will return errors.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Authentication errors indicate invalid or expired API keys; verify and update credentials.
- "Order not found" errors suggest the specified order ID does not exist or has already been processed.
- Validation errors for required fields mean some input properties are missing or incorrectly formatted; ensure all required fields per action are provided.
Links and References
- Binance Futures API Documentation
- n8n Expressions Documentation (for using expressions in property inputs)