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.
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 | – |
{"audience_id": "{{trigger.audience_id}}","email": "e.g. user@example.com","first_name": "e.g. Jane","last_name": "e.g. Doe","unsubscribed": "{{trigger.unsubscribed}}"}
{"id": "con_abc","object": "contact"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.