Step 1
In Google Chat, open the space you want alerts in, click the space name, and choose Apps & integrations → Webhooks → Add webhook.
Integration · Google Chat
Send form submissions to a Google Chat space.

splitforms connects your forms to Google Chat 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 Google Chat is unreachable.
Connecting Google Chat 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 Google Chat routing is configured in the splitforms dashboard against the form's access key — there's no client-side Google Chat-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="[email protected]" required />
<textarea name="message" placeholder="Your message" required></textarea>
<button type="submit">Send to Google Chat</button>
</form>How it works
Here's how to send form submissions to Google Chat in 5 steps — no code required, and most teams finish in a couple of minutes.
In Google Chat, open the space you want alerts in, click the space name, and choose Apps & integrations → Webhooks → Add webhook.
Give it a name (splitforms works well), optionally set an avatar URL, and copy the webhook URL. It starts with https://chat.googleapis.com/v1/spaces/ and carries a key and token in the query string — treat it as a secret.
In splitforms, open your form's Webhooks tab, add a destination, and paste the URL. splitforms recognises the chat.googleapis.com host automatically and switches to Google Chat's message format.
Submit a test entry. The message should land in the space within a couple of seconds, with the form name in bold and each field on its own line.
Repeat per form if you want different forms in different spaces — each form carries its own webhook configuration.
How teams use it
Google Chat spaces accept an incoming webhook that takes the same message body Slack does, so splitforms posts to one directly. Paste the space's webhook URL and submissions arrive as a formatted message — no Zapier, no Apps Script, nothing in between. Prefer a plainer destination? The same form can also send form submissions to email or forward them to any webhook.

Why splitforms
Formspree and Web3Forms have no native Google Chat destination — reaching a space with either means running Zapier or an Apps Script in between. 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
No. Google Chat's incoming webhooks accept a plain JSON body with a text field, which is the same shape Slack uses, so splitforms posts to the space directly. There is no middleware to configure, nothing to keep running, and no per-task quota to hit.
It matches the hostname chat.googleapis.com exactly and switches message format automatically — you do not pick anything. The match is anchored to the host, so a URL that merely mentions that domain in its path or query is not treated as Google Chat.
Yes. The key and token in the query string are what authorise posting to that space, so anyone holding the URL can post to it. Treat it like a password, and delete the webhook in Google Chat if it leaks — that immediately invalidates it.
The form name in bold, then each submitted field on its own line as label and value. Long values are trimmed so a large submission cannot break the message, and any stored file URLs stay clickable.
Yes. Webhook destinations are configured per form, so a contact form, a support form, and a job-application form can each land in their own space.
Usually not — creating a webhook is done by a space manager rather than a Workspace admin. Some organisations restrict who may add apps and webhooks to spaces, in which case ask whoever manages the space. Note that webhooks are a Workspace feature and are not available on personal @gmail.com Chat.
It uses outbound webhooks, so it is included on the paid plans — Pro ($5/month) and Annual ($49/year) — along with the other webhook destinations.
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