Webhook step
With the webhook step, you can introduce automation to your approval process management. You can place the webhook step at any stage of the approval path. With the automation plugin, you can alter the page if the approval path reaches the webhook step. Example automation actions upon webhook:
Archive page
Update page
Update content
With the webhook step at the beginning, you could prepare the page for the approval process. With the webhook step at the end of the process, you could transition the page to the next phase. Webhook is an HTTP call. You have to specify a URL and the method (GET/PUT/POST/DELETE). Optionally, you can specify the HTTP body and headers.
We have introduced the Automation Step, which makes the most popular Jira automations like changing issue status, adding/removing labels, or adding comments much simpler, without the need for creating webhooks.
Check out: Automation step
Dynamic Values
Inside URL, headers and body, you can use dynamic values:
You have to put names inside ${…}
Name | Description |
|---|---|
| Project id |
| Page id |
| Approval name |
| Approval id |
Action Type
In case of Approval and Consent types, we expect the HTTP endpoint to return an HTTP code between 200 and 299 inclusive. This will result in the “Approved” step. In case of other response codes or problems with the connection, the step will be marked as “Rejected”.
Notification type will always mark a step as “Approved”, no matter what kind of response we receive or if there is any problem with the connection.