> ## Documentation Index
> Fetch the complete documentation index at: https://developers.arg.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Resend

> Send email, track delivery, manage contacts, and run broadcasts.

Resend connects with an API key from your Resend dashboard. It is a developer email API - one call to send, one to read what happened.

## What you can do

**Actions** - send an email, send a batch, read a sent email, list domains, add a contact, list contacts, draft a broadcast, send a broadcast.

**Triggers** - none. Use it through the assistant in chat or as an action node in an automation.

## Get your credential

<Steps>
  <Step title="Open your Resend dashboard">
    Sign in at [resend.com/api-keys](https://resend.com/api-keys).
  </Step>

  <Step title="Create a key">
    Create a key and copy it. Keys start with `re_`. Choose **Full access** for the contact, domain,
    and broadcast actions - a sending-only key connects fine but can only send.
  </Step>
</Steps>

## Connect

<Steps>
  <Step title="Open Integrations">
    In arg.ai, go to **Settings → Integrations** and click **Connect** on **Resend**.
  </Step>

  <Step title="Paste the key">Enter your API key in the API key field.</Step>
  <Step title="Save">arg.ai checks the key against Resend without sending an email.</Step>
</Steps>

## Use it

* **In chat:** *"Did the receipt I sent this morning actually get delivered?"*
* **In an automation:** add a **Resend** action node to email each new form submission a confirmation.

## Sending, one or many

* **Send an email** takes a `from` address on a verified domain, up to 50 recipients, and `html`, `text`, or both. `scheduled_at` accepts an ISO 8601 timestamp or natural language such as `in 1 hour`.
* **Send a batch** sends up to 100 individually addressed messages in one call - one personalized message per recipient, rather than one message with many recipients.
* **List domains** shows which domains are verified, so you can pick a `from` that will actually send.

Both send actions return an email id. **Read a sent email** turns that id back into the delivery outcome - its `last_event` is `delivered`, `bounced`, `opened`, `complained`, and so on.

## Contacts and broadcasts

Resend's audiences are now **segments**. A broadcast is drafted against a `segment_id`, and nothing goes out until you send it - **Draft a broadcast** returns a broadcast id and **Send a broadcast** delivers it, immediately or at a scheduled time. Only broadcasts created through the API can be sent this way.