Overview
Connect Google Chat with Flows360
Google Chat is a messaging app that allows you to send and receive messages, create spaces, and more.
Use the Google Chat connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 6 actions and 2 triggers.
Available actions
- Send a Message
- Get Direct Message Details
- Add a Space Member
- Get Message Details
- Search Messages
- Find Member
Available triggers
- New Message
- New Mention
The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.
Technical guide
Technical reference
Package identity
- Connector: Google Chat
- Package:
@activepieces/piece-googlechat@0.1.7 - Exact artifact digest:
sha256:4705f0eab1d26c00df43138b6c4f723c7992dd3de76a5c967be81323b413eab5 - Runtime: Activepieces-compatible deterministic worker
- Source: the exact reviewed Activepieces source
Authentication
OAUTH2. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.
Action contracts
- Send a Message (
sendAMessage), Send a message to a space or direct conversation. Classification: read. - Get Direct Message Details (
getDirectMessageDetails), Retrieve details of a specific direct message by ID. Classification: read. - Add a Space Member (
addASpaceMember), Add a user to a Google Chat space. Classification: read. - Get Message Details (
getMessageDetails), Retrieve details of a specific message by ID. Supports both system-generated and custom message IDs. Classification: read. - Search Messages (
searchMessages), Search within Chat for messages matching keywords or filters. Classification: read. - Find Member (
findMember), Search space member by email Classification: read.
Trigger contracts
- New Message, webhook.
- New Mention, webhook.
Verification
Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.
Capability summary
Authentication
Authentication method: OAuth 2.0
Required scopes
https://www.googleapis.com/auth/chat.messageshttps://www.googleapis.com/auth/chat.spaceshttps://www.googleapis.com/auth/chat.membershipshttps://www.googleapis.com/auth/cloud-platformhttps://www.googleapis.com/auth/directory.readonlyemail Authentication profiles
connection · oauth2
OAuth scopes: https://www.googleapis.com/auth/chat.messages, https://www.googleapis.com/auth/chat.spaces, https://www.googleapis.com/auth/chat.memberships, https://www.googleapis.com/auth/cloud-platform, https://www.googleapis.com/auth/directory.readonly, email
Supported objects
| Object | Read | Write | Notes |
|---|---|---|---|
| Send a Message | Yes | No | Send a message to a space or direct conversation. |
| Get Direct Message Details | Yes | No | Retrieve details of a specific direct message by ID. |
| Add a Space Member | Yes | No | Add a user to a Google Chat space. |
| Get Message Details | Yes | No | Retrieve details of a specific message by ID. Supports both system-generated and custom message IDs. |
| Search Messages | Yes | No | Search within Chat for messages matching keywords or filters. |
| Find Member | Yes | No | Search space member by email |
| New Message | Yes | No | webhook trigger declared by the pinned package. |
| New Mention | Yes | No | webhook trigger declared by the pinned package. |
Supported actions
Send a Message · Read
Send a message to a space or direct conversation.
send_amessage · Risk: low · Retry: safe
Inputs
spaceId· string · Required, Select a Spacetext· string · Required, The message content to send. Supports basic formatting like *bold*, _italic_, and @mentions.thread· string · Optional, Select a thread to reply to, leave empty for new threadmessageReplyOption· string · Optional, How to handle replies when thread ID is provided.customMessageId· string · Optional, Optional unique ID for this message (auto-generated if empty). Useful for deduplication.isPrivate· boolean · Optional, Send this message privately to a specific user. Requires app authentication.privateMessageViewer· string · Optional, Select the user who can view this private message.
Get Direct Message Details · Read
Retrieve details of a specific direct message by ID.
get_direct_message_details · Risk: low · Retry: safe
Inputs
directMessageId· string · Required, Select a Direct Message
Add a Space Member · Read
Add a user to a Google Chat space.
add_aspace_member · Risk: low · Retry: safe
Inputs
spaceId· string · Required, Select a SpacepersonId· string · Required, Select a person
Get Message Details · Read
Retrieve details of a specific message by ID. Supports both system-generated and custom message IDs.
get_message_details · Risk: low · Retry: safe
Inputs
name· string · Required, The full resource name of the message. Format: spaces/{space}/messages/{message}
Search Messages · Read
Search within Chat for messages matching keywords or filters.
search_messages · Risk: low · Retry: safe
Inputs
spaceId· string · Required, Select a Spacekeyword· string · Required, Search for messages containing this textlimit· number · Optional, Maximum number of messages to return
Find Member · Read
Search space member by email
find_member · Risk: low · Retry: safe
Inputs
spaceId· string · Required, Select a Spaceemail· string · Required, The email address of the member to find
Triggers
New Message · Webhook
Triggers when a new message is received in Google Chat.
Inputs
projectId· stringspaceId· string
New Mention · Webhook
Triggers when a new mention is received in Google Chat.
Inputs
projectId· stringspaceId· stringspaceMemberId· string
Setup
Setup
- Add the Google Chat connector to the workflow in the target Flows360 Studio instance.
- Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
- Provide the connection fields declared by the pinned package:
- No provider credential fields are declared by the pinned package.
OAuth scopes
https://www.googleapis.com/auth/chat.messageshttps://www.googleapis.com/auth/chat.spaceshttps://www.googleapis.com/auth/chat.membershipshttps://www.googleapis.com/auth/cloud-platformhttps://www.googleapis.com/auth/directory.readonlyemail
- Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
- Test the workflow in the appropriate environment before enabling production scheduling or event delivery.
Limitations
Limitations and operational notes
- This content describes
@activepieces/piece-googlechat@0.1.7; provider behaviour can change independently and should be revalidated when the provider or connector version changes. - Only the 6 actions and 2 triggers declared by this pinned package are represented here.
- Tenant credentials and connection values are not stored in the public connector record.
- Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
- Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.
Troubleshooting
Why canu2019t the connector authenticate?
Check the tenant connection in Studio and confirm every required Google Chat connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.
Why is an action or trigger unavailable?
Confirm that the workflow is using @activepieces/piece-googlechat@0.1.7 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.
What should I check after a provider-side change?
Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.