Overview
This n8n node interacts with the Binance API to retrieve information about futures positions. It is designed for workflows that need to access or automate trading data from Binance Futures, such as monitoring open positions, building dashboards, or triggering alerts based on position changes.
Common scenarios:
- Fetching current futures positions for a specific symbol.
- Integrating Binance futures data into automated trading or reporting workflows.
- Monitoring and responding to changes in futures positions.
Practical example:
A user could use this node to automatically fetch their BTCUSDT futures position and send an alert if certain thresholds are met.
Properties
| Name | Type | Meaning |
|---|---|---|
| Symbol Name or ID | options | The futures trading pair (symbol) to query. You can select from a list or specify an ID using an expression. |
Output
The node outputs a JSON object containing details about the requested futures position for the specified symbol. The exact structure depends on the Binance API response, but typically includes fields such as:
symbol: The trading pair symbol (e.g., BTCUSDT).positionAmt: The amount of the asset in the position.entryPrice: The price at which the position was entered.unrealizedProfit: Current unrealized profit/loss.leverage: Leverage used for the position.- ...and other relevant position details.
Note:
If the node supports binary output, it would represent raw data from the Binance API, but for this operation, the output is expected to be JSON only.
Dependencies
- External Service: Requires access to the Binance API.
- Credentials: Must configure Binance API credentials (
binanceApi) in n8n. - Environment: No special environment variables required beyond n8n's standard credential management.
Troubleshooting
Common issues:
- Invalid or missing credentials: Ensure your Binance API key and secret are correctly configured in n8n.
- Symbol not found: If you enter an invalid symbol, the node may return an error or empty result. Double-check the symbol name or ID.
- API rate limits: Binance enforces rate limits; excessive requests may result in temporary bans or errors.
- Network errors: Connectivity issues between n8n and Binance can cause failures.
Error messages and resolutions:
"Invalid API-key, IP, or permissions for action": Check your API key permissions and allowed IPs in Binance settings."No such symbol": Verify the symbol exists and is available for futures trading on Binance."Timestamp for this request is outside of the recvWindow": Ensure your server time is synchronized.