Actions28
- Email Actions
- Submit Campaign Event
- Send Email
- Upsert Contact
- Bulk Upsert Contacts
- List Campaigns
- Stop Campaign
- Create Template
- Submit Event
- List Templates
- Delete Template
- List Mail Accounts
- Get Event Decisions
- Unsubscribe Contact
- List Unsubscribes
- List Webhooks
- Create Webhook
- Delete Webhook
- Update Webhook
- Get Webhook
- Disable Webhook
- List Webhook Deliveries
- Create Campaign
- Start Campaign
- Get Template
- Get Event
- Bulk Unsubscribe Contacts
- Enable Webhook
- Simulate Webhook Event
Overview
This node submits an event related to email activities to the Falconyte API. It supports various event types such as contact saved, contact unsubscribed, lead created, and sale created. The node is useful for tracking and recording specific email-related events in a system, enabling automation workflows to react to these events. For example, it can be used to log when a contact is saved or when a sale is created, helping businesses automate follow-up actions or analytics.
Use Case Examples
- Submit a 'contact.saved' event when a new contact is added to the system.
- Submit a 'sale.created' event to track new sales and trigger related workflows.
Properties
| Name | Meaning |
|---|---|
| Event Name | Type of event to submit, e.g., contact.saved, contact.unsubscribed, lead.created, sale.created |
| Email address associated with the event, optional to specify the related contact's email. | |
| Idempotency Key | Unique identifier to deduplicate events, preventing duplicate submissions. |
| Occurred At | Timestamp of when the event occurred; defaults to the current time if not provided. |
| Payload | Additional event data provided as a JSON object to include extra context or details. |
Output
JSON
json- Response from Falconyte API after submitting the event, containing details about the submitted event or any errors.
Dependencies
- Requires an API key credential for Falconyte API authentication.
Troubleshooting
- Ensure the API key credential is correctly configured and has the necessary permissions to submit events.
- Verify that the event name is one of the supported options; otherwise, the node will throw an unsupported operation error.
- If the event submission fails, check the payload JSON for correct formatting and valid data types.
- Network or API endpoint issues may cause request failures; verify the base URL and network connectivity.