Resend integration

What it does

The Resend integration lets your agency send transactional email from any workflow and turn engagement feedback into automation. Connect a client's Resend API key once and your workflows can send individual emails, retrieve message detail by id, manage audience contacts, list verified sending domains, and react in real time when Resend reports a delivery, bounce, open, or click.

Connect a Resend account

1. Open your workspace in TaskJuice and navigate to Connections.
2. Choose Resend and click Connect.
3. In a new tab, sign in to resend.com as the client and open API Keys.
4. Create a new API key with Sending Access (or Full Access if the workflow manages audiences and contacts) and copy the value once. Resend shows the key only at creation time.
5. Paste the key into TaskJuice and save the connection.

To rotate or revoke the key later, return to the API Keys page in Resend, delete or regenerate the key, and update the TaskJuice connection.

Triggers

• resend/email-delivered fires when Resend confirms a recipient mail server accepted an outbound message.
• resend/email-bounced fires when an outbound message hard- or soft-bounces, with the bounce type, sub-type, and provider message.
• resend/email-opened fires when a tracked recipient opens a message.
• resend/email-clicked fires when a tracked recipient clicks a link inside a message, with the link, timestamp, IP address, and user agent.

Each webhook delivers one event per POST. Configure the webhook in the Resend dashboard, copy the signing secret, and supply it when subscribing the trigger; TaskJuice verifies the Svix-format svix-signature header on every inbound POST against the svix-id and svix-timestamp headers and rejects unsigned or replayed traffic.

Actions

• resend/send-email sends a single transactional email with HTML and plain-text bodies, optional CC, BCC, reply-to, and tag metadata.
• resend/get-email fetches the full delivery state and content for one message by Resend email id.
• resend/create-contact adds a contact to an audience by id, with optional first name, last name, and unsubscribed flag.
• resend/list-contacts lists every contact within an audience by id.
• resend/list-domains returns the sending domains verified on the connected Resend account, with status and region.

Known limitations

• The integration calls the Resend REST API with the connected API key. Per-key send rates, sandbox restrictions, and verified-sender requirements are governed by the client's Resend account, not by TaskJuice. When Resend returns a 422 with a validation error code, TaskJuice surfaces it as a non-retryable validation failure; 429 responses are surfaced as retryable rate limits.
• Resend signs webhook payloads with the Svix scheme. Inbound authentication requires the signing secret shown when you create the webhook in Resend, stored alongside the trigger. Rotate the secret in Resend and update TaskJuice together; both sides accept overlapping secrets only briefly during rotation.
• Open and click tracking is governed by the per-message tracking settings on the connected Resend account. Workflows that branch on the Opened or Clicked trigger must confirm tracking is enabled on the originating send.
• The integration supports up to 50 to recipients per send-email call and up to one audience per create-contact call, matching the Resend API limits.