URL configuration concept_gbg_1f1_2gb

When configuring a custom action, you need to define the following URL Configuration parameters:

  1. In the URL field, specify the URL of the external service:

    • If the URL is static, enter the URL in this field.

    • If the URL includes a dynamic path, enter only the static part of the URL, that is, the scheme, the host, the port, and, optionally, a static part of the path.

      Example: https://xxx.yyy.com/somethingstatic/

      You will specify the dynamic path of the URL when adding the custom action to a journey. Learn more.

    note note
    For security reasons, we strongly recommend that you use the HTTPS scheme for the URL. We don’t allow the use of Adobe addresses that are not public and the use of IP addresses.
    Only the default ports are allowed when defining a custom action: 80 for http and 443 for https.
  2. Select the call Method: it can be either POST or PUT.

  3. In the Headers section, define the HTTP headers of the request message to be sent to the external service:

    1. To add a header field, click Add a header field.

    2. Enter the key of the header field.

    3. To set a dynamic value for the key-value pair, select Variable. Otherwise, select Constant.

      For example, for a timestamp, you can set a dynamic value.

    4. If you have selected Constant, then enter the constant value.

      If you have selected Variable, then you will specify this variable when adding the custom action to a journey. Learn more.

    5. To delete a header field, point to the header field and click the Delete icon.

    The Content-Type and Charset header fields are set by default. You cannot modify or delete these fields.

    After you have added the custom action to a journey, you can still add header fields to it if the journey is in draft status. If you do not want the journey to be affected by configuration changes, duplicate the custom action and add the header fields to the new custom action.

    note note
    Headers are validated according to field parsing rules. Learn more.