Skip to main content
Automations allow you to create email steps based on custom events from your application. You can use Automations for use cases like:
  • Welcome emails
  • Drip campaigns
  • Payment recovery
  • Abandoned cart
  • Trial expiration
Automations support {{{RESEND_UNSUBSCRIBE_URL}}} for compliance with non-transactional product and marketing messaging. See Unsubscribe behavior for how to add it to a Send Email step, or read more about when to use an unsubscribe link.

​
How it works

To start executing an Automation, you need to:
1

Create Automation

Outline the sequence of steps to be executed.
2

Add Trigger

Define the event name that will trigger the Automation.
3

Define Steps

Configure the steps to be executed.
4

Send an Event

Trigger the Automation by sending an event from your application.
5

Monitor Runs

Track and debug your Automation executions using runs.

​
Create an Automation

1

Create Automation

The Automations page shows all existing automations. You can search by name and filter by status (All Statuses, Enabled, or Disabled) to quickly find the automation you need.Click Create automation to start a new Automation.Create Automation
2

Add Trigger

A trigger is the first step that will run when the Automation is executed. You can use a custom event like user.created or onboarding.completed, defining it inline or in the Events page.Add Trigger to AutomationIn this example, we will receive an event called user.created as a trigger.Add Custom EventSee the Trigger documentation for more details.
3

Define Steps

Now, we need to define the steps that will be executed.There are several step types you can add to your Automation:
Step typeDescription
ConditionBranches the workflow based on rules
DelayPauses execution for a specified duration
Wait for EventPauses execution until a specific event is received
Send EmailSends an email using a template
Contact UpdateUpdates a contact’s fields
Contact DeleteDeletes the contact
Add to SegmentAdds the contact to a segment
On this example, we will use the Send Email step.Define StepsOnce you select that step, you will be able to select an existing template.Add Send Email StepIf you select a draft template, you can publish it directly from the Send Email node without leaving the workflow editor. Click the Publish button that appears when a draft template is selected.With the template selected, you will be able to configure the email subject and sender address.Send Email Step SettingsOnce you’re done with the email, you can click on Start to enable the Automation.Automation Enabled
4

Send an Event

Now, we’re ready to send an event to trigger the Automation.On your application, you can send an event to trigger the Automation by using the API.
import { Resend } from 'resend';

const resend = new Resend('re_xxxxxxxxx');

// Trigger with a contact ID
const { data, error } = await resend.events.send({
  event: 'user.created',
  contactId: '7f2e4a3b-dfbc-4e9a-8b2c-5f3a1d6e7c8b',
  payload: {
    plan: 'pro',
  },
});

// Trigger with an email address
const { data, error } = await resend.events.send({
  event: 'user.created',
  email: 'steve.wozniak@gmail.com',
  payload: {
    plan: 'pro',
  },
});

$resend = Resend::client('re_xxxxxxxxx');

// Trigger with a contact ID
$resend->events->send([
  'event' => 'user.created',
  'contact_id' => '7f2e4a3b-dfbc-4e9a-8b2c-5f3a1d6e7c8b',
  'payload' => ['plan' => 'pro'],
]);

// Trigger with an email address
$resend->events->send([
  'event' => 'user.created',
  'email' => 'steve.wozniak@gmail.com',
  'payload' => ['plan' => 'pro'],
]);

import resend

resend.api_key = "re_xxxxxxxxx"

# Trigger with a contact ID
params: resend.Events.SendParams = {
  "event": "user.created",
  "contact_id": "7f2e4a3b-dfbc-4e9a-8b2c-5f3a1d6e7c8b",
  "payload": {
    "plan": "pro",
  },
}

resend.Events.send(params)

# Trigger with an email address
params: resend.Events.SendParams = {
  "event": "user.created",
  "email": "steve.wozniak@gmail.com",
  "payload": {
    "plan": "pro",
  },
}

resend.Events.send(params)

require "resend"

Resend.api_key = "re_xxxxxxxxx"

# Trigger with a contact ID
params = {
  event: "user.created",
  contact_id: "7f2e4a3b-dfbc-4e9a-8b2c-5f3a1d6e7c8b",
  payload: {
    plan: "pro",
  },
}

Resend::Events.send(params)

# Trigger with an email address
params = {
  event: "user.created",
  email: "steve.wozniak@gmail.com",
  payload: {
    plan: "pro",
  },
}

Resend::Events.send(params)

package main

import "github.com/resend/resend-go/v3"

func main() {
	client := resend.NewClient("re_xxxxxxxxx")

	// Trigger with a contact ID
	client.Events.Send(&resend.SendEventRequest{
		Event:     "user.created",
		ContactId: "7f2e4a3b-dfbc-4e9a-8b2c-5f3a1d6e7c8b",
		Payload: map[string]any{
			"plan": "pro",
		},
	})

	// Trigger with an email address
	client.Events.Send(&resend.SendEventRequest{
		Event: "user.created",
		Email: "steve.wozniak@gmail.com",
		Payload: map[string]any{
			"plan": "pro",
		},
	})
}

use resend_rs::{types::SendEventOptions, Resend, Result};

#[tokio::main]
async fn main() -> Result<()> {
  let resend = Resend::new("re_xxxxxxxxx");

  // Trigger with a contact ID
  let _event = resend
    .events
    .send(SendEventOptions::new("user.created").contact_id(
      "7f2e4a3b-dfbc-4e9a-8b2c-5f3a1d6e7c8b",
    ).payload(serde_json::json!({
      "plan": "pro"
    })))
    .await?;

  // Trigger with an email address
  let _event = resend
    .events
    .send(SendEventOptions::new("user.created").email(
      "steve.wozniak@gmail.com",
    ).payload(serde_json::json!({
      "plan": "pro"
    })))
    .await?;

  Ok(())
}

import com.resend.*;

public class Main {
    public static void main(String[] args) {
        Resend resend = new Resend("re_xxxxxxxxx");

        // Trigger with a contact ID
        SendEventOptions params = SendEventOptions.builder()
                .event("user.created")
                .contactId("7f2e4a3b-dfbc-4e9a-8b2c-5f3a1d6e7c8b")
                .addPayload("plan", "pro")
                .build();

        SendEventResponseSuccess data = resend.events().send(params);

        // Trigger with an email address
        SendEventOptions params2 = SendEventOptions.builder()
                .event("user.created")
                .email("steve.wozniak@gmail.com")
                .addPayload("plan", "pro")
                .build();

        SendEventResponseSuccess data2 = resend.events().send(params2);
    }
}

using Resend;
using System.Text.Json;

IResend resend = ResendClient.Create( "re_xxxxxxxxx" );

var payload = JsonSerializer.SerializeToElement( new { plan = "pro" } );

// Trigger with a contact ID
var resp = await resend.EventSendAsync( new EventSendData()
{
    Event = "user.created",
    ContactId = new Guid( "7f2e4a3b-dfbc-4e9a-8b2c-5f3a1d6e7c8b" ),
    Payload = payload,
} );
Console.WriteLine( "Event={0}", resp.Content.Event );

// Trigger with an email address
await resend.EventSendAsync( new EventSendData()
{
    Event = "user.created",
    Email = "steve.wozniak@gmail.com",
    Payload = payload,
} );

# Trigger with a contact ID
curl -X POST 'https://api.resend.com/events/send' \
     -H 'Authorization: Bearer re_xxxxxxxxx' \
     -H 'Content-Type: application/json' \
     -d '{
  "event": "user.created",
  "contact_id": "7f2e4a3b-dfbc-4e9a-8b2c-5f3a1d6e7c8b",
  "payload": {
    "plan": "pro"
  }
}'

# Trigger with an email address
curl -X POST 'https://api.resend.com/events/send' \
     -H 'Authorization: Bearer re_xxxxxxxxx' \
     -H 'Content-Type: application/json' \
     -d '{
  "event": "user.created",
  "email": "steve.wozniak@gmail.com",
  "payload": {
    "plan": "pro"
  }
}'

# Trigger with a contact ID
resend events send \
  --event user.created \
  --contact-id 7f2e4a3b-dfbc-4e9a-8b2c-5f3a1d6e7c8b \
  --payload '{"plan":"pro"}'

# Trigger with an email address
resend events send \
  --event user.created \
  --email steve.wozniak@gmail.com \
  --payload '{"plan":"pro"}'
View the API reference for more details.
5

Monitor Runs

After sending events, you can monitor your Automation executions through Runs. Each time an event triggers an Automation, a Run is created to track the execution.Monitor RunsLearn how to:
  • View Run statuses and execution details
  • Filter Runs by status (running, completed, failed, cancelled)
  • Debug failed Runs with step-level error information
  • Stop Automation Runs when needed
See the Runs documentation for more details.