Overview
This node triggers workflows based on events from a stock alert service. It listens for specific stock alert events such as when an alert is triggered, created, updated, or deleted. Users can filter these events by stock symbols and alert conditions to only trigger workflows relevant to their interests.
Common scenarios include:
- Automating notifications or actions when a particular stock hits a price threshold.
- Tracking technical indicator crossovers like moving average golden/death crosses.
- Responding to new alerts or changes in existing alerts for portfolio monitoring.
For example, a user could set the node to trigger only when an alert for "AAPL" or "GOOGL" stocks is triggered with a "Price Above" condition, enabling automated trading signals or notifications.
Properties
| Name | Meaning |
|---|---|
| Events | The types of stock alert events to listen for. Options: Alert Triggered, Alert Created, Alert Updated, Alert Deleted. |
| Options | Additional filters to narrow down triggering events: |
| - Filter by Symbol | Comma-separated list of stock symbols (e.g., AAPL, GOOGL) to only trigger for those symbols. |
| - Filter by Condition | Specific alert types to trigger on. Options include: MA Death Cross, MA Golden Cross, New High, New Low, Price Above, Price Below, Price Change Down, Price Change Up, RSI Limit, Volume Change. |
Output
The node outputs JSON data representing the event payload received from the stock alert webhook. Each output item contains:
json: The full event data object sent by the stock alert service.headers: HTTP headers from the webhook request, including signature headers used for verification.
No binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the stock alert service.
- Uses a webhook URL configured in n8n to receive event callbacks.
- Relies on cryptographic verification of webhook signatures using a secret provided by the stock alert service.
Troubleshooting
- Invalid webhook signature: If the webhook signature does not match the expected HMAC hash, the node will throw an error. Ensure the webhook secret is correctly stored and that the stock alert service is sending valid signatures.
- Webhook creation failure: Errors during webhook registration may occur due to network issues or invalid credentials. Verify API key validity and network connectivity.
- No workflow trigger despite events: Check that the event types selected match those sent by the stock alert service. Also verify symbol and condition filters are correctly set and match incoming event data.
- Webhook deletion issues: If deleting the webhook fails, it may be due to the webhook already being removed externally. The node handles this gracefully by cleaning up local state.
Links and References
- StockAlert API Documentation (replace with actual URL)
- n8n Webhook Node Documentation
- HMAC Signature Verification