ActionResendUpdated September 2026

How do I add a Resend audience contact?

Short answer: You can resend create contact in Resend by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Resend Resend Create Contact action to a workflow, map its 5 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Resend Create Contact in Resend — start free All 5 Resend actions

Resend Create Contact in Resend — start free

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
Audience ID audience_id	string	Required	The Audience ID assigned by Resend. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label.
Email email	string	Required	The email address. Used as the recipient or identifier depending on context.
First Name first_name	string	Optional	Contact's first (given) name.
Last Name last_name	string	Optional	Contact's last (family) name.
Unsubscribed unsubscribed	options	Optional	–

Sample request

{
  "audience_id": "{{trigger.audience_id}}",
  "email": "e.g. user@example.com",
  "first_name": "e.g. Jane",
  "last_name": "e.g. Doe",
  "unsubscribed": "{{trigger.unsubscribed}}"
}

Returns

{
  "id": "con_abc",
  "object": "contact"
}

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

Triggered by

Apps that pair well as the trigger for Resend Create Contact.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Resend

2 Google Sheets triggers

HubSpot → Resend

18 HubSpot triggers

FAQ

Questions about Resend Create Contact.

What does the Resend Create Contact action do in Resend?

Adds a contact to a Resend Audience for broadcast use. The base hook for "form submission → push to newsletter audience" sync workflows.

What inputs does Resend Create Contact require?

Required: Audience ID, Email. 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 run history shows the failed step with its input and the error message Resend returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Resend Create Contact support batch operations?

Run Resend Create Contact inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Resend's rate limits.

More actions