Overview
This n8n node interacts with the Binance API to retrieve statistics for a specified futures symbol. It is designed for workflows that require automated access to futures market data, such as monitoring trading performance, building dashboards, or triggering alerts based on specific symbol statistics.
Common scenarios:
- Fetching up-to-date statistics for a particular futures contract.
- Integrating Binance futures data into reporting or analytics pipelines.
- Automating trading strategies that depend on real-time futures statistics.
Practical example:
A user could use this node to periodically pull statistics for the BTCUSDT perpetual contract and feed the results into a Google Sheets document for ongoing analysis.
Properties
| Name | Type | Meaning |
|---|---|---|
| Symbol Name or ID | options | The futures symbol to fetch statistics for. You can select from a list or specify an ID using an expression. |
Output
The node outputs a json object containing the statistics for the selected futures symbol. The exact structure of the output depends on the Binance API's response for the statistics endpoint, but typically includes fields such as price, volume, open interest, funding rate, and other relevant metrics for the specified symbol.
Dependencies
- External Service: Requires access to the Binance API.
- API Key: Needs valid Binance API credentials configured in n8n under the name
binanceApi.
Troubleshooting
- Missing or Invalid Credentials:
Error messages related to authentication (e.g., "Invalid API-key, IP, or permissions for action") indicate issues with the provided Binance API key. Ensure the credentials are correct and have the necessary permissions. - Symbol Not Found:
If an invalid or unsupported symbol is specified, the node may return an error such as "Unknown symbol." Double-check the symbol value or use the dropdown to select a valid one. - API Rate Limits:
Frequent requests may trigger Binance's rate limiting, resulting in errors like "Too many requests." Space out your requests or upgrade your API plan if needed.