Short answer: Drop the "Google Chat → Reply to Google Chat Thread" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Space Name spaceName | string | Required | Space Name |
Thread Name threadName | string | Required | Thread Name. Example: spaces/AAAA1234/threads/CCCC9012 |
Message Text text | string | Required | Message Text |
{"spaceName": "{{trigger.spaceName}}","threadName": "e.g. spaces/AAAA1234/threads/CCCC9012","text": "{{trigger.text}}"}
{"name": "spaces/AAAA1234/messages/DDDD1357","text": "Replied!","thread": {"name": "spaces/AAAA1234/threads/CCCC9012"}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.