--- title: "Google Chat Integration" description: "Post and manage messages, send interactive card messages, create and configure spaces, and manage space membership in Google Chat as the connected user over the Google Chat API." url: https://flowrunner.ai/integrations/google-chat date_modified: 2026-08-01T02:40:32-07:00 --- # Google Chat [Communication](https://flowrunner.ai/integrations/category/communication-messaging) Post and manage messages, send interactive card messages, create and configure spaces, and manage space membership in Google Chat as the connected user over the Google Chat API. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 14 actions · OAuth · available [Google Chat website](https://chat.google.com/) · [Platform Documentation](https://developers.google.com/workspace/chat/api/reference/rest) · Capability data verified 2026-08-12 1. A procurement agent finishes checking a new vendor request against policy 2. Agent reads the vendor details and the requested spend 3. Agent flags that the spend sits above the auto-approve threshold 4. Agent sends a card message to the procurement space with Approve and Deny buttons 5. Agent updates the card as the decision comes back 6. A procurement lead taps Approve on the card; the agent resumes and creates the vendor record ## What This Integration Enables FlowRunner agents use Google Chat to deliver structured decisions into the spaces Workspace teams already use. An agent can post a text message, send a rich cardsV2 message with buttons for an approval, create a space and seed it with members for a project kickoff, and manage membership as people join or leave. Group chats and direct messages appear in the space list only after their first message, so agents work with spaces the user already touches. The card message is what turns a notification into a decision the agent can act on. ### Without FlowRunner **Approvals in email**: Vendor requests wait in an inbox with no shared view of what is pending **Manual policy checks**: Someone reads each request against the spend policy by hand **No decision trail**: The approval lives in a reply thread nobody can find later ### With FlowRunner **Card in the space**: The request and its options arrive as a card where the team already works **Agent pre-checks policy**: The agent flags only the requests that actually need a human **Captured approval**: Each decision is recorded with who approved it ## Use Case Scenarios ### Card-based vendor approval A procurement agent checks each new vendor request against the spend policy. Requests under the threshold get created automatically. Requests over it get a card message in the procurement space showing the vendor, the requested spend, and the policy line it crosses, with Approve and Deny buttons. A procurement lead taps Approve. The agent creates the vendor record and updates the card to show the decision. Nothing over the threshold is created without that tap. ### Onboarding space setup A workflow reads a roster of new hires. For each cohort, the agent calls Set Up Space to create an onboarding space and add every person as a member in one step, then Send Message to post the first-day checklist. New hires land in a ready space instead of waiting for someone to assemble one. ### Cross-posting a formatted summary When an event fires in another system, the agent composes a summary and calls Send Card Message to post a clean, structured card into the relevant space. For spaces the connected user is not a member of, it uses Send Webhook Message under a bot identity so the update still lands. ## Human-in-Loop Highlight The human-in-loop moment is the card approval. When the procurement agent sees a vendor request above the auto-approve threshold, it does not create the record and it does not silently hold the request forever. It sends a card message into the procurement space that reads: "New vendor Acme requests 8,000 dollars in spend, above the 5,000 dollar auto-approve line. Approve to create, or Deny?" A procurement lead taps a button inside Google Chat. The agent resumes on the tap, creates the vendor record only if approved, and records who decided. The agent screens every request against policy. A person owns the ones that cross the line. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 14 actions ### Spaces 4 - **Create Space** Create a new Google Chat space. Used to open a dedicated space for a project or onboarding cohort. - **Get Space** Retrieve details of a space by resource name. Used to confirm a target space before posting. - **List Spaces** List spaces the connected user belongs to. Used to resolve a space by display name. - **Set Up Space** Create a space and add an initial member list in one step. Used for project kickoff or onboarding. ### Messages 7 - **Delete Message** Delete a message the connected user is allowed to modify. Used to remove a superseded notification. - **Get Message** Fetch a single message by resource name. Used to pull content for downstream processing. - **List Messages** List messages in a space. Used to read recent activity before the agent acts. - **Send Card Message** Post a rich cardsV2 message with headers, buttons, and images. Used to present a structured summary or an approval card in the space. - **Send Message** Post a text message to a space, optionally threaded. Used for status updates and alerts. - **Send Webhook Message** Post to a space through an incoming webhook URL under a bot identity, without using the OAuth connection. Used to reach spaces the user is not a member of. - **Update Message** Edit a message the connected user is allowed to modify. Used to update a status in place, for example to reflect a decision on a card. ### Members 3 - **Add Member** Add a user to a space. Used to enroll a stakeholder during onboarding. - **List Members** List the members of a space. Used to audit membership or drive per-member notification. - **Remove Member** Remove a user from a space. Used during offboarding or access cleanup. ## Frequently Asked Questions ### What can FlowRunner do with Google Chat? FlowRunner agents can run List Spaces, Get Space, and Create Space in Google Chat, plus 11 more actions. ### Does connecting Google Chat to FlowRunner require OAuth? Yes. Google Chat connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials. ### Can Google Chat trigger a FlowRunner workflow automatically? Google Chat doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Google Chat?** This integration exposes Google Chat to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/google-chat. Site index: https://flowrunner.ai/llms.txt