Microsoft Teams

Datafly Signal posts events to a Microsoft Teams channel as MessageCard notifications using a per-channel Incoming Webhook. Useful for routing operational alerts, lead notifications, and high-value order events to the team that owns them.

Prerequisites

Before configuring Microsoft Teams in Signal you need:

• A Microsoft Teams team that you can administer.
• A target channel (one webhook per channel — split traffic by creating multiple Signal integrations, each pointing at a different channel).
• Permission to add connectors to the channel.

Get your credentials

Step 1: Add an Incoming Webhook connector to your channel

1. In Microsoft Teams, open the channel you want to post to.
2. Click the … menu next to the channel name and choose Connectors.
3. Find Incoming Webhook in the connector list and click Configure (or Add, then Configure).
4. Give the webhook a recognisable name (e.g. Datafly Signal Alerts).
5. Optionally upload an icon — this becomes the avatar of every notification.
6. Click Create.

Step 2: Copy the webhook URL

Teams now displays the webhook URL. It looks like:

https://yourorg.webhook.office.com/webhookb2/<guid>@<tenant>/IncomingWebhook/<connector>/<user>

7. Click Done to finish.

Configure in Signal

Configuration fields

Management UI setup

1. Go to Integrations > Add Integration > Microsoft Teams.
2. Paste the webhook_url into the webhook_url field.
3. Select the General preset (the default for this integration).
4. Leave consent categories at the default (essential) — Teams notifications are operational, not marketing.
5. Click Save.

Management API setup

curl -X POST http://localhost:8084/v1/admin/integrations \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "source_id": "src_abc123",
    "vendor": "microsoft_teams",
    "name": "Teams - Sales Alerts",
    "enabled": true,
    "config": {
      "webhook_url": "https://yourorg.webhook.office.com/webhookb2/..."
    },
    "consent_categories": ["essential"]
  }'

API endpoint

POST {webhook_url}
Content-Type: application/json

Signal posts a MessageCard JSON document to the URL. Microsoft Teams renders the card directly in the target channel.

Event mapping

General preset

To customise the card text, summary, or theme colour, edit the integration’s field mappings in the Management UI. Every event renders as a MessageCard with these top-level fields:

Example: Order Completed

Datafly.js call:

datafly.track("Order Completed", {
  order_id: "ORD-001",
  total: 129.99,
  currency: "USD"
});

Teams payload sent by Signal:

{
  "@type": "MessageCard",
  "@context": "http://schema.org/extensions",
  "themeColor": "0076D7",
  "summary": "Order completed",
  "title": "Order completed",
  "text": "ORD-001"
}

Teams renders this as a card in the channel with the title, body text, and configured theme colour.

Splitting events across channels

Each Incoming Webhook posts to exactly one channel. To route different event classes to different channels (sales channel for leads, ops channel for failures), create one Signal integration per channel:

1. Configure an Incoming Webhook on each target channel and copy each URL.
2. Add multiple Microsoft Teams integrations in Signal, each with its own webhook_url and its own enabled event list.
3. Use the pipeline event filter to restrict which events reach each integration.

Identity

Signal sends no identity data to Microsoft Teams. The MessageCard contains only the event title and the property values you explicitly map. Personal data, IP address, user agent, and identifier cookies are all stripped before delivery. This is deliberate — Teams notifications are operational signals and should not leak PII into a chat channel.

If you need to include a customer name or order ID in the card, map only the specific property you need (e.g. properties.order_id) rather than passing the full property bag.

Consent

The default consent category is essential. Microsoft Teams notifications are treated as operational signalling, not marketing, so they fire regardless of the visitor’s marketing consent state. This matches how most legal teams classify internal team alerting.

If your data-governance policy requires this integration to honour marketing or analytics consent, change the consent category in the Management UI.

Verify it’s working

Step 1: Trigger a test event

From a page running Datafly.js:

datafly.track("Lead Submitted", {
  lead_type: "Test from Signal"
});

Step 2: Check the Teams channel

Within a few seconds, a card titled New lead submitted with body Test from Signal should appear in the channel.

Step 3: Inspect the Signal event debugger

In the Signal Management UI, open the integration’s Recent Events tab. You should see the event with a 2xx response and the full MessageCard payload that was posted.

Troubleshooting

See also

• Microsoft Teams Incoming Webhooks docs
• MessageCard reference
• PagerDuty integration — for paging on-call rotations instead of chat notifications