Google Chat n8n integrationAutomate Google Chat with n8n.

Pulls back a single membership record, so a workflow can confirm that a given person still belongs to a space before acting on it.

• Member ID: the membership to retrieve, written in the form spaces/*/members/*, which carries the space and the person in one string. It usually arrives from an earlier node through an expression, the {{ $json.name }} syntax that reads a field off the incoming item.

Lists everyone who belongs to one space and returns a separate item per membership, which makes the result easy to loop over.

• Space Name or ID: the space to inspect, in the form spaces/*. Pick it from the dropdown n8n fills in, or pass an ID with an expression.
• Return All: on, n8n follows the pages of the API until the whole membership list is in; off, Limit caps how many members come back.

Posts a new message into a space and returns its resource name, the value every later operation on that message needs.

• Space Name or ID: where the message lands, in the form spaces/*, for example spaces/AAAAMpdlehY.
• Message: the body itself, where Text holds the content and Request ID makes the call safe to repeat, since a second call with the same request ID returns the existing message instead of posting a duplicate.
• JSON Parameters: switch it on to send the whole object through Message (JSON).

Removes a message from the space for good. Nothing is kept on the n8n side, so a run that deletes at scale should log what it removes first.

• Message Resource Name: the full name of the message, in the format spaces/{space}/messages/{message}. A system-assigned ID looks like spaces/AAAAAAAAAAA/messages/BBBBBBBBBBB.BBBBBBBBBBB, while a custom ID keeps the name chosen at creation.

Reads one message back from Google Chat, which is how a run gets the current text of something it posted earlier, or verifies the message is still there.

• Message Resource Name: the same spaces/{space}/messages/{message} format used by the delete and update calls, so storing that value when the message is created saves a lookup later on.

Posts a message, then holds the execution open until someone in the space answers. The run resumes with that answer in its output, which is the human step inside an otherwise automatic process.

• Space Name or ID and Message: where the question goes and what it asks.
• Response Type: approval for buttons, freeText for a written reply, customForm for a form built with Form Elements.
• Limit Wait Time: caps how long the node waits before the execution moves on.

Rewrites a message that is already in the space instead of posting a second one, so a single thread keeps showing the current state.

• Message Resource Name: the message to rewrite, in the spaces/{space}/messages/{message} format returned when it was created.
• Update Fields: what changes, with Text holding the new content. With JSON Parameters on, Update Fields (JSON) takes the same thing as a JSON object.

Returns the details of one space from its resource name, the quickest way to confirm a space is reachable and to read its display name before anything is posted there.

• Space ID: the resource name of the space, in the form spaces/*. Unlike the message operations, this field is a plain text input rather than a dropdown, so the value has to come from the workflow.

Walks through every space the connected account belongs to and returns one item per space, which is how a workflow discovers where it is allowed to post.

• Return All: on, n8n pages through the API until the list is complete; off, Limit sets the maximum number of spaces returned.