iHook

iHook is a module that allows the creation of one or more webhook endpoints for inserting panel or activity records in iMIS. Formerly known as iTransfer Webhooks or iTransfer Inbound Transfers, iHook is now accessed entirely through the iWorkflow user interface.

Included Triggers and Actions

The following trigger is available within the iHook module:

• Webhook

The following actiond are available within the iHook module:

• JSON Schema Validation
• Insert Activity
• Insert Panel Record

Calling a Webhook

For information about what types of HTTP requests are accepted by the Webhook trigger, please refer to Webhook.

Webhook Responses

The following are the most common webhook responses:

Status Code	Reason
200	Webhook queued successfully for processing.
202	Alternate of 200 OK for compatibility reasons. Does not support polling at this time.
400	The body was not in JSON format, or the workflow URL is invalid.
401	The webhook URL or token is invalid.
500	A server error occurred. Contact ASI for assistance.

Response Body

By default, the webhook returns a JSON response body (application/json) containing the unique workflow run ID and the queue time. This response can be suppressed by enabling the Omit Response Body option on the webhook trigger.

CORS

Cross-Origin Resource Sharing (CORS) headers are enabled on all webhook endpoints by default. Webhooks can be invoked from JavaScript if desired. For information about CORS headers, see Cross-Origin Resource Sharing.

iTransfer Webhook Analog

To recreate the iTransfer webhook behavior, set up the following workflow:

Trigger: Webhook

• Leave default values set.

Action 1: JSON Schema Validate

• Paste the JSON schema into the schema property of this action.

Action 2: Insert Activity

• Map or hard-code any necessary activity values.

Note: Template syntax has changed - instead of $$propertyName$$, the new syntax is {{ propertyName }}. For more information, please see Template Engine.