Trigger use cases

This page lists 1–2 concrete use cases for using each CXP activity type as an automation trigger.

Event created

  • An event entered the system and you want to act on it. For example you recieve a newsletter subscribed event and want to trigger a thank you workflow.

Segment joined / left

  • Segment joined: a customer enters a high-value segment → trigger a VIP welcome message or notify the account manager.

  • Segment left: a customer drops out of an "active" segment (churn risk) → trigger a re-engagement or win-back campaign.

🚧 Event failed

  • Event failed: an event could not be processed (validation error, missing required fields) → trigger an alert to the data/engineering team so a source-system issue is caught quickly instead of data silently getting lost.

🚧 Object created

  • Object created: a new customer object comes into existence (first contact) → trigger an onboarding/introduction flow, or create a matching CRM record.

🚧 Object merged from / into

  • Merged into (this object is the surviving profile): trigger a consolidation action, e.g. transferring active journeys/subscriptions from the "disappearing" profile, or a duplicate-cleanup step in an external CRM.

  • Merged from (this object disappears into another): trigger stopping/cancelling any running automations on this profile to avoid duplicate communication.

🚧 Object updated

  • An object changes (e.g. email address, phone number, address) → trigger a sync to an external system (CRM/ESP) or a confirmation message ("your details have changed").

  • An attribute changes to a value that requires action (e.g. status becomes "cancelled") → trigger an exit/cancellation flow.

🚧 Incoming relation created / updated

  • A relation is created towards this object (e.g. a household object gets a new family member linked) → trigger an update of household-wide segmentation or combined communication preferences.

🚧 Outgoing relation created / updated

  • This object creates a relation to another object (e.g. a customer gets linked to a new subscription/asset) → trigger an activation/instruction email for that specific product, or provisioning in an external system.