Work with contacts and audiences
Contact and audience nodes let a workflow read customer information and change records or memberships. They operate on resources in the automation's workspace.
Automations is in Early access. Your workspace permissions determine which actions you can perform.
Find and use a contact
- Add Get contact when you have a contact ID, or List contacts when you need to search by supported filters.
- Map the identifier or search value from your trigger.
- For a list, add a Branch to distinguish an empty result from a found contact.
- Map the selected contact's fields into the next step.
An empty successful search is a result to handle. It does not follow the action's failure path. Use that path for a rejected or failed read.
Listing nodes return one page. A next-page cursor means more records may exist. Neither List contacts nor List audience contacts automatically visits further pages or performs a later action for each contact.
Create or update records
Use Create contact for a new record and Update contact for a known record. A lookup followed by creation is not an atomic operation: another process may create a matching contact between those steps. Handle a creation conflict rather than assuming the new contact exists.
Create or update contacts accepts a prepared batch. Inspect each entry's result: one entry can fail while others are created or updated. A successful node does not mean each batch entry succeeded, and successful changes are not rolled back when another entry fails.
Large inputs and results can exceed automation data limits even when the Contacts product accepts a larger batch. Use a smaller prepared batch if validation or the run reports an oversized value.
Manage static audience memberships
- Select an existing audience, or add Create audience to make one as part of the workflow.
- Use Add contacts to audience, Remove contact from audience, or Remove contacts from audience with explicit contact IDs.
- Inspect the action result and handle failures before proceeding.
Membership removal retains the contact. Adding to one audience and removing from another are separate operations, so a failure between them can leave the contact in both audiences. Plan the failure path for the state that needs attention.
Use Get audience and Update audience to read or change the audience itself. These nodes do not make a snapshot of its members or turn the workflow into a broadcast.
Delete a contact deliberately
Use Delete contact to permanently remove the contact and its audience memberships.
Preference and suppression records associated with the person's channel address can remain. Deleting and recreating a contact does not remove an opt-out or delivery block.
Next steps
- Use preferences and lookups.
- Use data from earlier steps.
- Preview and check a workflow.
- Browse the Automations guides.
संबंधित संसाधन
इस विषय के लिए डॉक्यूमेंटेशन, गाइड और उदाहरणों के साथ आगे बढ़ें। संसाधन अंग्रेज़ी में हैं।