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 Asite System Administrator.

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

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 system task for files in a project (steps 1 to 4).

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

3. Upon selecting '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. This is optional and depends on your use case.

  • Send API Key In: Choose how you want to send the API key and values (e.g., as a Request Parameter, in 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. Once you have configured the details as applicable, click on 'Create' button to complete creating a system task. Your webhook is now ready to 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 performed by system automatically based on the condition defined in related workflow trigger. It appears in related file audit history & task assignment emails as performed by 'Workflow Agent'.



Did this answer your question?