Join Activity Format

Joins are a convention of outcomes, but are represented in the journey as activities to make them easier to edit. Multiple outcomes with the same next value, pointing to the same activity, constitutes a join. Joins are used by marketers to to easily join branches back together. This activity type can’t be used in a custom activity.

Journey Specification Format

The activity must be formatted as specified below. The following JSON object is included in the activities array of a journey, as defined in the Journey Specification.

Sample Request

1{
2    "key": "Wait4",
3    "type": "Wait",
4    "configurationArguments": {
5        "waitDuration": 2,
6        "waitUnit": "DAYS"
7    },
8    "outcomes": [
9        {
10            "next": "Email6"
11        }
12    ]
13},
14{
15    "key": "Email5",
16    "type": "EMAILV2",
17    "outcomes": [
18        {
19            "next": "Email6"
20        }
21    ]
22}

Sample Response

1{
2    "key": "Wait4",
3    "type": "Wait",
4    "configurationArguments": {
5        "waitDuration": 2,
6        "waitUnit": "DAYS"
7    },
8    "outcomes": [
9        {
10            "next": "Email6"
11        }
12    ]
13},
14{
15    "key": "Email5",
16    "type": "EMAILV2",
17    "outcomes": [
18        {
19            "next": "Email6"
20        }
21    ]
22}

Related Items

Journey Specification