Step 1
In Microsoft Teams, open Workflows and choose the template that posts to a channel when a webhook request is received, then copy its webhook URL. An existing Incoming Webhook URL also works.
Integration · Microsoft Teams
Send form submissions to Microsoft Teams channels.

splitforms connects your forms to Microsoft Teams and moves every submission across the moment it's received — no manual export, no copy-paste.
Every submission is emailed to you and saved to a searchable dashboard, so the lead is captured even if Microsoft Teams is unreachable.
Connecting Microsoft Teams to your forms is included in your plan — no add-on charge and no per-message billing from splitforms.
Example: form markup
The form posts to https://splitforms.com/api/submit. The Microsoft Teams routing is configured in the splitforms dashboard against the form's access key — there's no client-side Microsoft Teams-specific code in your HTML.
<form action="https://splitforms.com/api/submit" method="POST">
<input type="hidden" name="access_key" value="YOUR_SPLITFORMS_KEY" />
<input type="email" name="email" placeholder="you@example.com" required />
<textarea name="message" placeholder="Your message" required></textarea>
<button type="submit">Send to Microsoft Teams</button>
</form>How it works
Here's how to send form submissions to Microsoft Teams in 6 steps — no code required, and most teams finish in a couple of minutes.
In Microsoft Teams, open Workflows and choose the template that posts to a channel when a webhook request is received, then copy its webhook URL. An existing Incoming Webhook URL also works.
For the Workflows trigger authentication type, choose “Anyone.” splitforms does not send a Microsoft OAuth token, so tenant-user-only trigger modes will reject the delivery.
In splitforms, open your form's Webhooks tab, name the destination “Microsoft Teams,” and paste the Teams webhook URL.
splitforms POSTs an Adaptive Card payload with the form name and each submitted field as a fact row.
Submit a test entry — the card should appear in the Teams channel within a couple of seconds.
Add a co-owner to the Teams Workflow so it does not become orphaned if its original owner leaves.
How teams use it
Use Microsoft Teams Workflows, or an existing Incoming Webhook where your tenant still supports one. Paste the URL into splitforms and submissions arrive as compact Adaptive Cards. Prefer a plainer destination? The same form can also send form submissions to email or forward them to any webhook.

Why splitforms
splitforms is free for 500 submissions (no card), then $5/mo on Pro (5,000/month) or $49/year on Annual (15,000/month), with no per-integration add-on fees.

How SplitForms works
splitforms receives the submission, filters spam, saves it to your dashboard and emails you — then, on paid plans, sends it on to your webhooks and integrations. No backend infrastructure to build.

Point your form to your unique SplitForms endpoint. That's it.

We instantly capture and organize every submission in your inbox.

Send data to email, spreadsheets, CRMs, webhooks, and 7,000+ apps.

No credit card required. Set up in under 60 seconds.
Connect & automate
On paid plans, submissions can also go to Slack, Discord, Google Sheets, Notion, Airtable, Zapier or any signed webhook — and splitforms works on the platforms you build on, from WordPress and Shopify to Next.js. With Stripe connected, your forms can take payments too.

Common questions
Sometimes. Microsoft 365 tenants can restrict the Workflows app, connectors, or who may post to a channel. If you cannot create the webhook workflow, ask your Teams administrator to enable it or create it with you.
Teams Workflow availability and licensing depend on your Microsoft 365 tenant and its policies. splitforms does not add a per-message charge; Microsoft-side licensing is managed in Teams or Power Automate.
Choose Anyone (unauthenticated) for the When a Teams webhook request is received trigger. splitforms sends the Adaptive Card to the signed workflow URL but does not attach a Microsoft OAuth bearer token, so tenant-user and specific-user modes are not compatible.
splitforms sends an Adaptive Card with the form name as the title, each field as a labelled fact row, and the submission timestamp. Long values are bounded so the card stays below Teams' message-size limit; stored file links remain clickable URLs.
Microsoft 365 Connectors are nearing deprecation and Microsoft recommends the Teams Workflows webhook trigger for new setups. splitforms sends the same supported Adaptive Card envelope to existing Teams webhook URLs and to a Teams Workflow when the webhook is labelled “Microsoft Teams.”
Yes. Each form in splitforms has its own webhook configuration, so you can configure one Incoming Webhook URL per form and route distinct contact, support, and HR forms into separate Teams channels.
Microsoft Teams delivery uses outbound webhooks, so it is included on the paid plans: Pro ($5/month) and Annual ($49/year).
Simple pricing
Free gives you 500 submissions for $0 — no card, no time limit. Pro is $5/month for 5,000 submissions a month, and Annual is $49/year for 15,000 a month with every Pro feature.
For side projects and indie devs.
Every paid feature, for agencies and growing products.
Every Pro feature with triple the volume — $0.27 per 1,000 at full use.
No credit card required on Free • Cancel anytime • Full pricing and FAQ