Google Chat
Google Chat space messages and threads
Google Chat (the Workspace messaging product, formerly Hangouts Chat) is the team-chat surface inside Gmail. Tiny Command surfaces one trigger (Message Received — fires when a message lands in any Chat space the connected Workspace user or service account participates in) plus three actions: Send Message (post a new top-level message into a space), Reply to Thread (post a reply inside an existing thread for threaded conversations), List Spaces. The connection uses Google OAuth with the chat.spaces and chat.messages scopes, or a Google Cloud service-account configured as a Chat app (for bot-style workflows). Google Chat's space concept is the org-level container — spaces can be 1:1 DMs, group chats, or named spaces (Slack-channel-equivalents). The trigger fires for all spaces the connected identity is in; filter downstream by spaceId. Reply to Thread requires the thread.name from a prior message — most workflows store the thread name when they post the first message of a thread, then reply into the same thread for subsequent updates.
Workflows start when Google Chat does.
1 real-time trigger, each backed by a webhook subscription. Events arrive within seconds and you don't have to set up polling.
Do anything Google Chat can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| List Google Chat Spaces | Returns spaces the connected user or bot is a member of. Useful for resolving space IDs at workflow setup. |
| Reply to Google Chat Thread | Posts a reply inside an existing thread. For "all updates about this deploy → same thread" patterns that keep noise contained to one conversation. |
| Send Google Chat Message | Posts a new top-level message into a space — text, markdown, or rich Cards. For "weekly summary into team space" or "alert posted to incident channel" workflows. |
Pre-built Google Chat workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Google Chat once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Google Chat field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Google Chat integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Google Chat to Tiny Command?
What Google Chat triggers does Tiny Command support?
What Google Chat actions can I run from a workflow?
Is the Google Chat integration real-time?
Do I need to write code to use Google Chat with Tiny Command?
How much does the Google Chat integration cost?
More communication apps people connect.
Same category as Google Chat, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Google Chat.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
