Custom actions enable you to configure connection of a third-party system to send messages or API calls. An action can be configured with any service from any provider that can be called through a REST API with a JSON-formatted payload.
In Journey Optimizer, you can apply data governance and consent policies to your custom actions to prevent specific fields from being exported to third-party systems or exclude customers who have not consented to receive email, push or SMS communication. For more information, refer to the following pages:
The configuration pane of the Custom action activity shows the URL configuration parameters and the authentication parameters that are configured for the custom action. You cannot set up the static part of the URL in the journey, but in the global configuration of the custom action. Learn more.
If the URL includes a dynamic path, specify the path in the Path field.
To concatenate fields and plain text strings, use the String functions or the Plus sign (+) in the advanced expression editor. Enclose plain text strings in single quotation marks (') or in double quotation marks ("). Learn more.
This table shows an example of configuration:
The concatenated URL has this form:
The URL Configuration section shows the dynamic header fields, but not the constant header fields. Dynamic header fields are HTTP header fields whose value is configured as a variable. Learn more.
If required, specify the value of dynamic header fields:
Select the custom action in the journey.
In the configuration pane, click the pencil icon next to the header field in the URL Configuration section.
Select a field and click OK.
In the Action parameters section, you’ll see the message parameters defined as “Variable”. For these parameters, you can define where to get this information (example: events, data sources), pass values manually or use the advanced expression editor for advanced use cases. Advanced uses cases can be data manipulation and other function usage. Refer to this page.