🎉 Celebrate with 10% OFF on All Products! Use Code: GFEX10 Or Buy Any 2+ Items for 30% OFF with Code: GFEX30!
Guides & Tutorials October 23, 2026

How to Post Gravity Forms Submissions to a Google Chat Space as a Card

GravityExtra
How to Post Gravity Forms Submissions to a Google Chat Space as a Card

A new lead that sits unseen in an inbox for three hours is a lost lead. Teams that already live in Google Chat can have the form land where they work: a card in a space, with the name, the plan and a button that opens the entry. This guide shows how to post Gravity Forms submissions to a Google Chat space through an incoming webhook, in card format, with conditional logic and threads. It uses the Gravity Forms Google Chat Premium Add-on, and the steps work with any webhook-based setup that follows Google’s documentation.

Why post a form to a chat space

E-mail notifications are fine for a record, but they are slow and personal: one person gets them, and they scroll away. A space is shared. Everyone in the sales or support space sees the new submission at the same time, can answer in the thread under it, and the message stays in the history of the space. That is useful for three kinds of forms.

  • Leads and quote requests: the first person who sees the card takes it, and the rest of the team can see that it is handled.
  • Support and bug reports: a card with the reporter, the priority and a link to the entry goes straight to the people who can fix it.
  • Bookings and orders: the whole team sees what is coming in, without opening the admin.

Gravity Forms has official add-ons for several chat tools, but none for Google Chat. Google Chat can receive messages from any server through an incoming webhook, so the form only has to build a message in the format Google expects and post it. That is exactly what the add-on does.

What an incoming webhook is

An incoming webhook is a private address for one space. Google documents it in the Chat webhook guide: you send a POST request with a JSON body to https://chat.googleapis.com/v1/spaces/SPACE_ID/messages with a key and a token in the address, and the message appears in the space. There is no sign-in, no Google Cloud project and nothing to approve. The token is what makes the address private, so keep it secret like a password.

A message can be plain text, or it can be a card. Cards are described in the Cards v2 reference: a header with a title and a subtitle, sections, and widgets such as text paragraphs, labelled values and buttons that open a link. A card is much easier to scan than a block of text, which is why this add-on uses cards by default.

What you need before you start

  • A Google Chat space and the right to add a webhook to it. If the Webhooks entry is missing, ask your Workspace administrator.
  • Gravity Forms 2.9 or newer.
  • A form with the fields you want to see in the card.

Step 1: create the webhook

Open the space, open the space menu at the top, choose Apps and integrations, then Webhooks, and add one called Website forms. Copy the address. Create one per space; a webhook belongs to the space where you made it, so a sales space and a support space each need their own.

Step 2: save it once, encrypted

Install the add-on, open Forms, Settings, Google Chat, activate your license and paste the address as the default space. The add-on checks that it is a real Google Chat address, encrypts it with AES-256-GCM before it reaches the database, and from then on shows only the space id and the last four characters of the token. A database backup, an export or a support copy of your site never contains the address in clear text.

The Google Chat settings screen in Gravity Forms: the license box and the default space webhook field, blank, with a hint that an encrypted address is stored and only the space id and the last characters of the token are shown
The add-on settings: one default space. The saved address is encrypted and never shown again.

This is worth a moment of attention. Many setups paste the webhook address into a text box and store it as it is, so anyone with access to a backup can post to your space. Encrypting it costs nothing and removes that risk.

Step 3: build the card

Open the form, go to Settings, Google Chat and add a feed called Sales alert. Leave the webhook blank to use the default space, keep the format on Card, and write the title with merge tags: New {form_title} submission. A subtitle such as Entry #{entry_id} helps people refer to it in the thread.

Under Fields in the card, choose Every field that was filled in for a general alert. Empty fields are left out, so a long form does not turn into a wall of blank rows. For a short, focused alert such as a VIP booking, choose Chosen fields only and tick the name and the plan. Whatever a visitor typed is shown as plain text, so nobody can slip a link or formatting into your space through a form field.

The Google Chat feed editor: space webhook address, card format, title and subtitle with merge tags, chosen fields, the View entry button, an extra button, a custom thread key and conditional logic that posts only for the Premium plan
A feed: where it posts, what the card shows, the buttons, the thread and the condition.

Step 4: add buttons that save a click

The View entry button opens the entry in the WordPress admin. You can add one more button with your own text and an https link, and the link accepts merge tags. A button called Open calendar can point to your booking calendar with the visitor’s name in the address, and a button called Open in CRM can point to a record search. Buttons are the difference between a notification and a workflow step.

Step 5: use threads to keep the space tidy

Threads are optional, but they matter in a busy space. The add-on offers four modes. With one thread per entry, a card to the team and a second message from another feed about the same entry stay together. With one thread per form, every booking lands in the Bookings thread. With a custom key you can group by anything you can write with a merge tag, for example the plan or the city. Under the hood the add-on sends the thread key and the reply option REPLY_MESSAGE_FALLBACK_TO_NEW_THREAD from Google’s guide, so a new key opens a thread and a known key continues it.

Step 6: send different cards to different spaces

A feed can have its own webhook. That lets one form feed several spaces: every submission to the general space, and only the Premium plan to a VIP space, with a different title and fewer fields. Add a second feed, paste the VIP webhook, tick the fields, and turn on conditional logic with the rule Plan is Premium. The list of feeds shows which space each feed uses, with the address masked.

What happens when something goes wrong

A chat post must never break a form. If Google Chat is slow or refuses the message, the visitor still gets the normal confirmation and the entry is saved. The add-on writes a note on the entry that tells you what happened, for example HTTP 404 NOT_FOUND when someone deleted the webhook. It reads only the HTTP code and the status word, because Google states that the text of an error message is not part of the API and may change.

A Gravity Forms entry screen with two notes that say a Google Chat message was posted to a masked space, with the Google message name
Every post is written to the entry as a note, with the space masked.

Google allows one request per second for each space. If several feeds post to the same space at the same moment, one of them may get HTTP 429. The add-on retries quota, busy and server errors up to three times with a growing pause, as the guide recommends, and it never posts the same message twice for the same entry and feed.

Tips for good cards

  • Put the reason first. The title is what shows in the notification on a phone: New booking, Premium plan beats New submission.
  • Show five or six fields, not twenty. The entry link is one click away.
  • Use one space per audience. Sales, support and operations rarely want the same cards.
  • Test with a harmless form first and use a private space with only you in it.
  • If a form holds personal data, think about who is in the space. A chat space is another place where the data lives.

Frequently asked questions

Does it cost anything on the Google side?

Incoming webhooks need no Google Cloud project. Check the terms of your Google Workspace plan for chat features.

Can I use Zapier or Make instead?

Yes, and it works. The difference is that an automation tool adds another account, another monthly fee and another place where your form data passes. A feed add-on posts from your own server straight to Google.

What about Slack, Teams, Discord or Telegram?

GravityExtra has separate add-ons for those, built the same way: one feed per message, merge tags and conditional logic. This one is for Google Chat.

Can the visitor see the card?

No. The message goes to your space only. The visitor sees the normal confirmation of the form.

Summary

To post a Gravity Forms submission to Google Chat you need a webhook address, a feed that builds a card from merge tags and chosen fields, buttons that open the entry or a page, an optional thread and a condition. Keep the address encrypted, send different forms to different spaces and read the entry notes when something does not arrive.

The Gravity Forms Google Chat Premium Add-on does all of this from the form settings, with cards, buttons, threads, conditional logic and an encrypted webhook address. See the features, the price and the setup guide on the add-on page.

See the Google Chat add-on

0
0
Your Cart
Your cart is emptyReturn to Shop
🔥 FREQUENTLY BOUGHT TOGETHER
Complete Combo & Save 40%!
ITEM IN YOUR CART
Gravity Forms Klaviyo Add-on
$39.00/yr
+
🎁 RECOMMENDED ADD-ON SAVE 40% OFF
Original Price: $39.00/yr
Bundle Special Price: $23.40/yr