If your team runs on Microsoft Teams, you'll want call activity showing up there instead of buried in another app. A native Teams integration isn't built yet, but you can connect dialnote to Teams today using webhooks or Zapier.
Coming soon
A direct Microsoft Teams integration is on our roadmap but isn't available yet. When it ships, you'll be able to post call notifications, AI summaries, and recording links straight to your Teams channels. In the meantime, the workarounds below get the same data into Teams right now.
What it'll do#
When the native integration lands, you'll be able to send missed-call, completed-call, and voicemail alerts to any Teams channel, share AI call summaries and action items after each call, and route notifications from different dialnote numbers to different channels.
Use Teams meetings today#
One Teams feature already works: AI voice agents can book Microsoft Teams meetings. If a Calendly or Cal.com event type uses Teams as its meeting location, your agent's Book Meeting action will create that meeting and share the join link with the caller. See the calendar integrations guide to set that up.
Push call data to Teams now#
You can pipe call events into a Teams channel using either path:
- Custom webhooks — In Teams, add an Incoming Webhook connector to your channel. In dialnote, go to Settings → Webhook Management, add a webhook, and pick one event (each webhook sends a single event type: call logs, call recordings, or notes). You'll need a small middleware layer to reshape dialnote's signed payload into the Teams message-card format. See the webhooks guide.
- Zapier — Connect dialnote in Zapier (your API key lives under Settings → Webhook Management), trigger on
call_logorcall_recording, and use the Microsoft Teams Send Channel Message action.
Heads up
Teams incoming webhooks expect a specific message-card JSON shape. Sending dialnote's raw event payload to a Teams webhook URL won't work — you need a middleware step to transform it. Zapier handles that formatting for you.