How to integrate Unify with Resend
To integrate Unify with Resend, configure a Unify Play Webhook action to call the documented API with POST, the required credentials, and the destination-specific JSON body. Use this connection to create a Resend contact for an explicitly designed audience process.[1][2][3]
- Connection
- Via API
- Customer engagement
- Tool
- Resend
- Resend
- Data flow
- Unify → Resend
- JSON payload
At a glance
- Via API: Resend receives the handoff
- POST request with an explicit JSON contract and destination authentication
- Test scenario: Separate contact creation from sending
When this workflow makes sense
Start with the decision your team needs to make, then choose the connection that supports it.
Use a contact handoff to prepare an audience record without accidentally starting communication. Separate the source of identity from the source of subscription eligibility. This makes the transition from sales context to marketing ownership reviewable.
A good fit when
Teams that want to create a Resend contact for an explicitly designed audience process and have an owner for the receiving process. The destination account must permit the documented request and the chosen downstream action.
Reconsider the plan when
The receiving team has not agreed how this Resend operation should behave when the same record arrives again. Resolve the matching rule before enabling retries.
Design the handoff
Use this framework to agree on the input, the next action, and who owns the result.
Suggested workflow design, based on the documented capabilities below.
| Stage | Decision to make |
|---|---|
| Business decision | Create a Resend contact for an explicitly designed audience process |
| Receiving contract | Agree which of the 3 example data fields the receiving process actually needs. Set missing-value and identity rules in the field mapping below. |
| Execution boundary | Give one owner access to inspect the Resend request and its resulting action. |
| Completion | Decide who can confirm the Resend outcome and recover a failed or repeated handoff. Use the completion check below as the acceptance criterion. |
Explore the scenarios
Choose the situation that fits your team and work through the proposed plan.
Open a scenario to explore its plan. Checklists track your selections in this page only.
Create a Resend contact for an explicitly designed audience process
Start with one controlled record and one intended Resend outcome. Keep the test destination separate from live operations.
The receiving owner must distinguish accepted input from completed work. Agree on the evidence required before treating this handoff as successful.
- Prepare the destination using the Resend setup checklist
- Resolve the sample fields for one known record and inspect the request before sending it
- Trace that handoff through the receiving operation and compare the actual destination values with the source
Separate contact creation from sending
Separate contact creation from sending: create the fictional unsubscribed contact and confirm no campaign is triggered by the implementation. Review topic decisions as a separate step.
Decide whether this case should be held for review, corrected, or retried. Make that decision before running Resend against live records.
- Isolate the test in a controlled destination and record the starting state
- Run the edge case described above and capture the actual response and destination state
- Recover the record once, then check that recovery did not create unintended additional work
Illustrative workflow, not a preconfigured automation. Complete these checks in your own account.
Define success before launch
Inspect the data and the intended outcome separately. Connection status is only the first check.
Expected, not tested
Create a Resend contact for an explicitly designed audience process
Inspect the contact, global subscription state, and any selected segments before testing a separate sending process.
Documentation-based reference. This workflow has not been tested end to end. Use a record or event you control before enabling live activity.
Questions answered
Common decisions when connecting Unify and Resend.
Does the sample subscribe the prospect to Broadcasts?
No. It sets unsubscribed to true. Change subscription choices only when the corresponding permission and intended audience behavior are established.[3]
Limits & decisions
Check these boundaries before designing a live workflow around the connection.
What the connection supports
Understand the connection, the data involved, and the behavior that matters for a Unify + Resend workflow.
POST / JSON
| Decision | What to know |
|---|---|
| Unify action | Outbound HTTP request with configurable method, authentication, headers, and body[1] |
| Receiving operation | Create an API key and decide how global and topic subscription choices are managed. This fictional sample creates an unsubscribed contact.[3] |
| Response handling | Webhook response bodies are not available as inputs to later Unify Play actions[2] |
Technical setup reference
References and requirements for the Resend connection.
Connection requirements and setup checklist
Before connecting
- A Unify Play with a Webhook action and a controlled record for testing
- Access to the intended Resend environment and the permissions required by the cited API or trigger
- The destination identifiers, credentials, and schema used by the request below
- An agreed record identity, duplicate policy, and owner for failed handoffs
Prepare the Resend destination
Create an API key and decide how global and topic subscription choices are managed. This fictional sample creates an unsubscribed contact.[3]
Configure the destination action
POST the contact body using REST field names. Add properties or segment IDs only when their definitions already match your Resend setup.[3]
Configure the Unify request
Use POST, the endpoint and authentication below, and JSON body format in the Webhook action. Replace setup placeholders, then inspect Expand preview with a controlled record. The receiver must respond within 8 seconds; webhook response bodies are not exposed to later Play steps.[1][2]
Validate the complete handoff
Run the success and edge-case scenarios in Explore the scenarios with a controlled record. Save the request identity and destination evidence, then apply the completion check before enabling live traffic.[3]
Request configuration
- Method
POST- URL pattern
https://api.resend.com/contacts- Headers
Content-Type: application/jsonAuthorization: Bearer YOUR_RESEND_API_KEY- Authentication
- Use Authorization: Bearer YOUR_RESEND_API_KEY with permission to manage contacts.
Choose JSON as the body format. Unify sets Content-Type automatically. The receiver must respond within Unify’s 8-second timeout; request responses are not passed to later Play steps.[2]
Replace URL placeholders with the actual receiver URL from your account or deployed application. These example URLs are not working endpoints.
Example handoff payload
Start with a fictional prospect. Validate the resolved values before using a real record.
Inspect the sample payload and field mapping
{
"email": "alex@example.com",
"first_name": "Alex",
"last_name": "Morgan",
"unsubscribed": true
}Fictional data. Replace sample values before using a real Play.
Illustrative JSON for the documented receiving operation. All prospect values are fictional. Replace credentials, identifiers, schema-specific fields, and fixed example values before a controlled test. Use the field mapping to distinguish record data from fixed settings. Select available fields in your Play and inspect Expand preview; do not replace configuration values with prospect data.[1][2][3]
| Payload field | Value to send |
|---|---|
email | Select the available email field for the controlled person or company record in Unify. Keep the receiving field a string. If missing: Skip or hold the handoff if this value is required by the destination; omit it only when the destination contract permits omission. Do not send a guessed value. |
first_name | Select the available first name field for the controlled person or company record in Unify. Keep the receiving field a string. If missing: Skip or hold the handoff if this value is required by the destination; omit it only when the destination contract permits omission. Do not send a guessed value. |
last_name | Select the available last name field for the controlled person or company record in Unify. Keep the receiving field a string. If missing: Skip or hold the handoff if this value is required by the destination; omit it only when the destination contract permits omission. Do not send a guessed value. |
unsubscribed | Keep the boolean true for this sample: the handoff does not establish marketing subscription permission. Do not quote it as a string or infer consent from a prospect record. If missing: Keep this configured value in the request; do not replace it with a blank prospect field. |
Map email, first_name, and last_name. Keep the subscription value tied to a real consent decision; the example deliberately does not opt the person into Broadcasts.
Troubleshooting
Start with the stage where the expected data or action stops appearing.
The request is rejected
Use Authorization: Bearer YOUR_RESEND_API_KEY with permission to manage contacts. Check the receiving account, permissions, endpoint, and required fields against the cited documentation.[3]
The values or destination are wrong
Compare the resolved JSON with the field-by-field contract in Example handoff payload. Check identifiers against the selected Resend environment, and distinguish an absent source value from an intentional static value. Fix the mapping before repeating the write.[3]
Receipt does not match the expected result
Find the request in the receiving logs, then inspect the actual Resend resource or execution. If the request was accepted but no result exists, investigate the destination failure before retrying. Keep the same logical handoff identity when recovering a repeat.[3]
Sources & review
Official documentation reviewed on September 15, 2026.
Technical claims link to primary documentation from Unify and the destination tool. Scenarios, field choices, and recovery plans are editorial implementation examples. Documentation review is separate from execution testing.
Documentation reviewed; end-to-end execution not tested. No named technical reviewer has signed off on these articles yet.
Content updated: . Report a correction to Unify with the tool name, source URL, and behavior you observed.
Keep exploring
