Short answer: Drop the "Google Chat → Google Chat Message Received" trigger on your workflow canvas, add filters if you want them, and publish. It fires within seconds of the event in Google Chat, not on a polling schedule.
Drop it on the canvas. Configure a couple of fields. Publish.
You don’t need to read this. Tiny Command auto-maps every field into the visual picker so downstream nodes can pull values by clicking. We show it here for power users who want to know what’s on the wire.
{"name": "spaces/AAAA1234/messages/DDDD1357","text": "Hey team!","space": {"name": "spaces/AAAA1234","displayName": "Engineering"},"sender": {"displayName": "John Doe"},"createTime": "2026-04-12T10:00:00Z"}
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| name | string | "spaces/AAAA1234/messages/DDDD1357" |
| text | string | "Hey team!" |
| space | object | { … } |
| space.name | string | "spaces/AAAA1234" |
| space.displayName | string | "Engineering" |
| sender | object | { … } |
| sender.displayName | string | "John Doe" |
| createTime | string | "2026-04-12T10:00:00Z" |
One trigger. 3+ downstream actions. Zero glue.