Get started with journey activities

Combine the different event, orchestration and action activities to build your multi-step cross-channel scenarios.

Events activities

Events are what trigger a personalized journey, such as an online purchase. Once someone enters a journey, they move through as an individual, and no two individuals are moving along at the same rate or along the same path. When you start your journey with an event, the journey is triggered when the event is received. Each person in the journey then follows, individually, the next steps defined in your journey.

Events configured by the technical user (see this page) are all displayed in the first category of the palette, on the left side of the screen. The following events activities are available:

Start your journey by drag and dropping an event activity. You can also double-click on it.

Orchestration activities

Orchestration activities are different conditions that help determine the next step in the journey. It can be if the person has an open support case or not, the weather forecast at their current location, if they completed a purchase or not, or reached 10 000 loyalty points.

From the palette, on the left-hand side of the screen, the following orchestration activities are available:

Action activities

Actions are what you want to happen as result of some kind of trigger, like sending a message. It is the piece of journey that the customer experiences.

From the palette, on the left-hand side of the screen, below Events and Orchestration, you can find the Actions category. The following action activities are available:

These activities represent the different available communication channels. You can combine them to create a cross-channel scenario.

If you have configured custom actions, they also appear here. Learn more).

Best practices

Most activities allow you to define a Label. This adds a suffix to the name that will appear under your activity in the canvas. This is useful if you use the same activity several times in your journey and want to identify them more easily. It will also make debugging easier in case of errors and it will make reports easier to read. You can also add an optional Description.

When an error occurs in an action or a condition, the journey of an individual stops. The only way to make it continue is to check the box Add an alternative path in case of a timeout or an error. See this section.

On this page