Show Menu
TOPICS×

12.3 Define Custom Actions

In this exercise, you'll create two custom Actions by making use of Journey Orchestration in combination with Adobe Experience Platform.
You'll see the Adobe Experience Cloud homepage.
Click on Journey Orchestration .
Next, you'll see the Journey Orchestration homepage.
In the menu, click on Actions .
You'll then see the Actions list.
You'll define two actions:
  • One action that sends an SMS using an external application, Twilio
  • One action that sends a text to a Slack channel

Action: Send SMS using Twilio

Twilio is a 3rd party provider of SMS Messages. It has an easy-to-use API and we'll use Journey Orchestration to trigger their API.
Click Add to start adding your action.
You'll see an empty Action popup.
As a Name for the Action, use smsTwilioLdap and replace Ldap with your LDAP. In this example, the Action Name is smsTwilioVangeluw .
Set Description to: Send SMS using Twilio .
For the URL Configuration , use this:
  • URL: https://l1uikl5kog.execute-api.us-west-2.amazonaws.com/prod/
  • Method: POST
You don't need to change the Header Fields.
(For transparency, we're using an AWS API Gateway and AWS Lambda function that sits behind the above URL to handle the authentication and sending of SMSs to Twilio.)
Authentication should be set to No Authentication .
For the Message Parameters , you need to define which fields should be sent towards Twilio. Logically, we want Journey Orchestration and Adobe Experience Platform to be the brain of personalization, so the SMS Message Text and the Mobile Number to send the SMS towards should be defined by Journey Orchestration and then sent to Twilio for execution.
So for the Message Parameters , click the Edit Payload icon.
You'll then see an empty popup-window.
Copy the below text and paste it in the empty popup-window.
{
 "body": {
  "textMessage": {
   "toBeMapped": true,
   "dataType": "string",
   "label": "textMessage"
  },
  "to": {
   "toBeMapped": true,
   "dataType": "string",
   "label": "mobileNr"
  }
 }
}

FYI: by specifying the below fields, these fields will become accessible from your Customer Journey and you'll be able to populate them dynamically from the Journey:
"toBeMapped": true,
"dataType": "string",
"label": "textMessage"
You'll then see this:
Click Save .
Scroll up and click Save one more time to save your custom Action.
Your custom Action is now part of the Actions list.
Let's define your second action now.

Action: Send Text to Slack Channel

We'll now use an existing Slack Channel and send messages to that Slack Channel. Slack has an easy-to-use API and we'll use Journey Orchestration to trigger their API.
Click Add to start adding your action.
You'll see an empty Action popup.
As a Name for the Action, use textSlackLdap and replace Ldap with your LDAP. In this example, the Action Name is textSlackVangeluw .
Set Description to: Send Text to Slack .
For the URL Configuration , use this:
  • URL: https://hooks.slack.com/services/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
  • Method: POST
You don't need to change the Header Fields.
Authentication should be set to No Authentication .
For the Message Parameters , you need to define which fields should be sent towards Slack. Logically, we want Journey Orchestration and Adobe Experience Platform to be the brain of personalization, so the text to send to Slack should be defined by Journey Orchestration and then sent to Slack for execution.
So for the Message Parameters , click the Edit Payload icon.
You'll then see an empty popup-window.
Copy the below text and paste it in the empty popup window.
{
 "text": {
  "toBeMapped": true,
  "dataType": "string",
  "label": "textToSlack"
 }
}

FYI: by specifying the below fields, these fields will become accessible from your Customer Journey and you'll be able to populate them dynamically from the Journey:
"toBeMapped": true,
"dataType": "string",
"label": "textToSlack"
You'll then see this:
Click Save .
Scroll up and click Save one more time to save your custom Action.
Your custom Action is now part of the Actions list.
You've defined Events, Data Sources and Actions. Now let's consolidate all of that in one Orchestrated Journey.