Send FyneDesk notifications to Microsoft Teams

Get a message in your Teams channel every time a ticket is created, commented on, or changes status. FyneDesk sends the event to a webhook, and a short Power Automate flow turns it into a Teams message. Follow the steps below in order — it takes about ten minutes.

How it works

FyneDesk sends each event (new ticket, new comment, and so on) as a small JSON data packet to the URL you provide. Microsoft Teams doesn't display that packet on its own — your Power Automate flow has to take the data and post it as a message.

This is why a test can say "sent successfully" while nothing shows up in Teams: Power Automate replies 202 Accepted the instant it receives a request, so "success" only means Microsoft received the data. It says nothing about whether a message was posted. Once you add the posting step in Part 3, messages will appear.

Before you start

• A Microsoft Teams team and channel where you want the notifications, and a Power Automate account with a licence that can post to Teams.
• Admin access to FyneDesk webhooks, under Admin Settings → Advanced → Webhooks (also reachable via Settings → Connections → Webhooks).
• About ten minutes. You'll build a flow from a ready-made template, paste its URL into FyneDesk, then add one step that posts the message.

Set it up

This is the exact path our team uses, end to end. It produces a simple, readable text message. (Want the message to name each event type, or prefer a formatted card? See the advanced options below.)

Part 1 — Create the flow from a template

Go to make.powerautomate.com and sign in. In the left menu choose Templates, type webhook in the search box, and open Send webhook alerts to a channel — the plain one, not the "(TEST)" versions. Click Continue (sign in again if asked).

The template shows it will connect Teams → Microsoft Teams and generate a webhook URL. Before you click Create, set the Team and Channel you want the notifications posted to — this is easy to miss, and it matters.

Choose your Team and channel, then click Create. When the flow opens, click Edit to start editing it.

Part 2 — Give the URL to FyneDesk

In the flow, click the first box, "When a Teams webhook request is received," and copy the HTTP URL it shows.

Then in FyneDesk, go to Admin Settings → Advanced → Webhooks and click Add webhook:

• Name it something you'll recognise later, e.g. Microsoft Teams.
• Paste the Power Automate URL into Endpoint URL (it must be an HTTPS link).
• Leave ticket.created ticked — that's all you need to start. (You can add more events later.)
• Click Save.

Part 3 — Tell the flow what to post

This is the step that's easy to miss — and it's exactly why a test can say "sent" while nothing appears in Teams.

1. Delete the two prebuilt steps. The template adds an Initialize variable action (sometimes two) and an Attachments is null condition. Delete both — click the … on each step, then Delete. Leaving them in is what triggers the "AdaptiveCard" error.

2. Add the posting action. Click the + under the trigger and choose Post message in a chat or channel (the Microsoft Teams connector). Set the dropdowns:

3. Build the message. Click inside the Message box, click the blue fx (Insert expression) button, paste the expression below exactly, then click Add.

concat('New ticket ', triggerBody()?['data']?['ticket_number'], ' - ', triggerBody()?['data']?['title'], ' | Status: ', triggerBody()?['data']?['status'], ' | Priority: ', triggerBody()?['data']?['priority'], ' | https://app.fynedesk.io/tickets/', string(triggerBody()?['data']?['id']))

4. Save. Click Save (top right). You should see "Your flow is ready to go."

Part 4 — Test

Create or update a real ticket in FyneDesk. A message appears in your Teams channel within a few seconds.

Optional: label every event, or post a card

The expression above always begins with "New ticket". If you'd like the message to name the event (new comment, status change, and so on) or you'd prefer a formatted card, use one of the options below. The setup is identical — only the Message expression changes.

What FyneDesk sends

Your webhook can subscribe to four events. Here's the shape of each packet (values are examples).

ticket.created

{
  "event": "ticket.created",
  "timestamp": "2026-05-30T22:19:59",
  "organization": { "id": 173, "name": "SafePACS" },
  "data": {
    "id": 6381,
    "ticket_number": "INC004736",
    "title": "Printer not working",
    "description": "The 3rd floor printer is offline",
    "status": "New",
    "priority": "Medium",
    "ticket_type": "Incident",
    "source": "Email",
    "created_at": "2026-05-30T22:19:59"
  }
}

ticket.updated and ticket.status_changed use the same shape as above, plus updated_at, assigned_to, and assigned_team_id.

ticket.commented — note that the field names are slightly different here:

{
  "event": "ticket.commented",
  "timestamp": "2026-05-30T22:19:59",
  "organization": { "id": 173, "name": "SafePACS" },
  "data": {
    "ticket_id": 6381,
    "ticket_number": "INC004736",
    "ticket_title": "Printer not working",
    "ticket_status": "New",
    "content": "Any update on this?",
    "comment_id": 8809,
    "is_internal": false
  }
}

Option A — A richer text message

Instead of the single expression, type the layout below in the Message box. Everything that isn't a 〈placeholder〉 is plain text you type. For each 〈placeholder〉, click the fx button, paste the matching expression from the table, then click Add.

〈eventLabel〉  〈ticketNumber〉
〈title〉

Status: 〈status〉   •   Priority: 〈priority〉

〈message〉

Open in FyneDesk: 〈link〉

Option B — A formatted card

Prefer a card? Use the action Post card in a chat or channel and paste the following into the Adaptive Card field. It uses the same expressions, so it's the same data in a tidier layout.

{
  "type": "AdaptiveCard",
  "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
  "version": "1.2",
  "body": [
    {
      "type": "TextBlock",
      "size": "Medium",
      "weight": "Bolder",
      "text": "@{if(equals(triggerBody()?['event'],'ticket.created'),'🎫 New ticket',if(equals(triggerBody()?['event'],'ticket.commented'),'💬 New comment',if(equals(triggerBody()?['event'],'ticket.status_changed'),'🔄 Status changed','✏️ Ticket updated')))} @{triggerBody()?['data']?['ticket_number']}"
    },
    {
      "type": "TextBlock",
      "text": "@{coalesce(triggerBody()?['data']?['title'],triggerBody()?['data']?['ticket_title'],'(no title)')}",
      "wrap": true
    },
    {
      "type": "FactSet",
      "facts": [
        { "title": "Status", "value": "@{coalesce(triggerBody()?['data']?['status'],triggerBody()?['data']?['ticket_status'],'-')}" },
        { "title": "Priority", "value": "@{coalesce(triggerBody()?['data']?['priority'],'-')}" }
      ]
    },
    {
      "type": "TextBlock",
      "text": "@{coalesce(triggerBody()?['data']?['content'],triggerBody()?['data']?['description'],'')}",
      "wrap": true
    }
  ],
  "actions": [
    {
      "type": "Action.OpenUrl",
      "title": "Open in FyneDesk",
      "url": "@{concat('https://app.fynedesk.io/',if(equals(triggerBody()?['data']?['ticket_type'],'Service Request'),'requests/','tickets/'),string(coalesce(triggerBody()?['data']?['id'],triggerBody()?['data']?['ticket_id'])))}"
    }
  ]
}

Troubleshooting

A note on security

Your Power Automate URL contains a secret signature (the sig=... part) — treat the whole URL like a password and don't share it. FyneDesk also signs every request with an X-FyneDesk-Signature header (HMAC-SHA256) if you ever want to verify authenticity inside the flow, though that's optional and not required to get messages flowing.

Frequently asked questions