Microsoft Teams

Connect Microsoft Teams with Webflow to post form submissions, orders, and CMS changes into the Teams channels where your team already works.

→
↗
►
↓
←
↑
Install app
→
↗
►
↓
←
↑
View website
→
↗
►
↓
←
↑
View lesson
→
↗
►
↓
←
↑
A record settings
→
↗
►
↓
←
↑
CNAME record settings
Microsoft Teams

Form submissions on a Webflow site land in site settings and in email notification inboxes. Nobody sees a new demo request in a Microsoft Teams channel unless something moves it there, so a lead can sit unread while the sales channel stays quiet.

Connecting Teams and Webflow sends each submission, order, or CMS event to a chosen channel or chat as it happens. Automation platforms handle the common cases with prebuilt templates. The Webflow Data API and Microsoft Graph cover the reverse direction, where Teams messages create or update CMS items.

Sales reps use this setup to answer inbound leads within minutes, and support or HR teams use it to route each form type to its own department channel. Agencies and developers use the API path to build Teams-based content workflows for client sites.

How to integrate Microsoft Teams with Webflow

What is Microsoft Teams? Microsoft Teams combines chat, audio and video calling, online meetings, and file sharing in one workspace. You can license it inside qualifying Microsoft 365 plans or as a standalone product such as Teams Essentials. Its Workflows app, built on Power Automate, runs automations that post messages to channels and chats.

Microsoft Teams service description on Microsoft Learn

Channel messages put demo requests and new orders in front of the people who act on them. In the other direction, content that starts as a Teams conversation can become a Webflow CMS item without anyone logging in to Webflow.

The Microsoft Teams-Webflow integration supports 4 approaches:

  • Social Intents Live Chat: The Social Intents Marketplace app routes visitor chats from your Webflow site into a Teams channel without code.
  • Code Embed and links: Code Embed elements and buttons put Microsoft Bookings pages and Teams event registration links on your pages.
  • Automation platforms: Zapier, Make, n8n, IFTTT, and viaSocket connect Webflow form, order, and CMS events to Teams messages, and Teams messages back to Webflow items.
  • Webflow and Microsoft APIs: A small server you run gives full control over card formatting and two-way CMS sync, at the cost of writing and hosting code.

Many sites combine two of these methods, such as an automation or webhook for alerts plus the app for live chat.

Install the Social Intents Live Chat app

Microsoft Teams has no official app on the Webflow Marketplace. The closest option is Social Intents Live Chat, a third-party app that lets you chat with website visitors from Microsoft Teams, Slack, Google Chat, and Zoom. Use it when you want real-time conversations with visitors rather than one-way form alerts.

Social Intents Live Chat listing on the Webflow Marketplace

To set up the integration:

  1. Open the Apps panel in Webflow.
  2. Search for Social Intents Live Chat and install it on your site.
  3. Approve the requested scopes, which cover reading the authorized user, reading and writing custom code, and reading site data.
  4. In Social Intents, connect Microsoft Teams and select the Team and Channel that receive chat requests.
  5. Publish your site so the chat widget goes live.

Once connected, every new website chat arrives as a request in the Teams channel you selected, and agents reply to visitors from Teams. The app can also put an AI chatbot trained on your website data in front of visitors, with handoff to a human agent when the bot can't answer. The listing carries the "Approved by Webflow" label, and pricing comes from Social Intents rather than your Webflow plan.

Add Bookings pages and event links with Code Embed elements

Two Microsoft 365 features put Teams meetings on your Webflow pages without any server code. Microsoft Bookings provides an iframe for its booking page and can attach a Teams meeting to each appointment. Teams events provide a registration link you can attach to any button. Neither option embeds a live Teams meeting or chat on the page.

Embed a Microsoft Bookings page

Bookings lets visitors schedule an appointment that comes with its own Teams meeting link when you turn on Add online meeting for the service. Per the Bookings FAQ, Bookings is included in Microsoft 365 Business Basic, Business Standard, Business Premium, Teams Essentials, and several Enterprise plans, and Outlook on the web must be enabled. Adding the iframe uses a Code Embed element, which you can use with a Core, Growth, Agency, or Freelancer Workspace or an active Site plan.

To embed a booking page:

  1. In Bookings, open the Booking page tab and copy the iframe code.
  2. In Webflow, open the Add panel and drag a Code Embed element onto the canvas.
  3. Paste the iframe code, then save and close the modal.
  4. Publish your site, since embedded code doesn't go live until you publish.

Custom code in a Code Embed element can't exceed 50,000 characters, which leaves plenty of room for a Bookings iframe.

Link to a Teams event registration page

Teams now creates webinars and town halls through one events flow, and a public event lets anyone with the registration link join, per Microsoft's Teams events guide. Microsoft documents sharing that link rather than embedding the registration form, so a button on your Webflow event page is the supported path.

To add the registration link:

  1. In Teams, create the event as a public webinar and copy its registration link.
  2. In Webflow, select a Button or Link Block and paste the URL into its link settings.
  3. Publish your site and test the button from a signed-out browser.

Teams live events retired on June 30, 2026, so use webinars or town halls for new events.

Connect with Zapier, Make, or other automation tools

Five automation platforms list both a Webflow connector and a Microsoft Teams connector: Zapier, Make, n8n, IFTTT, and viaSocket. Zapier publishes a ready-made template that will post form submissions to a Teams channel, and viaSocket lists ready-made flows on its Webflow and Teams page.

The table below lists the Webflow and Teams steps each platform exposes for this pairing, in either direction.

PlatformWebflow sideTeams side
ZapierNew Form Submission (instant), New Order, Updated OrderSend Channel Message, Send Chat Message, or Send Bot Message
Zapier (reverse)Create Live ItemNew Channel Mention or New Chat trigger
viaSocketNew Form Submission, New Order, Collection Item CreatedSend Channel Message or Send Chat Message
MakeWatch EventsSend a Message to a channel or chat
IFTTTForm submitted (polling)Post to channel, built yourself since no published Applet pairs the two
n8nItem create or update actionSend and Wait for Response action, used inside a workflow you trigger yourself

Check the account requirements before you build. Zapier's Teams setup guide states that "Microsoft Teams Free accounts are not supported." Make requires a Microsoft business account for its Teams modules. Zapier's form-submission template uses the Send Bot Message action, which requires installing the Zapier app from the Teams Store.

Build with the Webflow and Microsoft Teams APIs

The API path suits developers who need custom Adaptive Cards, form filtering, or Teams-to-CMS sync. It requires server-side code, because Webflow custom code runs only HTML, CSS, and JavaScript in the browser. Placing a Teams webhook URL in client-side code exposes it to every visitor.

These APIs cover the integration:

  • Teams webhook trigger: The Teams webhook trigger, named When a Teams webhook request is received in Workflows, accepts POST requests and posts Adaptive Cards to a channel or chat.
  • Graph channel messages: The Graph send message API posts a message to a channel under a signed-in user's name.
  • Graph change notifications: Message change notifications report new and edited channel messages to an HTTPS endpoint you host.
  • Webflow Data API: The Webflow API reads form submissions and creates CMS collection items on your site.
  • Webflow webhooks: Webflow webhooks push form_submission and other events to your server as they happen.

Office 365 Connectors and the old Incoming Webhook stopped working after Microsoft's May 18 to May 22, 2026 rollout, so build on Workflows or Graph. The Teams webhook trigger runs on the standard Teams connector, and Microsoft's Workflows webhook guide says the templates and trigger don't require a premium license. The generic Power Automate trigger When a HTTP request is received is different: it is a premium trigger, and Microsoft 365 licenses cover standard connectors only, so stick to the Teams webhook trigger unless you already pay for Power Automate Premium.

Post form submissions through a Workflows webhook

This pattern sends each Webflow form submission to a small server function, which reshapes it into a Teams card. The relay is needed because the Webflow payload doesn't match the Teams message envelope. Signing depends on how you create the Webflow webhook: webhooks added in Site settings carry no signature headers, a webhook added from a form's Send to setting shows a secret key once, and a webhook registered through the API with a site token returns a secretKey. Webhooks registered by an OAuth app are signed with that app's client secret.

To implement this:

  1. In Teams, select More options (…) next to the channel, select Workflows, and choose the Send webhook alerts to a channel template. Select Save and copy the webhook URL.
  2. Register a Webflow webhook with a bearer token that has the sites:write scope:
curl -X POST https://api.webflow.com/v2/sites/{site_id}/webhooks \
  -H "Authorization: Bearer $WEBFLOW_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"triggerType":"form_submission","url":"https://your-relay.example.com/","filter":{"name":"Contact Us"}}'
  1. Implement signature and timestamp validation before deploying your relay. This incomplete Cloudflare Workers example shows payload reshaping and posting with the documented Teams envelope, but leaves validation unimplemented:
export default {
  async fetch(request, env, ctx) {
    const raw = await request.text();
    // Validate x-webflow-signature (SHA-256 HMAC) and reject
    // x-webflow-timestamp values older than 5 minutes before continuing.
    const { name, data } = JSON.parse(raw).payload;

    const message = {
      type: "message",
      attachments: [{
        contentType: "application/vnd.microsoft.card.adaptive",
        contentUrl: null,
        content: {
          type: "AdaptiveCard",
          version: "1.2",
          body: [
            { type: "TextBlock", text: `New ${name} submission` },
            { type: "FactSet", facts: Object.entries(data).map(([title, value]) => ({ title, value: String(value) })) }
          ]
        }
      }]
    };

    await fetch(env.TEAMS_WORKFLOW_URL, {
      method: "POST",
      headers: { "Content-Type": "application/json" },
      body: JSON.stringify(message)
    });
    return new Response("ok");
  }
};
  1. Store the Teams URL and the webhook secret as server-side environment variables.

Keep each card under the 28 KB message limit. If your workflow uses the "Anyone" authentication option, don't send an authentication header, or the POST fails. Messages posted this way show the default Workflows bot identity, and Microsoft doesn't support custom bot names or icons for them.

Post as a user with Microsoft Graph

Graph posts a message under a real user's name instead of the Workflows bot. Register an app in Microsoft Entra, record the Application (client) ID, and request the delegated ChannelMessage.Send permission. The only application permission for this endpoint, Teamwork.Migrate.All, is supported for message migration only, so a background service can't use it to post alerts.

To send a channel message:

  1. Acquire a delegated bearer token for the signed-in user.
  2. Call POST https://graph.microsoft.com/v1.0/teams/{team-id}/channels/{channel-id}/messages with Authorization: Bearer {token} and Content-type: application/json.
  3. Send a body such as {"body": {"content": "New demo request from the pricing page"}}, since only body is required.
  4. Read the 201 Created response for the new message object.

Graph supports only the OpenUrl card action, so link buttons work but other card actions need a bot. Microsoft also treats using Teams as a log file as a terms violation, so send only messages people will read.

Sync Teams channel messages into the Webflow CMS

Graph change notifications tell your server when someone posts in a channel, and the Data API turns that post into a CMS item. Use this for announcement feeds, changelogs, or team updates that render on your site in a Collection List.

To implement this:

  1. Create a subscription with POST https://graph.microsoft.com/v1.0/subscriptions. Set resource to /teams/{team-id}/channels/{channel-id}/messages, changeType to created, and notificationUrl to an HTTPS URL. Request the delegated ChannelMessage.Read.All permission.
  2. Add a lifecycleNotificationUrl if expirationDateTime is more than one hour away, and renew the subscription before it expires.
  3. When a basic notification arrives, fetch the message from the notification's resource path. Requesting includeResourceData instead requires an encryptionCertificate.
  4. Create a staged item with POST https://api.webflow.com/v2/collections/{collection_id}/items/insert and a cms:write token. Send {"items":[{"fieldData":{"name":"...","slug":"..."}}]}.
  5. Generate the slug in your code, because Teams messages have no slug field and Webflow requires one.

New items default to isDraft: true, so they stay out of the next site publish until a reviewer sets them live.

What you can build with the Microsoft Teams Webflow integration

Website activity reaches the people who act on it in Teams, without anyone watching form dashboards or email inboxes.

These builds come up most often:

  • Instant demo-request alerts: A demo form on your pricing page posts an Adaptive Card to the sales channel with the visitor's name, company, and email, so a rep replies within minutes.
  • Department routing for every form: Quote requests go to the sales channel and job applications to the recruiting channel, each through its own form filter and workflow.
  • Teams-sourced announcements feed: Team members post in a dedicated channel, and each new post becomes a draft CMS item in a company news Collection List after review.
  • Consultation booking page: A services page embeds a Bookings iframe, and every booked appointment arrives with its own Teams meeting link for the client.

If part of your team works in Slack, send form leads into Slack with the same alert pattern.

Frequently asked questions

  • No. Microsoft Teams has no native Webflow app, so you connect the two through automation tools, a Teams Workflows webhook, or the APIs. For live visitor chat, the third-party Social Intents Live Chat app routes conversations from your site into a Teams channel.

  • No. Microsoft's connector retirement post lists a final rollout from May 18 to May 22, 2026, after which "Office 365 Connectors will no longer function." Move connector-based webhooks to Workflows webhooks. The incoming webhook guide covers the replacement setup.

  • Not for most routes. Zapier doesn't support Teams Free accounts, Make's Teams modules require a Microsoft business account, and Graph's channel message API doesn't support personal Microsoft accounts. Plan on a Microsoft 365 business plan or Teams Essentials.

  • Microsoft lists a Teams MCP server in preview, but its Agent 365 guide says app-specific Microsoft 365 servers are for backward compatibility only and points new projects to Work IQ MCP. On the Webflow side, the Webflow MCP server lets an agent manage CMS content and pages.

  • Any Site plan works, but the free Starter plan caps you at 50 lifetime form submissions. All other Site plans have unlimited submissions, per the form submissions guide. To start building, register a form_submission webhook and point it at your relay.

Microsoft Teams
Microsoft Teams
Joined in

Description

Route Webflow form submissions, orders, and CMS events into Teams channels through Zapier, Make, or Teams Workflows webhooks, and turn Teams messages into CMS items with the Webflow Data API and Microsoft Graph.

→
↗
►
↓
←
↑
Install app

This integration page is provided for informational and convenience purposes only.


Other Office suites integrations

Other Office suites integrations

Google Workspace (G Suite)

Google Workspace (G Suite)

Connect Google Workspace with Webflow to route form submissions into Google Sheets and publish spreadsheet rows as [Webflow CMS](https://help.webflow.com/hc/en-us/articles/33961307099027-Intro-to-the-Webflow-CMS) items.

Office suites
Learn more
Office 365

Office 365

Connect Office 365 with Webflow to send form submissions to Outlook, Excel, SharePoint, and Teams and embed Microsoft Forms and Bookings on your pages.

Office suites
Learn more
Office 365

Office 365

Connect Office 365 with Webflow to embed Microsoft Forms, Bookings pages, and OneDrive files and send form submissions into Outlook, Excel, and Teams.

Office suites
Learn more
Microsoft Excel

Microsoft Excel

Excel has no Webflow app. Move data between the two with embeds, CSV imports, automation platforms, or the Webflow Data API and Microsoft Graph.

Office suites
Learn more
Google Workspace Admin

Google Workspace Admin

Building a custom integration between Google Workspace Admin and Webflow gives you complete control over user provisioning workflows and authentication systems

Office suites
Learn more
G Suite

G Suite

Embed Google Workspace files, formerly G Suite, in Webflow: publish a Doc, Sheet, Slides, or Form to the web, then paste the embed code into a Code Embed element.

Office suites
Learn more

Related integrations

No items found.

Get started for free

Try Webflow for as long as you like with our free Starter plan. Purchase a paid Site plan to publish, host, and unlock additional features.

Get started — it’s free