Overview
This node acts as a trigger for Binance-related events within an n8n workflow. It listens for specific conditions or thresholds related to Binance data and activates the workflow when those conditions are met. Typical use cases include monitoring price changes, trade volumes, or other market indicators on Binance and triggering automated actions such as notifications, trades, or data logging.
For example, you might configure this node to trigger when the price of a cryptocurrency changes by more than a certain percentage or after a specified time interval has passed.
Properties
| Name | Meaning |
|---|---|
| Percent Threshold | A numeric value representing the percentage change threshold that triggers the node. |
| TimeThreshold | A numeric value representing the time duration threshold (likely in seconds or minutes) after which the trigger activates. |
| Is Final | A boolean flag indicating whether this is the final trigger event in a sequence or process. |
Output
The node outputs JSON data relevant to the Binance event that triggered it. This typically includes details about the market condition or event that met the configured thresholds. The output structure will contain fields describing the event specifics, such as price changes or timing information.
No binary data output is indicated in the source code.
Dependencies
- Requires an API key credential for Binance to access its data.
- The node depends on internal trigger logic defined in external files (
./triggers/binance.triggerand./triggers/binance.properties), which handle the actual event listening and data fetching from Binance. - Proper configuration of the Binance API credentials within n8n is necessary for operation.
Troubleshooting
Common issues:
- Missing or invalid Binance API credentials will prevent the node from connecting to Binance services.
- Incorrectly set thresholds (e.g., zero or negative values) may cause the trigger never to activate.
- Network connectivity problems can disrupt real-time data fetching.
Error messages:
- Authentication errors usually indicate invalid or expired API keys; reconfigure the credentials.
- Timeout or connection errors suggest network issues or Binance service downtime.
- Misconfiguration warnings may appear if required properties are missing or improperly set.