This event executes a job when an HTTP request is received from an external server. This could be information from a website or shop system. When this information is received by Engage, the corresponding job is executed. It is possible to limit the event to requests containing certain information or parameters.

Example HTTP Request

Send the HTTP request to the following address. Replace the email and the password with the correct values. You can add optional parameters to the request (e.g. abcdef, pqrst). When you send the HTTP request, an XML page is returned if the request is successful.

<webdomain>/automated/action.jsp?action=externalRequest&psw=<password>&uemail=<email>&abcdef=value&pqrst=value

Hint:

The designation (C) means contact-related. In general, you only combine contact (C) events with contact (C) jobs. For more information, see ​Contact (C) vs. System (S) Automations​.

General

​Name​

Defines the name of the automation. The name is used to identify the automation in the system. The maximum length is 100 characters.

​Description​

Provides information about the automation. The description makes it easier to identify the automation in the system.

​Event​

Selects the type of event that, when combined with a job, forms the automation. Every time this event occurs, the system executes the dependent job. The job is defined in the ​Edit Event-based Job​ window.

Recommended Automations​

An automation is a combination of an event plus a resulting job. The following combinations are recommended. It is possible to create other combinations, as well, but not all combinations of events and jobs result in meaningful system behavior.

  • External HTTP Request Received (C) + Send Prepared Message to Group (S): This automation sends a prepared message to all group members when the external request is received.

  • External HTTP Request Received (C) + Increase or Decrease Profile Attribute Value (U): This automation increases or decreases a numerical profile attribute when the external request is received.

Define Event​

This area defines the specific parameters of the event.

  • Executor: This input field defines a system user ID. This system user is considered the executor of the HTTP request. (An HTTP request does not actually have an executor ID.) This system user selected here must have the necessary permissions for the resulting job.

  • Source Address: These fields limit the event to requests from a certain source address.

    • Equals: The source address exactly matches the value in the drop-down field.

    • Does Not Equal: The source address does not match the value in the input field.

    • Starts with: The source address starts with the value in the input field.

    • Ends with: The source address ends with the value in the input field

    • Matches [Regex]: The source address matches the regular expression in the input field.

  • Parameters: This button creates three new fields. These fields limit the event by selecting only those requests containing certain parameters. It is possible to add up to 10 parameters. The rules are combined with AND.

    • First field: This input field defines the parameter. You can freely define the parameter in this field according to the parameters transmitted in the incoming request.

    • Second field: This drop-down list defines the relationship between the parameter (first field) and the value (third field).

    • =: The parameter equals the value in the input field (only for numeric, boolean and date values).

    • !=: The parameter does not equal the value in the input field (only for numeric, boolean and date values).

    • >: The parameter is greater than the value in the input field (only for numeric, boolean and date values).

    • <: The parameter is less than the value in the input field (only for numeric, boolean and date values).

    • Equals: The parameter exactly matches the value in the drop-down field.

    • Does Not Equal: The parameter does not match the value in the input field.

    • Starts with: The parameter starts with the value in the input field.

    • Ends with: The parameter ends with the value in the input field

    • Matches [Regex]: The parameter matches the regular expression in the input field.

    • Third field: This input field defines the parameter value.

  • Case Insensitive: This checkbox ignores differences in uppercase and lowercase.

Actions

The following actions are available: