How to integrate Unify with Google Chat
To integrate Unify with Google Chat, send a POST request from a Unify Play to the tool’s configured webhook trigger and map the received fields into the intended action. Use this connection to notify a Google Chat space about a selected prospect.[1][2][3]
- Connection
- Via webhook
- Team collaboration
- Tool
- Google Chat
- Google Chat
- Data flow
- Unify → Google Chat
- JSON payload
At a glance
- Via webhook: Google Chat receives the handoff
- POST request with an explicit JSON contract and destination authentication
- Test scenario: Make missing context visible
When this workflow makes sense
Start with the decision your team needs to make, then choose the connection that supports it.
A team space can be a useful review surface when the alert has a clear purpose. Send only records that need shared attention and state what a teammate should check. Keep the message understandable when one source field is missing.
A good fit when
Teams that want to notify a Google Chat space about a selected prospect and have an owner for the receiving process. The destination account must permit the documented request and the chosen downstream action.
Reconsider the plan when
The receiving team has not agreed how this Google Chat operation should behave when the same record arrives again. Resolve the matching rule before enabling retries.
Design the handoff
Use this framework to agree on the input, the next action, and who owns the result.
Suggested workflow design, based on the documented capabilities below.
| Stage | Decision to make |
|---|---|
| Business decision | Notify a Google Chat space about a selected prospect |
| Receiving contract | Agree which of the 1 example data fields the receiving process actually needs. Set missing-value and identity rules in the field mapping below. |
| Execution boundary | Give one owner access to inspect the Google Chat request and its resulting action. |
| Completion | Decide who can confirm the Google Chat outcome and recover a failed or repeated handoff. Use the completion check below as the acceptance criterion. |
Explore the scenarios
Choose the situation that fits your team and work through the proposed plan.
Open a scenario to explore its plan. Checklists track your selections in this page only.
Notify a Google Chat space about a selected prospect
Start with one controlled record and one intended Google Chat outcome. Keep the test destination separate from live operations.
The receiving owner must distinguish accepted input from completed work. Agree on the evidence required before treating this handoff as successful.
- Prepare the destination using the Google Chat setup checklist
- Resolve the sample fields for one known record and inspect the request before sending it
- Trace that handoff through the receiving operation and compare the actual destination values with the source
Make missing context visible
Make missing context visible: send a test message without a company domain and label the gap rather than showing a broken link. Confirm the reviewer still knows where to investigate.
Decide whether this case should be held for review, corrected, or retried. Make that decision before running Google Chat against live records.
- Isolate the test in a controlled destination and record the starting state
- Run the edge case described above and capture the actual response and destination state
- Recover the record once, then check that recovery did not create unintended additional work
Illustrative workflow, not a preconfigured automation. Complete these checks in your own account.
Define success before launch
Inspect the data and the intended outcome separately. Connection status is only the first check.
Expected, not tested
Notify a Google Chat space about a selected prospect
Inspect the posted message in the intended space and confirm the responsible teammate can identify the next action.
Documentation-based reference. This workflow has not been tested end to end. Use a record or event you control before enabling live activity.
Questions answered
Common decisions when connecting Unify and Google Chat.
Can a teammate reply to control the Unify Play?
This incoming webhook is one-way. It does not process Chat replies or send them back into Unify; interactive behavior requires a separate Chat app.[3]
Limits & decisions
Check these boundaries before designing a live workflow around the connection.
What the connection supports
Understand the connection, the data involved, and the behavior that matters for a Unify + Google Chat workflow.
POST / JSON
| Decision | What to know |
|---|---|
| Unify action | Outbound HTTP request with configurable method, authentication, headers, and body[1] |
| Receiving operation | Choose the receiving Chat space and create an incoming webhook where the Workspace policy permits it. Copy the complete generated URL.[3] |
| Response handling | Webhook response bodies are not available as inputs to later Unify Play actions[2] |
Technical setup reference
References and requirements for the Google Chat connection.
Connection requirements and setup checklist
Before connecting
- A Unify Play with a Webhook action and a controlled record for testing
- Access to the intended Google Chat environment and the permissions required by the cited API or trigger
- The destination identifiers, credentials, and schema used by the request below
- An agreed record identity, duplicate policy, and owner for failed handoffs
Prepare the Google Chat destination
Choose the receiving Chat space and create an incoming webhook where the Workspace policy permits it. Copy the complete generated URL.[3]
Configure the destination action
Send a JSON text message from the Play. Keep the space destination fixed and include the known facts plus one clear review instruction.[3]
Configure the Unify request
Use POST, the endpoint and authentication below, and JSON body format in the Webhook action. Replace setup placeholders, then inspect Expand preview with a controlled record. The receiver must respond within 8 seconds; webhook response bodies are not exposed to later Play steps.[1][2]
Validate the complete handoff
Run the success and edge-case scenarios in Explore the scenarios with a controlled record. Save the request identity and destination evidence, then apply the completion check before enabling live traffic.[3]
Request configuration
- Method
POST- URL pattern
https://chat.googleapis.com/v1/spaces/YOUR_SPACE/messages?key=YOUR_KEY&token=YOUR_TOKEN- Headers
Content-Type: application/json- Authentication
- The incoming webhook URL contains the key and token. Keep it private and ensure the Workspace administrator allows incoming webhooks.
Choose JSON as the body format. Unify sets Content-Type automatically. The receiver must respond within Unify’s 8-second timeout; request responses are not passed to later Play steps.[2]
Replace URL placeholders with the actual receiver URL from your account or deployed application. These example URLs are not working endpoints.
Example handoff payload
Start with a fictional prospect. Validate the resolved values before using a real record.
Inspect the sample payload and field mapping
{
"text": "Review Example Company: Alex Morgan (alex@example.com). Source: Unify."
}Fictional data. Replace sample values before using a real Play.
Illustrative JSON for the documented receiving operation. All prospect values are fictional. Replace credentials, identifiers, schema-specific fields, and fixed example values before a controlled test. Use the field mapping to distinguish record data from fixed settings. Select available fields in your Play and inspect Expand preview; do not replace configuration values with prospect data.[1][2][3]
| Payload field | Value to send |
|---|---|
text | Keep the editorial message template and replace only its fictional person name, email, or company name with available source fields. Preserve JSON escaping. If missing: Remove optional missing context from the message; hold it if the receiving team cannot identify the record. |
text is the visible message body. Use plain text for the initial handoff and keep the URL credentials outside the payload.
Troubleshooting
Start with the stage where the expected data or action stops appearing.
The request is rejected
The incoming webhook URL contains the key and token. Keep it private and ensure the Workspace administrator allows incoming webhooks. Check the receiving account, permissions, endpoint, and required fields against the cited documentation.[3]
The values or destination are wrong
Compare the resolved JSON with the field-by-field contract in Example handoff payload. Check identifiers against the selected Google Chat environment, and distinguish an absent source value from an intentional static value. Fix the mapping before repeating the write.[3]
Receipt does not match the expected result
Find the request in the receiving logs, then inspect the actual Google Chat resource or execution. If the request was accepted but no result exists, investigate the destination failure before retrying. Keep the same logical handoff identity when recovering a repeat.[3]
Sources & review
Official documentation reviewed on September 15, 2026.
Technical claims link to primary documentation from Unify and the destination tool. Scenarios, field choices, and recovery plans are editorial implementation examples. Documentation review is separate from execution testing.
Documentation reviewed; end-to-end execution not tested. No named technical reviewer has signed off on these articles yet.
Content updated: . Report a correction to Unify with the tool name, source URL, and behavior you observed.
Keep exploring
