Google Chat is on our roadmap.
Google Workspace's chat spaces. A native Google Chat connector is not available yet. This page describes what it is designed to do, so you can tell us whether it is the one you need.
- Spaces and threads you grant
- Shared files
- Post in a space or thread
- Request an approval and wait
Questions it should answer.
The plan, not the product. These are the requests a native Google Chat connector is being designed around.
What did the support space raise about the new release?
Post the daily digest to the team space each morning.
Three ways to use Google Chat data today.
None of them is the native connector, and we will not pretend otherwise. But each one works now.
- Remote MCP - if Google Chat offers an MCP server, switch it on for an agent, a prompt or a workflow
- Knowledge bases - upload exports and documents from Google Chat as PDF, CSV or XLSX and ask about them
- Built-in connections - email sending, Pipedrive, ActiveCampaign, Brevo and SQL databases
The rest of this category.
What teams ask about Google Chat.
Can we connect Google Chat today?
Not as a native connector yet. If Google Chat offers an MCP server, add it as a remote MCP server and agents, prompts and workflows can use its tools today. You can also upload exports and documents from Google Chat to a knowledge base, as PDF, CSV or XLSX.
When will it be available?
We do not publish dates for connectors we have not built. Tell us you need it, and what you would ask it first. Real demand decides the order we build in.
What can we connect now?
Email sending through SMTP, Postmark, Resend or SendGrid; Pipedrive, ActiveCampaign and Brevo as a CRM; PostgreSQL, MySQL, MariaDB and SQL Server databases, with an optional SSH bridge; and any remote MCP server.
Tell us what you would ask it first.
We build connectors in the order customers need them. Book a call, name the system and the question, and you will get a straight answer on timing.