Overview
This node integrates with the StockAlert.pro API to manage webhooks related to stock alerts. Specifically, for the Webhook - Get Many operation, it retrieves a list of all configured webhooks from the StockAlert.pro service.
Typical use cases include:
- Synchronizing your system with existing webhook configurations.
- Auditing or displaying all active webhooks in your StockAlert.pro account.
- Automating workflows that depend on the current set of webhooks without manually checking the StockAlert.pro dashboard.
For example, you might use this node to fetch all webhooks and then filter or process them further in your n8n workflow.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all webhook results or limit the number of returned items (true/false). |
Output
The output is a JSON array where each element represents a webhook object retrieved from the StockAlert.pro API. Each webhook object typically contains details such as its unique ID, URL, subscribed events, and other metadata provided by the API.
No binary data is output by this operation.
Example output structure (simplified):
[
{
"id": "webhook-id-123",
"url": "https://your-app.com/webhook",
"events": ["alert.triggered", "alert.created"],
"created_at": "2023-01-01T12:00:00Z"
},
{
"id": "webhook-id-456",
"url": "https://another-url.com/hook",
"events": ["alert.updated"],
"created_at": "2023-02-15T08:30:00Z"
}
]
Dependencies
- Requires an API key credential for authenticating with the StockAlert.pro API.
- The node uses HTTP requests to communicate with the StockAlert.pro endpoints.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
Common issues:
- Authentication failures due to invalid or missing API credentials.
- Network connectivity problems preventing access to the StockAlert.pro API.
- Receiving empty results if no webhooks are configured in the StockAlert.pro account.
Error messages:
- Errors returned from the API will be propagated, e.g., unauthorized access or rate limiting.
- If the node is set to continue on fail, errors will appear in the output as objects with an
errorproperty containing the message.
Resolutions:
- Verify that the API key credential is correctly configured and has necessary permissions.
- Check network connectivity and firewall settings.
- Ensure that webhooks exist in the StockAlert.pro account before attempting to retrieve them.
Links and References
- StockAlert.pro API Documentation (hypothetical link)
- n8n documentation on creating custom nodes