In Connect, Event-Triggered Messaging Campaigns send messages in response to External Events. An External Event can be anything that happens in another system, such as a purchase or payment transaction, an appointment reminder, or a promotional message. The resulting message is created by the Event-Triggered Campaign, and can be an email, an SMS, or any other kind of message supported by Connect.

Describing External Events

Each External Event is described by a bundle of data that is used to describe the event so that the message can be generated. The data bundle consists of the following:

Customer information, describing the recipient of the message.
The Name and optional Attributes of the Event.
An optional XML document providing further details of the Event.
Optional Attachments to be included with the Event message.
Metadata that helps identify the Event and that controls how it is handled by Connect.

Connect implements an XML dialect, called KXCML, to describe these Events.

Capturing External Events

Connect provides several modules to capture External Events:

The Event Listener, which can receive Event descriptions (in KXCML format) using JMS Message Queues or using SMTP.
The REST API, which can receive Event descriptions in KCXML or JSON format.
The Bulk Data Loader, which can capture Events by importing them into the Connect database tables.