Apono outbound webhooks integrations with communications and notifications tools
Loading...
Loading...
Loading...
Create an outgoing webhook in Apono that will send emails to Outlook / Gmail based on Apono access requests using Azure Logic App
An Azure Logic App integration can seamlessly connect with Outlook or Gmail using their respective APIs to send Apono access requests events. By configuring triggers to initiate actions based on specified conditions, the Logic App can efficiently gather the necessary data and format it appropriately for transmission.
Utilizing Azure's secure connectivity and workflow automation capabilities, this integration ensures reliable and timely delivery of event notifications to users' Outlook or Gmail accounts, streamlining communication and enhancing productivity.
An Azure account with subscription (Create an Azure account here).
An Azure workflow Logic App of your choice (Create an Azure logic app here).
In Azure portal search for Logic App and choose the Logic App you want to use.
Under Logic app designer do the following:
Add the following Request Body JSON Schema and save.
As follow:
Press on the + button to add an action and search for Outlook. Under the Gmail API choose Send an email (V2), as follow:
In Send an email (V2) action, configure the "When a HTTP request is received" trigger values by standing on each value input and press on the lightning icon and choose the relevant value as follow and save:
Press on the + button to add an action and search for Gmail. Under the Gmail API choose Send email (V2), as follow:
In Send email (V2) action, configure the "When a HTTP request is received" trigger values by standing on each value input and press on the lightning icon and choose the relevant value as follow and save:
Follow these steps to configure a webhook:
On the Webhooks page, click Add Webhook. The Add Webhook page appears.
Enter a unique, alphanumeric, user-friendly Name for identifying this webhook.
Click the Status toggle to Active.
From the Method dropdown menu, select POST
In the URL field, enter the Workflow URL for the Logic App. This is located on the Overview page in your Azure Portal
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.
From the Triggers dropdown menu, select one or more of the following event triggers, which correspond to Apono access request statuses:
RequestCreated
RequestApproved
RequestRejected
RequestGranted
RequestExpired
RequestFailed
Manual
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.
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 Outlook and Gmail based on the triggers you have selected.
Your webhook should now start sending emails using Azure Logic App to Outlook / Gmail once triggered:
Create an outgoing webhook in Apono that will send messages in a Slack channel based on an Apono access requests
The steps below describe how to create an outgoing webhook in Apono that will allow to automatically send messages in Slack from Apono access requests.
Create a Slack app or use an existing one
Enable incoming webhooks From your Slack app's management dashboard. Select Incoming Webhooks, and toggle Activate Incoming Webhooks to on.
Create an incoming webhook - Now that incoming webhooks are enabled, the settings page should refresh and a button called Add New Webhook to Workspace will appear.
Pick a channel that the app will post to, then select Authorize. If you need to add the incoming webhook to a private channel, you must be a member of that channel.
You'll be sent back to your app settings, where you should see a new entry under the Webhook URLs for Your Workspace section. Your webhook URL will look something like this: https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX
Follow these steps to configure a webhook:
On the Webhooks page, click Add Webhook. The Add Webhook page appears.
Enter a unique, alphanumeric, user-friendly Name for identifying this webhook.
Click the Status toggle to Active.
From the Method dropdown menu, select POST.
In the URL field, enter https//:hooks.slack.com/services/<T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX>.
Be sure to replace <T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX>
with the incoming webhook URL values.
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.
From the Triggers dropdown menu, select one or more of the following event triggers, which correspond to Apono access request statuses:
RequestCreated
RequestApproved
RequestRejected
RequestGranted
RequestExpired
RequestFailed
Manual
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.
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 Slack based on the triggers you have selected.
Your webhook should now start sending messages in the webhook Slack channel once triggered:
Send Apono access requests data to Teams channels triggered by Apono requests events
Microsoft Teams is a collaboration platform by Microsoft that integrates chat, video conferencing, file storage, and application integration for streamlined teamwork.
Leveraging Apono's webhooks solution, you can send requests' data to a dedicated Teams channel as access is requested, granted and revoked.
Teams account with an active Subscription (Create an Teams account here).
Follow these steps to configure a webhook:
On the Webhooks page, click Add Webhook. The Add Webhook page appears.
Enter a unique, alphanumeric, user-friendly Name for identifying this webhook.
Click the Status toggle to Active.
From the Method dropdown menu, select POST.
In the URL field, enter the incoming webhook URL.
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.
From the Triggers dropdown menu, select one or more of the following event triggers, which correspond to Apono access request statuses:
RequestCreated
RequestApproved
RequestRejected
RequestGranted
RequestExpired
RequestFailed
Manual
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.
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 Teams based on the triggers you have selected.
Your webhook should now start sending request event message to your Teams channel once triggered: