If you’re using a third-party system to send messages or if you want Journey Orchestration to send API calls to a third-party system, this is where you configure its connection to Journey Orchestration. The custom action defined by technical users will then be available in the left palette of your journey, in the Action category (see this page. Here are a few examples of systems that you can connect to with custom actions: Epsilon, Facebook, Adobe.io, Firebase, etc.
Limitations are listed in this page.
In custom action parameters, you can pass a simple collection, as well as a collection of objects. Regarding the limitations, please refer to this page. Also note that the parameters have an expected format (example: string, decimal, etc.). You must be careful to respect these expected formats. Refer to this use case.
Here are the main steps required to configure a custom action:
From the Actions list, click Add to create a new action. The action configuration pane opens on the right side of the screen.
Enter a name for your action.
Do not use spaces or special characters. Do not use more than 30 characters.
Add a description to your action. This step is optional.
The number of journeys that use this action is displayed in the Used in field. You can click the View journeys button to display the list of journeys using this action.
Define the different URL Configuration parameters. See this page.
Configure the Authentication section. This configuration is the same as for data sources. See this section.
Define the Action parameters. See this page.
The custom action is now configured and ready to be used in your journeys. See this page.
When a custom action is used in a journey, most parameters are read-only. You can only modify the Name, Description, URL fields and the Authentication section.