Apono outbound webhooks integrations with IT Service Management tools
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Create ServiceDesk Plus request using an Apono webhook
ServiceDesk Plus is ManageEngine's flagship IT and enterprise service management platform that helps modern enterprises design and deliver critical IT and business services.
Through this integration, you will configure an Apono webhook that creates new request in ServiceDesk Plus when user access requests are created, approved, granted, and revoked, or when requests fail.
ServiceDesk Plus API key and copy the API key to use it later
Follow these steps to configure a webhook:
On the Webhooks page, click Add Webhook. The Add Webhook page appears.
Click Request Webhook.
Enter a unique, alphanumeric, user-friendly Request Webhook Name for identifying this webhook.
Click the Status toggle to Active.
From the Method dropdown menu, select POST.
For the webhook URL, enter http://<SERVER-NAME>:<PORT>/api/v3/requests
The Body Template field expects a JSON structure as appears below. For the full JSON scheme for creating a ticket SEE HERE.
Click View event's payload schema to reveal the payload schema and available data fields. You can also refer to the Webhook Payload Schema Reference to read the descriptions of each data field.
For Headers, use the following Key and Value to set the authorization.
Authorization
authtoken <API-KEY>
From the Triggers dropdown menu, select one or more of the following event triggers, which correspond to Apono access request statuses:
RequestCreated
RequestApproved
RequestExpired
RequestFailed
RequestGranted
RequestRejected
Under Filters, define one or several filter from the listed dropdown menus.
Filters empower admins to control the data transmitted via webhooks, minimizing the amount of data third-party tools receive and reducing unnecessary clutter.
Examples:
Send only production requests to your admins' Slack channel.
Trigger Okta workflows for events from specific integrations or resource types.
Open a ticket in Jira or ServiceNow for manually approved requests.
(Optional) In the Timeout in seconds field, enter the duration in seconds to wait before marking the request as failed.
(Optional) Define Response Validators to verify that the response from the webhook meets specified criteria:
Click + Add. A row of settings appears.
Starting with $.data., enter the Json Path of the JSON parameter.
In the Expected Values field, enter a value and press the Enter key on your keyboard.
Repeat step c to add several expected values.
Repeat steps a-d to add multiple response validators.
Click Test to generate a test event to trigger your webhook. A Test successful or Test failed response status will appear at the bottom of the page. A successful test will send mock data to the target system.
For more information about the test, click View Invocation Data. A panel opens revealing the request, response, and other relevant details.
Should your test fail, view these tips to troubleshoot your webhook.
Click Save Webhook.
The new webhook appears in the Webhooks table. Active webhooks are preceded by a green dot. Inactive webhooks are preceded by a white dot.
Apono access request will be created on ServiceDesk Plus based on the triggers you have selected.
Create Freshdesk tickets using an Apono webhook
Freshdesk is a customer support platform that helps businesses efficiently manage and resolve customer inquiries and issues. It provides tools to streamline customer service processes across various channels, such as email, phone, chat, and social media.
Through this integration, you will configure an Apono webhook that creates new tickets in Freshdesk when user access requests are created, approved, granted, and revoked, or when requests fail.
Freshdesk API Token
Log in to your Freshdesk account.
Click your profile picture > Profile settings
Click View API key.
Freshdesk API URL
Route for creating a ticket in your Freshdesk instance
Example: https://<SUBDOMAIN>.freshdesk.com/api/v2/tickets
Follow these steps to configure an Apono webhook:
On the Webhooks page, click Add Webhook. The Add Webhook page appears.
Click Request Webhook.
Enter a unique, alphanumeric, user-friendly Request Webhook Name for identifying this webhook.
Click the Status toggle to Active.
From the Method dropdown menu, select a REST method.
For the webhook URL, enter https://<SUBDOMAIN>.freshdesk.com/api/v2/tickets.
Be sure to replace <SUBDOMAIN>
with the Freshdesk subdomain for your account.
The webhook URL must adhere to the following requirements:
Uses the HTTPS protocol
Does not specify any custom ports
In the Body Template field, construct a JSON body for the webhook payload.
Click View event's payload schema to reveal the payload schema and available data fields. You can also refer to the Webhook Payload Schema Reference to read the descriptions of each data field.
Under Headers, use the following Key and Value to set the header. Be sure to replace <FRESHDESK_TOKEN>
with a base64-encoded authentication string ({ base64-encoding <api_token>:X}
).
Authorization
Basic <FRESHDESK_TOKEN>
From the Triggers dropdown menu, select RequestCreated.
Under Filters, define one or several filter from the listed dropdown menus.
Filters empower admins to control the data transmitted via webhooks, minimizing the amount of data third-party tools receive and reducing unnecessary clutter.
Examples:
Send only production requests to your admins' Slack channel.
Trigger Okta workflows for events from specific integrations or resource types.
Open a ticket in Jira or ServiceNow for manually approved requests.
(Optional) In the Timeout in seconds field, enter the duration in seconds to wait before marking the request as failed.
(Optional) Define Response Validators to verify that the response from the webhook meets specified criteria:
Click + Add. A row of settings appears.
Starting with $.data., enter the Json Path of the JSON parameter.
In the Expected Values field, enter a value and press the Enter key on your keyboard.
Repeat step c to add several expected values.
Repeat steps a-d to add multiple response validators.
Click Test to generate a test event to trigger your webhook. A Test successful or Test failed response status will appear at the bottom of the page. A successful test will send mock data to the target system.
For more information about the test, click View Invocation Data. A panel opens revealing the request, response, and other relevant details.
Should your test fail, view these tips to troubleshoot your webhook.
Click Save Webhook.
The new webhook appears in the Webhooks table. Active webhooks are preceded by a green dot. Inactive webhooks are preceded by a white dot.
Apono will send a call to Freshdesk to create a new ticket when the RequestCreated
event is triggered.
Create an outgoing webhook in Apono that will allow to automatically create issues in Jira from Apono access requests
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.
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.
A user in Jira to be used by Apono. You'll need the user's email address.
An API token for this user. These credentials will be used to communicate with Jira REST API.
Make sure the user has appropriate permissions to create and update issues in Jira.
What are Jira Basic tokens?
Read more here
Follow these steps to configure an Apono webhook:
On the Webhooks page, click Add Webhook. The Add Webhook page appears.
Click Request Webhook.
Enter a unique, alphanumeric, user-friendly Request Webhook Name for identifying this webhook.
Click the Status toggle to Active.
From the Method dropdown menu, select a REST method.
In the URL field, enter https://<DOMAIN>.atlassian.net/rest/api/3/issue.
Be sure to replace <DOMAIN>
with your Jira domain.
The webhook URL must adhere to the following requirements:
Uses the HTTPS protocol
Does not specify any custom ports
In the Body Template field, construct a JSON body for the webhook payload.
Click View event's payload schema to reveal the payload schema and available data fields. You can also refer to the Webhook Payload Schema Reference to read the descriptions of each data field.
Under Headers, use the following Key and Value to set the headers required by the target system, such as an authorization header.
Authorization
From the Triggers dropdown menu, select one or more of the following event triggers, which correspond to Apono access request statuses:
RequestCreated
RequestApproved
RequestExpired
RequestFailed
RequestGranted
RequestRejected
Under Filters, define one or several filter from the listed dropdown menus.
Filters empower admins to control the data transmitted via webhooks, minimizing the amount of data third-party tools receive and reducing unnecessary clutter.
Examples:
Send only production requests to your admins' Slack channel.
Trigger Okta workflows for events from specific integrations or resource types.
Open a ticket in Jira or ServiceNow for manually approved requests.
(Optional) In the Timeout in seconds field, enter the duration in seconds to wait before marking the request as failed.
(Optional) Define Response Validators to verify that the response from the webhook meets specified criteria:
Click + Add. A row of settings appears.
Starting with $.data., enter the Json Path of the JSON parameter.
In the Expected Values field, enter a value and press the Enter key on your keyboard.
Repeat step c to add several expected values.
Repeat steps a-d to add multiple response validators.
Click Test to generate a test event to trigger your webhook. A Test successful or Test failed response status will appear at the bottom of the page. A successful test will send mock data to the target system.
For more information about the test, click View Invocation Data. A panel opens revealing the request, response, and other relevant details.
Should your test fail, view these tips to troubleshoot your webhook.
Click Save Webhook.
The new webhook appears in the Webhooks table. Active webhooks are preceded by a green dot. Inactive webhooks are preceded by a white dot.
Apono access request logs will be sent to Jira based on the triggers you have selected.
Your webhook should now start creating Jira tickets in the relevant project once triggered:
Create Freshservice tickets using an Apono webhook
Freshservice is an AI-powered, unified IT and employee service management solution that is simple to use and easy to scale. It provides the capabilities required for managing IT services and extends to non-IT teams as well.
Through this integration, you will configure an Apono webhook that creates new tickets in Freshservice when user access requests are created, approved, granted, and revoked, or when requests fail.
Freshservice API key and copy the key to use it later
Follow these steps to configure a webhook:
On the Webhooks page, click Add Webhook. The Add Webhook page appears.
Click Request Webhook.