Use of triggers

Use timeouts at the action level. Whenever an action fails or when the timeout is exceeded at the action level, the trigger is re-invoked. By default, the maximum retry count of a trigger is set to 3. You can change this by modifying the ActionsConfiguration setting in Sitecore Content Hub.

To set up the API call action to invoke an Azure Function, use an HttpTrigger Azure Function and specify the URL of the function into the action. You can find this URL in the Azure portal where your Azure Function is deployed.

To validate the connection between Content Hub and the Azure Function, make sure to use the HEAD request header. You can configure this at the function level. When you click Test connection, a HEAD request is sent to the provided URL.

public static async Task HttpResponseMessage Run([HttpTrigger(AuthorizationLevel.Function, "head", "post", Route = null)]HttpRequestMessage req, TraceWriter log)
{
// Allow head request to test connectivity with the Markting Content Hub
 if (req.Method == HttpMethod.Head) return req.CreateResponse(HttpStatusCode.OK);
}

When you select the Azure Service Bus as an action, the message (that is, the detailed event) from Content Hub is put on the Azure Service Bus queue for which connection details have been provided in the action.

Supported methods are GET, PUT and POST. Request headers are passed along for every request. When you use PUT or POST, the request body also contains a detailed overview of the event or message (SaveEntityMessage or DeleteEntityMessage). This is a serialized JSON string: