How to integrate Unify with Microsoft Teams

Before connecting

• A Unify Play with a Webhook action
• Access to Teams Workflows and the destination channel
• A workflow owner and permission to use the chosen trigger authentication setting

1. 01

   Choose the receiving channel

   In Teams Workflows, choose Send webhook alerts to a channel. Select the destination and the connection used to post messages.[3]

2. 02

   Check trigger access

   For this example, select Anyone on the Teams webhook trigger. Save and copy the complete callback URL. If organizational policy requires tenant-restricted access, validate that authentication path before proceeding.[4]

3. 03

   Configure the Unify request

   Paste the callback URL into a Unify Webhook action. Use POST, JSON, and authentication None. Start with the fictional Adaptive Card below and inspect Expand preview.[1][2][4]

4. 04

   Inspect delivery and ownership

   Send a controlled record and inspect the workflow run and actual channel card. Replace sample values only after checking the display. Assign a co-owner to maintain the workflow if its creator leaves.[3][5]

{
  "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",
            "text": "Prospect ready for review",
            "weight": "Bolder",
            "wrap": true
          },
          {
            "type": "FactSet",
            "facts": [
              {
                "title": "Name",
                "value": "Alex Morgan"
              },
              {
                "title": "Email",
                "value": "alex@example.com"
              },
              {
                "title": "Company",
                "value": "Example Company"
              },
              {
                "title": "Domain",
                "value": "example.com"
              }
            ]
          },
          {
            "type": "TextBlock",
            "text": "Next step: review account context before follow-up.",
            "wrap": true
          }
        ]
      }
    }
  ]
}

Microsoft Teams expects a card envelope for this workflow. Keep type, attachments, contentType, and the Adaptive Card structure; replace only the fictional prospect values and message copy. The flat payload used by the other webhook articles is not interchangeable with this example. Use the field mapping to distinguish record data from fixed settings. Select available fields in your Play and inspect Expand preview; do not replace configuration values with prospect data.[2][4]

The prospect facts live inside the Adaptive Card’s FactSet. Preserve the envelope and map the values shown in the example. The template posts the card; it does not infer a card from arbitrary prospect keys.