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 new high or low.
- Triggering workflows when moving average crossovers occur (golden cross or death cross).
- Responding to price changes or volume changes in selected stocks.
- Integrating stock alert events into broader automation pipelines for trading, reporting, or monitoring.
For example, a user could set the node to trigger only when alerts for "AAPL" or "GOOGL" stocks are triggered with a "Price Above" condition, enabling targeted workflow execution.
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: |
| - Filter by Symbol | Comma-separated list of stock symbols (e.g., AAPL, GOOGL) to restrict triggering only to 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.
- Verifies incoming webhook requests using HMAC SHA256 signatures with a secret provided by the stock alert service.
- Depends on the
cryptomodule for signature verification.
Troubleshooting
- Invalid webhook signature error: This occurs if the webhook request's signature does not match the expected HMAC hash. Ensure the webhook secret is correctly stored and that the stock alert service is sending valid signatures.
- No workflow trigger despite events firing: Check that the event type is included in the selected "Events" property and that any symbol or condition filters match the incoming event data.
- Webhook creation failure: If the node cannot create the webhook on the stock alert service, verify that the API key credential is valid and has sufficient permissions.
- Missing or incorrect webhook URL: Confirm that the webhook URL registered with the stock alert service matches the one generated by n8n.