Contact Delete

Adding a step
Configuration

Automations are currently in private alpha and only available to a limited number of users. APIs might change before GA.To use the methods on this page, you must upgrade your Resend SDK:

npm install resend@6.10.0-preview-workflows.3

This step removes the contact that triggered the Automation from its Audience. Once deleted, the contact will no longer receive emails from that audience and any remaining steps in the Automation run are skipped. Common use cases:

Compliance — Delete contacts as part of a data-removal workflow.
Churn — Remove a contact, when a user stops using your service.
Unsubscribe flows — Automatically remove contacts who opt out.

Adding a step

Using the dashboard
Using the API

Include the Delete contact step to your Automation.

No configuration required. It is ready as soon as you add it.

Add a contact_delete step to your Automation’s steps array.

import { Resend } from 'resend';

const resend = new Resend('re_xxxxxxxxx');

const { data, error } = await resend.automations.create({
  name: 'Remove churned users',
  steps: [
    {
      ref: 'trigger',
      type: 'trigger',
      config: { eventName: 'user.deleted' },
    },
    {
      ref: 'remove_contact',
      type: 'contact_delete',
      config: {},
    },
  ],
  edges: [{ from: 'trigger', to: 'remove_contact', edgeType: 'default' }],
});

The config object is empty, so no additional fields are required.

Deleting a contact is permanent. The contact and all of its properties are removed from the audience. If the contact needs to be re-added later, it must be created again.

Configuration

Example

{
  "ref": "remove_contact",
  "type": "contact_delete",
  "config": {}
}

Contact Update

Runs

⌘I

Documentation

Quickstart

Learn

Resources

Contact Delete

Adding a step

Configuration

Documentation

Quickstart

Learn

Resources

​Adding a step

​Configuration

Adding a step

Configuration