Marketing

Resend

Resend is an email API for developers: transactional sends, the delivery event that followed each one, the domains you are allowed to send from, and audiences of contacts.

Authentication

  • API key

Actions

Generic API request. Call any Resend API endpoint on this connection, for the case where no shipped action covers it yet. The connection supplies the base URL, the authentication and the egress route, so only the path, query and body are yours to fill.

  • Create contact (v1)Create a contact inside an audience (POST /audiences/{audienceId}/contacts, application/json).
  • Get email (v1)Look up an email you already sent, by the UUID Send email returned, to find out what happened to it.
  • List API keys (v2)List the API keys that exist on the Resend account, for auditing which integrations still hold credentials and when each was last used.
  • List audiences (v1)List the contact audiences on the account - the segments that Create contact and List contacts address by audienceId - so you can resolve an audience name to its UUID.
  • List contacts (v1)List the subscribers inside one audience, e.g. to export a segment or find who has opted out.
  • List domains (v1)List the sending domains registered on the account with their verification state - the first thing to check when a send is rejected on its From address.
  • List emails (v1)List the emails already sent from the connected account, newest first, so you can find the id of a send without having kept the send response.
  • Send email (v1)Send a transactional email via the Resend Send Email API (POST /emails, application/json).

Triggers

  • Email receivedStarts when Resend receives an email at one of the account's receiving addresses, delivered by a signed Resend webhook carrying the email's sender, recipients and subject.
  • Emails to the receiving addressAnswers as an agent by email: when someone writes to one of the Resend account's receiving addresses, the agent replies in the same email thread.

Product names, logos and brands are the property of their respective owners and are used here for identification only. Their use does not imply endorsement by, or affiliation with, those owners.