Overview
The Falconyte Trigger node allows users to receive real-time events from Falconyte webhooks. It is designed to automate workflows based on specific email-related events such as when an email is queued, sent, opened, clicked, or bounced, as well as contact and lead activities. This node is beneficial for scenarios where users want to trigger actions in their workflows based on email campaign activities or contact updates, enabling timely responses and automation in marketing or customer engagement processes.
Use Case Examples
- Trigger a workflow when an email is successfully sent to update a CRM system.
- Start a workflow when a recipient opens an email to send a follow-up message.
- Automate lead creation in a sales system when a lead is created from email activity.
Properties
| Name | Meaning |
|---|---|
| Events | A collection of email-related events to subscribe to for triggering the workflow. Users can select multiple events such as 'Email Sent', 'Email Opened', 'Contact Saved', etc. |
Output
JSON
json- The event payload received from Falconyte, including the event data and metadata such as event name, webhook ID, mode, and signature timestamp.headers- HTTP headers received with the webhook request.
Dependencies
- Requires Falconyte API credentials for authentication and webhook management.
Troubleshooting
- Ensure that at least one event is selected to subscribe to; otherwise, webhook creation will fail.
- If the webhook secret is missing or invalid, the node will respond with an error and not process events. Reinitializing the trigger may be necessary.
- The node verifies the X-FY-Signature header for security; missing or invalid signatures will cause the webhook to reject the request with an error.
- If the webhook ID stored in static data is not found on Falconyte, the node attempts to create a new webhook automatically.
Links
- Falconyte Webhooks Documentation - Official documentation for Falconyte webhook events and setup.