Pro plan. Google Chat works through HTTP steps, which are part of Pro and Agency (and the free trial). Anything you already have keeps working on every plan. See Plans and billing.
How it connects: Google Chat’s incoming webhooks, as Google’s webhook quickstart describes them, for Google Workspace accounts. The body below is Google’s simple text message.
1. Create the webhook in Google Chat
Open the space, click the arrow next to its name, then Apps & integrations > Add webhooks. Name it (for example “Kerux”), save, and copy the URL. It looks likehttps://chat.googleapis.com/v1/spaces/SPACE_ID/messages?key=...&token=... and holds its own key and token: keep it private.
2. Post replies
A contact who replies leaves the campaign (the When the contact replies box). Create a one-step “Replied: tell Google Chat” campaign; in your outreach campaigns, add Send to another campaign to the When the contact replies box and pick it. Its step is a Webhook / HTTP step with no connection:name, text and space). Card messages also work: send Google Chat’s card JSON as the body.
For booked meetings, start a small campaign with the Meeting booked Kerux event and post {{meeting.start}} and {{meeting.title}} the same way.
Test with one contact
In the one-step campaign’s Builder, click Test to open Test on one contact and check the message in the space.Common errors
400 Bad Request
400 Bad Request
The body isn’t a valid Google Chat message. Start from the
text body above.403 or 404
403 or 404
The webhook was deleted, the URL was cut, or your Workspace admin doesn’t allow incoming webhooks. Copy it again or ask the admin.
429 Too Many Requests
429 Too Many Requests
Google limits messages per space. Kerux retries later on its own.