Overview

The steps below describe how to create an outgoing webhook in Apono that will allow to automatically create issues in Jira from Apono access requests.

Step-by-step guide

Create Jira ticket triggered by Apono webhook

You can automatically create and resolve issues in Jira via outgoing webhooks. This guide provides example webhook configurations for common use cases, as well as information on how to set up a user in Jira to be used by Apono.

Prerequisites

1. A user in Jira to be used by Apono. You'll need the user's email address.
2. An API token for this user. These credentials will be used to communicate with Jira REST API.
3. Make sure the user has appropriate permissions to create and update issues in Jira.

📘

What are Jira Basic tokens?

Read more here

Creating the webhook

1. In the Apono admin portal, click your avatar at the bottom left corner, click Settings and pick Webhooks

2. Click Add Webhook
3. Fill in the following fields:
4. Method - POST
5. URL

   https://<DOMAIN>.atlassian.net/rest/api/3/issue
   

   Replace <DOMAIN> with your Jira domain.
6. The webhook body:

{
  "fields": {
    "project": {
      "key": "<PROJECT_KEY>"
    },
    "issuetype": {
      "name": "<ISSUE_TYPE_NAME>"
    },
    "summary": "Apono request created: {{ data.friendly_id }}"
  }
}

Replace <PROJECT_KEY> with your Project Key, found in the Jira Project Settings.

Replace <ISSUE_TYPE_NAME> with your the issue name, such as epic, task, story, etc.

This is an example body. You may use other fields according to your needs. See the schema to the right of the screen to learn more about available data fields.

7. Headers:
   1. Authorization header as follows:
      Key: Authorization
      Value: Basic <USERNAME:TOKEN>
      Where: username is the user's email and token is the personal API token required in Prerequisites 1 and 2
      Please note: <USERNAME:TOKEN> must be supplied in base64 encoding.
8. Triggers - you may pick one or more triggers. Triggers correspond to Apono access request statuses:

• Created
• Approved
• Rejected
• Granted
• Expired
• Failed

9. Name - any name of your choosing. This will be displayed in the webhooks table.
10. Status - if you save the webhook as active, it can be triggered immediately. If you prefer, you may also save it as inactive and activate it later.
11. Optional: Test your webhook configuration. You should see Success as the response status.
    Please note: The Test will create a ticket in your Jira project with mock data.

Results

Your webhook should now start creating Jira tickets in the relevant project once triggered: