# Google Chat + Krokul CRM

Yes. Krokul CRM integrates with Google Chat. You add the Krokul app to your Google Chat spaces, bind a space to each pipeline, and Krokul posts won deals, stage changes and payments there as cards. Card buttons approve or reject a deal stage in Krokul, and the /krokul command finds a deal or creates a task from the conversation.

**Status:** Via API and webhooks. **Automation platforms:** Zapier, Make, n8n.

## What your team gets

### One space per pipeline, one thread per deal

The projects pipeline posts to the Projects sales space. Every message about a deal carries a thread key built from the deal ID, so the card for the new deal, its stage changes and its payment all line up in one thread of that space. People reply under the card, and the thread reads like the deal history.

### Approve a discount from a card

A deal reaches the stage that needs sign-off. The Krokul app posts a card with the client, amount, discount and two buttons to the approvers space. A click from a linked user moves the deal forward or back in Krokul, writes the decision to the deal feed and updates the card message so it shows who decided.

### Payments for the finance space

When payment.received or invoice.paid fires, the app sends a message to the finance space with the client, amount and invoice number. Finance confirms in the thread. Nobody opens Krokul for a routine check.

### A task from the conversation

A colleague types /krokul task Call the client on Friday in a space. The app opens a dialog with the text, assignee and due date, creates the task in Krokul and replies in the thread with a link to it. A pasted Krokul deal link shows a preview card with stage and amount for people who can see that deal.

## What moves between Google Chat and Krokul

| Google Chat | Krokul | Direction | When |
|---|---|---|---|
| Card message in the pipeline space, thread per deal | Deal created, moved, won or lost | Krokul → Google Chat | The deal event fires |
| Message in the finance space | Payment received; invoice paid in full | Krokul → Google Chat | The payment event fires |
| Card button click (Approve, Reject) | Deal stage and a note in the deal feed | Google Chat → Krokul | A linked user clicks |
| /krokul command and dialog | Task; deal lookup | Google Chat → Krokul | A linked user runs it |
| Link preview card | Deal summary | Krokul → Google Chat | A Krokul link is posted |

## How to connect today

### Krokul app in Zapier, Make or n8n

1. Connect the Krokul app with a Krokul API key.
2. Pair a Krokul trigger such as Deal Won or Payment Received with Create Message on Zapier, Create a Message on Make, or the Google Chat node in n8n.
3. For approvals in n8n, put Send and Wait for Response after the Krokul trigger Deal Stage Changed and finish with the Krokul action Change Deal Stage.
4. On Make, start from Watch Events in a space and use the Krokul action Create Task for messages that ask for follow-up.

### Custom flow through the Krokul API and webhooks

1. Create an incoming webhook in the Google Chat space and keep its URL with the key and token secret.
2. Subscribe a Krokul webhook to card.won, card.statusChanged or payment.received and verify the x-crm-signature header on each delivery.
3. Build the message text from the entity field, add thread.threadKey from the deal UUID and post it to the webhook URL with messageReplyOption=REPLY_MESSAGE_FALLBACK_TO_NEW_THREAD.

**Triggers:** Watch Events.

**Actions:** Create Message; Create a Message; Update a message; Send and Wait for Response; Get a Space.

### For integrators

A Google Chat incoming webhook is one way and posts to the single space it was made in, so buttons and commands need the Krokul Chat app. The Krokul webhook body is event data without ready text, which is why a raw delivery needs a step that writes the message. Each Krokul delivery is signed with HMAC-SHA256 over the timestamp and body. It also carries a delivery ID for deduplication.

[API documentation](https://app.krokul.com/api/v1/docs)

## Questions and answers

### Does Krokul integrate with Google Chat?

Yes. The Krokul app for Google Chat posts deal and payment events to the spaces you bind to pipelines, and the Krokul app in Zapier, Make and n8n covers flows of your own.

### Can I keep all messages about one deal together?

Yes. Krokul uses a thread key per deal, so updates about that deal reply in the same thread of the space.

### Can I use a free Gmail account?

Incoming webhooks need a Business or Enterprise Google Workspace account with Google Chat, and your admin must allow webhooks.

### Who can approve a deal from Google Chat?

People who linked their Google account to a Krokul user. Each click runs with that user’s Krokul rights.

## Limits

Google Chat is where colleagues discuss a deal, and the deal, its amounts and documents stay in Krokul. A Chat user acts in Krokul only after linking a Krokul account, and only with that account’s rights. Google allows incoming webhooks for Business and Enterprise Google Workspace accounts, at one request per second shared by all webhooks of a space.

## Related services

- [Slack](https://krokul.com/en/integrations/slack/index.md)
- [Microsoft Teams](https://krokul.com/en/integrations/microsoft-teams/index.md)
- [Gmail](https://krokul.com/en/integrations/gmail/index.md)
- [Google Meet](https://krokul.com/en/integrations/google-meet/index.md)
- [Google Calendar](https://krokul.com/en/integrations/google-calendar/index.md)

[Team chat](https://krokul.com/en/integrations/category/team-chat/index.md)

Google Chat and Google Workspace are trademarks of Google LLC. Krokul is not affiliated with Google.

Updated: 2026-10-15

---

App: https://app.krokul.com/ · API: https://app.krokul.com/api/v1/docs