Integrations · Google Chat
There is no nativeGoogle Chat integration.
We would rather say that here than let you find out during a trial. Answering customers from a Google Chat space is a real need, and there is a real way to do it today — it runs through automation rather than through a Google Chat-shaped connector we have not built.
- 0
- native Google Chat connectorsNo workspace chat tool connector is built, and none is scheduled.
- 17
- events you can act onDelivered to Zapier and to signed webhooks.
- 6
- channels that are nativeSlack · WhatsApp · Microsoft Teams · Zapier · Zoom · SMS
What works today
Reaching Google Chat without a Google Chat connector.
EzyConn publishes 17 event types. Zapier receives them, and Zapier already speaks Google Chat. That is one hop more than a native integration and it is available now.
- 01Post new conversations into a SpaceA Zap can push each new conversation into the Google Chat space your team already watches.via Zapier
- 02Notify on escalationWhen a conversation is handed to a person, send the transcript link to the space.via Zapier
- 03Booking alertsAny of the booking events can post to a space the moment work is confirmed or cancelled.via Zapier
The event contract
What actually leaves the platform.
Generated from the delivery list in the API. An event that is not on it is dropped, so this is the promise rather than a description of one.
- agent.assigned
- agent.unassigned
- booking.cancelled
- booking.completed
- booking.confirmed
- booking.created
- booking.no_show
- booking.reminder_due
- booking.rescheduled
- contact.created
- conversation.closed
- conversation.created
- conversation.updated
- message.received
- message.sent
- order.created
- reservation.created
7 of them cover the booking lifecycle, which is usually the part a workspace chat tool actually wants.
Setting it up
Three steps, no engineering.
Step 01
Create a Zap
Pick EzyConn as the trigger and choose one of the 17 events.Step 02
Choose Google Chat as the action
Zapier handles the Google Chat authentication and field mapping.Step 03
Test it with a real conversation
Every delivery is logged, so a failure is visible rather than silent.
Prefer to skip Zapier? The same events are available as signed webhooks — see the developer docs.
We publish what we have not built.
If a native Google Chat connector is the thing that decides it for you, tell us — that is useful, and it is a better outcome than discovering the gap after you have migrated.