Get Resend Email: Resend action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Email ID email_id	string	Required	The UUID returned when the email was sent

Sample request

{
  "email_id": "e.g. 49a3999c-0ce1-4ea6-ab68-afcd6dc2e794"
}

Returns

{
  "id": "49a3999c-0ce1-4ea6-ab68-afcd6dc2e794",
  "to": [
    "user@example.com"
  ],
  "from": "noreply@company.com",
  "subject": "Welcome!",
  "created_at": "2025-01-15T12:00:00.000Z",
  "last_event": "delivered"
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Get Resend Email.

What does the Get Resend Email action do in Resend?

Returns a previously-sent email by ID with delivery status. For polling-based delivery confirmation.

What inputs does Get Resend Email require?

Required: Email ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Resend returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Get Resend Email support batch operations?

Yes. Run Get Resend Email inside a Loop node to process arrays. Tiny Command handles Resend's rate limits automatically so you don't have to throttle manually.

More actions