Resend Automations

Product Introduction

1. Definition: Resend Automations is a cloud-based, event-driven email workflow automation platform. It falls under the technical categories of Email API, Marketing Automation, and Workflow Orchestration.
2. Core Value Proposition: It exists to enable developers and technical teams to build, manage, and observe complex, data-driven email sequences triggered by custom application events, eliminating the need for manual cron jobs, queue management, and fragmented logging systems.

Main Features

1. Custom Event Triggers: Workflows are initiated by sending a custom event via the Resend API or SDK. Events are strongly typed and can carry a payload (e.g., user.created, order.completed). This allows for precise, real-time triggering based on user actions within your application.
2. Multi-Step Workflow Builder: Automations are not single emails. You can design sequences with multiple steps, including conditional logic (if/else branches), time-based delays (minutes, hours, days), and "Wait for Event" steps that pause the workflow until a subsequent event (like user.onboarded) is received.
3. Granular Observability (Run Visibility): Every execution of an automation is logged as a "run." The dashboard provides a detailed, step-by-step audit trail for each run, showing the trigger payload, the status of each step (e.g., completed, failed, skipped, timed out), execution times, and output data, which is critical for debugging and compliance.

Problems Solved

1. Pain Point: Replacing brittle, hand-coded email sequences that rely on scheduled tasks (crons) and database flags, which are difficult to debug, scale, and modify.
2. Target Audience: The primary user is a Developer, Engineering Lead, or Product Manager at a tech company (especially startups and scale-ups) who needs to implement transactional or lifecycle emails (e.g., SaaS welcome drips, e-commerce order journeys) directly from their codebase. Secondary users include Growth and Marketing teams requiring complex, behavior-triggered campaigns without using a separate, non-technical marketing tool.
3. Use Cases:
   • Multi-day User Onboarding: Trigger a user.signed.up event, then send a welcome email immediately, wait 24 hours, send a tips email, wait for a feature.used event, and then send a relevant guide.
   • E-commerce Abandoned Cart Recovery: Trigger an order.created event, wait 1 hour for an order.completed event, and if it's not received, send a reminder email with the cart contents.
   • Post-Purchase Follow-up: After an order.shipped event, wait 3 days, then send a delivery confirmation email and request a review.

Unique Advantages

1. Differentiation: Unlike traditional marketing automation platforms (e.g., HubSpot, Mailchimp) that are GUI-first and data-warehouse oriented, Resend Automations is API-first and developer-centric. It integrates directly with application logic. Unlike building in-house, it provides a managed, observable orchestration layer without the infrastructure overhead.
2. Key Innovation: The deep integration of the "Wait for Event" step within a visual workflow builder. This allows developers to model complex, reactive user journeys that pause and resume based on real-time user behavior, a feature typically requiring significant custom backend engineering.

Frequently Asked Questions (FAQ)

1. What is the difference between Resend Automations and a traditional ESP? Traditional Email Service Providers (ESPs) focus on batch sending and broad marketing campaigns. Resend Automations is an orchestration layer built for developers, triggering emails based on real-time API events from your app, enabling complex, conditional, multi-step workflows tied directly to user behavior.
2. How does the "Wait for Event" step work technically? When a workflow hits a "Wait for Event" node, it pauses indefinitely or until a timeout. Resend's system listens for the specified event (e.g., order.completed) for that specific user/run. When you send that matching event via the API, the workflow instantly resumes, enabling interactive, event-driven email sequences.
3. Can I use Resend Automations for marketing newsletters? While possible, its strength is in transactional and lifecycle automation (welcome series, cart abandonment, password resets). For broad-cast newsletters, Resend's core Email API or Broadcasts feature is more appropriate.
4. How is pricing calculated for Resend Automations? Pricing is based on the number of automation "runs." A run is a single execution of an automation for one recipient. For example, a 3-step welcome sequence for 100 users counts as 100 runs, not 300 steps.