Contact Delete

How it works
Configuration

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.

How it works

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: [
    {
      key: 'start',
      type: 'trigger',
      config: { eventName: 'user.deleted' },
    },
    {
      key: 'remove',
      type: 'contact_delete',
      config: {},
    },
  ],
  connections: [{ from: 'start', to: 'remove', type: '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

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

Contact Update

Custom Events

⌘I

Documentation

Quickstart

Learn

Resources

Contact Delete

How it works

Configuration

Documentation

Quickstart

Learn

Resources

​How it works

​Configuration

How it works

Configuration