Skip to main content
Create a System Task - Set Up Webhook for Files (in a Project)

This article helps you understand how to create a system task for setting up webhook for files in a project.

Updated this week

Pre-requisites:

  • Privilege for enabling webhooks, assigned to you by the Asite System Administrator.

  • Role privilege 'Manage Workflow Rules' on the project where a system task needs to be created.

The steps to create a system task for setting up a webhook for files in a project are as mentioned below:

1. Follow the steps to create a system task for files in a project (steps 1 to 4).

2. In the task dropdown, select 'Webhook'.

3. When you select the 'Webhook' option, the page expands and enables you to enter related information as described below:

  • Call Back URL: Provide the URL where your webhook will send data. This is typically an endpoint on your server that can handle incoming webhook requests.
    Note: Make sure the URL should be whitelisted in Asite before use. Reach out to your Asite point of contact if required.

  • API Key Name and API Key: If your webhook requires authentication, enter the API key name and its corresponding value. These fields allow you to pass authentication information to the webhook endpoint. Depending on your use case, this is optional.

  • Send API Key In: Choose how to send the API key and values (e.g., as a Request Parameter, in the HTTP header, etc.). By default, HTTP headers will be selected.

  • JSON Text: If your webhook expects specific data in the request body, provide a JSON object with the necessary key-value pairs.

Remember to customize the details according to your specific webhook setup.

4. After configuring the necessary webhook details, click the 'Create' button to create a system task. Your webhook is now ready for use.

You can create independent system tasks which can be executed using workflow triggers without adding them to a complex workflow.

All system tasks are executed automatically according to the conditions outlined in the relevant workflow trigger. The related file audit history and task assignment details indicate that they were performed by the 'Workflow Agent'.



Did this answer your question?