Send form submissions to Microsoft Teams

Set it up

1. In Teams, go to the channel that should receive submissions, select More options (...) next to it and choose Workflows.
2. Search for the template Send webhook alerts to a channel, select it, check the team and channel, and save.
3. Copy the webhook link the workflow shows once it is created.
4. In Formward, open the form, go to its Settings tab and scroll to the Connections panel. Choose Webhooks.
5. Pick Microsoft Teams in the type menu, paste the link and click Add webhook. Leave the signing secret empty.
6. Click Test next to the webhook. A card titled "New submission to" followed by your form name should appear in the channel.

What Formward sends to Teams

A message card, with each field as a fact row:

json

Copy{
  "@type": "MessageCard",
  "@context": "https://schema.org/extensions",
  "summary": "New submission to Contact form",
  "themeColor": "00853d",
  "title": "New submission to Contact form",
  "sections": [
    {
      "facts": [
        { "name": "name", "value": "Ada Lovelace" },
        { "name": "email", "value": "ada@example.com" },
        { "name": "message", "value": "Do you ship to Norway?" }
      ]
    }
  ]
}

The card shows up to twelve fields; underscore control fields are left out. When AI summaries are on, the summary is added as the section text.

Plan and limits

• →Webhooks, including the chat formats, need the Professional plan or above. A form can have several webhooks, and each one gets every submission independently.
• →Only submissions that finish processing are sent. Spam is never posted, and neither is a submission that is held because the form's notification address has not been confirmed yet.
• →A delivery succeeds when the endpoint answers 2xx within 10 seconds. A timeout, an error status or a redirect counts as a failure and is retried up to three more times with increasing delays.
• →Every attempt appears in the delivery log on the form's Webhooks settings tab, with the response code and a Replay button for workspace owners and admins.

Where the data goes

Microsoft is a US company. Where a Teams message is stored depends on your own Microsoft 365 tenant, and the workflow itself runs on Power Automate. Treat it as a destination you have to assess as controller.

Formward stores and processes the submission in the EU. Posting it to a chat tool is a second copy that you choose to make, and it then lives under that platform's storage and retention rules. Record the destination in your own records of processing, and keep forms that collect sensitive data away from chat channels: send those to your own endpoint with a generic webhook instead.

Your data-flow page lists every destination each of your forms uses right now.

Troubleshooting

An old Teams webhook URL stopped working

URLs created with the Incoming Webhook connector stopped delivering when Microsoft retired Office 365 connectors in May 2026. Create a new webhook with the Workflows app and replace the URL in Formward.

Deliveries stopped after a colleague left

A workflow belongs to the person who created it, not to the channel. If that account is removed the flow can be switched off. Ask your Microsoft 365 admin to add a co-owner, or recreate the workflow under a shared account.

Nothing appears in a private channel

Microsoft lists posting as the flow bot in private channels as still under development. Point the workflow at a standard or shared channel.

The test works but real submissions never arrive

Open the submission in your inbox and check its status. Spam is never forwarded, and a submission stays held, and undelivered everywhere, while the form's notification address is unconfirmed. Confirm the address from the email Formward sent to it and new submissions flow through.

Related

• Webhooks reference: Delivery rules for every webhook type.
• Slack: If part of your team works in Slack instead.
• Agencies: Route client form submissions to the right channel.
• GDPR for web forms: What to record when submissions go to another tool.

Third-party steps checked against: Microsoft Learn: Create an Incoming Webhook (Workflows); Microsoft 365 Developer Blog: Retirement of Office 365 connectors within Microsoft Teams. Their interfaces change; tell us at hello@formward.eu if a label has moved.