Upsert a Contact
A 3-step recipe with Omnisend. We can help you get access.
Recipe · 3 steps
Upsert a Contact
with Omnisend · Customer Data Management
Upsert a single Omnisend contact by id with an email-based fallback.
- Attempt to read an existing contact by its Omnisend contact id. A 200 means the contact exists and can be patched by id; any other status routes to the create-or-update fallback.
- Patch the matched contact by id with the supplied attributes. Only the provided fields are changed.
- Create the contact, or update it in place, using the email as the natural key when no contact id matched.
What you'll need to have ready
- apiKey: The Omnisend API key sent in the X-API-KEY header.
- contactId: Optional Omnisend contact id used to look up an existing contact.
- email: The contact email used as the natural key for create-or-update.
- firstName: The contact first name to write.
- lastName: The contact last name to write.
- status: Subscription status (subscribed, unsubscribed, nonSubscribed).
For your developer
Arazzo workflow omnisend:upsert-contact, 3 operations: {$sourceDescriptions.contactsApi.url}#/paths/~1contacts~1{id}/get → {$sourceDescriptions.contactsApi.url}#/paths/~1contacts~1{id}/patch → {$sourceDescriptions.contactsApi.url}#/paths/~1contacts/post. Specs on APIs.io.