finlight Webhook Trigger
AI-generatedOverview
This node acts as a webhook trigger for receiving new events from Finlight. It listens for incoming POST requests on a specified webhook path and validates the request based on the selected authentication method (Webhook Secret, Basic Auth, or None). Upon successful validation, it extracts relevant event data from the webhook payload and outputs it for further workflow processing. This node is useful for automating workflows that respond to real-time Finlight events such as news updates, sentiment analysis, or company-related information.
Use Case Examples
- Automatically process and analyze news articles as they are published by Finlight.
- Trigger alerts or notifications based on sentiment or confidence scores in Finlight events.
- Integrate Finlight event data into CRM or data analytics platforms for enhanced insights.
Properties
| Name | Meaning |
|---|---|
| Authentication Method | Specifies the authentication method used to validate incoming webhook requests from Finlight. Options include Webhook Secret (X-Finlight-Key), Basic Auth, or None. |
Output
JSON
workflowData0
*0
*json
*link- URL link of the event content
*source- Source of the event
*title- Title of the event
*publishDate- Publish date of the event
*language- Language of the event content
*summary- Summary of the event (if available)
*content- Full content of the event (if available)
*sentiment- Sentiment analysis result of the event (if available)
*confidence- Confidence score of the sentiment analysis (if available)
*images- Array of images related to the event (if available)
*companies- Array of companies mentioned in the event (if available)
*createdAt- Creation timestamp of the event (if available)
*categories- Categories associated with the event (if available)
*countries- Countries related to the event (if available)
*isUpdate- Boolean indicating if the event is an update (if available)
*revisedDate- Date when the event was revised (if available)
Dependencies
- Requires credentials for authentication: either a webhook secret key credential or HTTP Basic Auth credentials depending on the selected authentication method.
Troubleshooting
- Unauthorized errors occur if the webhook secret or Basic Auth credentials do not match the incoming request headers. Verify that the correct credentials are configured in the node settings.
- If no authentication is selected, ensure that the webhook endpoint is secured by other means to prevent unauthorized access.
- The node expects a POST request with a JSON body containing specific event fields. Malformed or missing data in the webhook payload may cause incomplete output data.
Links
- Finlight Webhook Documentation - Official documentation for setting up and using Finlight webhooks.