Resend Trigger icon

Resend Trigger

Triggers workflows when Resend email events occur, such as email sent, delivered, opened, clicked, bounced, or complained. Includes secure webhook signature verification.

Resend Trigger

AI-generated

Overview

This node triggers workflows based on Resend email events such as email sent, delivered, opened, clicked, bounced, complained, and other related events. It listens for webhook events from Resend, verifies the webhook signature for security, and processes only the selected event types. This node is useful for automating workflows that respond to email lifecycle events, for example, updating a CRM when an email is opened or logging bounced emails for further analysis.

Use Case Examples

  1. Trigger a workflow when an email is sent to log the event in a database.
  2. Trigger a workflow when an email is opened to update user engagement metrics.
  3. Trigger a workflow on email bounce events to notify the support team.

Properties

Name Meaning
Path The path segment for the webhook URL, replacing the default UUID segment. This defines the webhook endpoint URL to receive Resend events.
Events The Resend event types to listen for, such as email.sent, email.opened, email.bounced, etc. Only events selected here will trigger the workflow.

Output

JSON

  • type - The type of the Resend event received, e.g., email.sent, email.opened.
  • data - The payload data associated with the event, containing detailed information about the email or contact event.

Dependencies

  • Requires an API key credential for webhook signing secret to verify webhook signatures securely.

Troubleshooting

  • Webhook signature verification failure: Ensure the webhook signing secret is correctly configured and matches the secret used in the Resend dashboard.
  • Missing Svix signature headers: The webhook request must include svix-id, svix-timestamp, and svix-signature headers for verification.
  • Event type not triggering workflow: Confirm the event type is selected in the node's Events property and that the webhook URL is correctly set in the Resend dashboard.

Links

Discussion