Define the Unique identifier. After you deploy the trigger, this unique identifier registers the trigger on your Control Center. Use only alphanumeric characters. Special characters are not permitted.

If you are running the cloud trigger configuration on multiple computers, you must make sure each computer automatically uses its own unique identifier. To prevent unwanted duplications, insert internal variables as part of the Unique identifier. You can use two internal variables for this purpose:

To insert internal variables to the Unique identifier, click Insert data source and select your internal variables.

Wait for trigger execution to finish: The HTTP protocol requires a receiver (in this case Loftware Automation) to send a numeric response back to the sender indicating the status of the received message. By default, Loftware Automation responds with code 200. This indicates Automation successfully received the data, but gives no information about the success of trigger actions.

This option specifies that a trigger doesn't send a response immediately after receiving the data, but waits until all actions execute. Then, it sends the response code indicating a successful action execution. With this option enabled, you can send back a custom response type and data (e.g., the response to a HTTP request is label preview in PDF format).

With cloud trigger, the relevant built-in Automation standard HTTP response codes are:

	Note
	To send feedback to Automation about the print process, enable synchronous print mode. For more information, see section Synchronous Print Mode.

Response type: Specifies the type of your response message. Frequently used Internet media types (also known as MIME types, or Content-types) are predefined in the drop down box. If your media type is not available in the list, type it yourself. Automation sends the response data outbound as feedback, formatted in the defined media type. Variable enables variable media types. If enabled, select or create a variable that contains media type.

	Note
	If you don't specify the Content-Type, Loftware Automation uses application/octet-stream as a default.

Response data: Defines the content of your response message. Examples of what you can send back as an HTTP response are custom error messages, label previews, generated PDF files, print stream (spool) files, XML files with details from the print engine plus the label preview (encoded as a Base64 string).

If your output consists of binary-only content (such as label preview or print stream), make sure you select a supported media type, e.g. image/jpeg or application/octet-stream.

Additional headers: Allow you to define custom MIME headers for the HTTP response message.

Response header syntax and examples are available in the HTTP Request action section.

	Tip
	With Response data and Additional headers, you can use fixed content, mix of fixed and variable content, or variable content alone. To insert variable content, click the button with an arrow to the right of the data area and insert your variable from the list. You can also create a new variable that contains the data you want to use. For more information, see section Using Compound Values.