Actions10
- Spot Actions
- Future Actions
- Custom Actions
Overview
This node integrates with the Binance API, specifically providing functionality related to futures trading statistics. The "Future - Statistics" operation allows users to retrieve statistical data about a specific futures symbol (trading pair) on Binance. This can be useful for traders or analysts who want to programmatically access market data such as price changes, volume, and other relevant metrics for futures contracts.
Practical examples include:
- Automatically fetching the latest futures statistics for a given symbol to inform trading decisions.
- Integrating futures market data into dashboards or reports.
- Triggering workflows based on specific futures market conditions.
Properties
| Name | Meaning |
|---|---|
| Symbol Name or ID | Select a futures trading symbol from a list or specify its ID using an expression. This identifies the futures contract for which statistics will be retrieved. |
Output
The node outputs JSON data containing the futures statistics for the specified symbol. This typically includes fields such as price change, price change percent, weighted average price, previous close price, last price, bid price, ask price, open price, high price, low price, volume, quote volume, open time, close time, first trade ID, last trade ID, and number of trades.
If binary data were involved, it would represent associated files or media, but in this case, the output is purely JSON-based market data.
Dependencies
- Requires an API key credential for authenticating with the Binance API.
- The node depends on the Binance API service being available and accessible.
- No additional environment variables are explicitly required beyond the API authentication.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication errors.
- Specifying an incorrect or unsupported symbol name/ID may result in errors or empty responses.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Authentication failures usually indicate invalid API keys; verify and update credentials.
- "Symbol not found" or similar errors suggest the symbol does not exist or is misspelled; check the symbol list.
- Rate limit exceeded errors mean too many requests in a short period; implement retry logic or reduce request frequency.
Links and References
- Binance Futures API Documentation
- n8n Expressions Documentation (for specifying dynamic symbol IDs)