Teams

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.

---

Prerequisites

1. Teams account with an active Subscription (Create an Teams account here).

2. Teams chat to send Apono events to (Create a new Teams channel here).

   1. Add an Incoming Webhook to your Teams channel here

      1. Make sure you copy and save the unique webhook URL you get present in the dialog. The URL maps to the channel and you can use it to send information to Teams.

---

Create a webhook

Follow these steps to configure a webhook:

1. On the Webhooks page, click Add Webhook. The Add Webhook page appears.

2. Click Request Webhook.

3. Enter a unique, alphanumeric, user-friendly Request Webhook Name for identifying this webhook.

4. Click the Status toggle to Active.

5. From the Method dropdown menu, select POST.

6. 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

1. In the Body Template field, construct a JSON body for the webhook payload.

{
      "type":"message",
      "attachments":[
         {
            "contentType":"application/vnd.microsoft.card.adaptive",
            "contentUrl":null,
            "content":{
               "$schema":"http://adaptivecards.io/schemas/adaptive-card.json",
               "type":"AdaptiveCard",
               "version":"1.2",
               "body":[
                  {
                     "type": "TextBlock",
                     "size": "medium",
                     "weight": "bolder",
                     "text": "New {{ event_type }} from {{ data.requester.name }}",
                     "style": "heading",
                     "wrap": true
                  },
                  {
                     "type": "TextBlock",
                     "text": "We are excited to inform you about a new event request that requires your attention",
                     "wrap": true
                  },
                  {
                     "type": "FactSet",
                     "facts": [
                        {
                           "title": "Event Type:",
                           "value": "{{event_type}}"
                        },
                        {
                           "title": "Event Time:",
                           "value": "{{event_time}}"
                        },
                        {
                           "title": "Integration:",
                           "value": "{{data.access_groups.[0].integration.name}}"
                        },
                        {
                           "title": "Requester Name:",
                           "value": "{{data.requester.name}}"
                        },
                        {
                           "title": "Requester Email:",
                           "value": "{{data.requester.email}}"
                        }
                     ]
                  }
               ]
            }
         }
      ]
   }

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.

1. 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

2. 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.

1. (Optional) In the Timeout in seconds field, enter the duration in seconds to wait before marking the request as failed.

2. (Optional) Define Response Validators to verify that the response from the webhook meets specified criteria:

   1. Click + Add. A row of settings appears.

   2. Starting with $.data., enter the Json Path of the JSON parameter.

   3. In the Expected Values field, enter a value and press the Enter key on your keyboard.

   4. Repeat step c to add several expected values.

   5. Repeat steps a-d to add multiple response validators.

3. 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.

1. 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.

---

Results

Your webhook should now start sending request event message to your Teams channel once triggered: