Yes. Krokul CRM integrates with Slack. You install the Krokul app for Slack in your workspace, bind a Slack channel to each pipeline, and Krokul posts won deals, stage moves and payments there as formatted messages. Buttons in those messages, such as Approve, act back in Krokul, and a slash command creates a task or finds a deal without leaving Slack.
Automation platformsZapierMaken8nAlbato
The wholesale pipeline posts to #sales-wholesale and the projects pipeline to #sales-projects. When a deal is won, the Krokul app sends a channel message with the client, amount, manager and a button that opens the deal. Lost deals can go to a separate channel for the head of sales.
A deal reaches the stage where a discount needs approval. The Krokul app posts a message with the price, the discount and two buttons, Approve and Decline, to the approvers channel. A click moves the deal to the next stage or back, writes the decision to the deal timeline and updates the Slack message so nobody clicks twice.
When a payment arrives or an invoice is covered in full, the app posts to #finance with the client, amount and invoice number. A thread under the message keeps questions about that payment together.
Someone writes in a channel that a client asked for a call back. The message shortcut Create Krokul task opens a short form with the text, the assignee and a due date, and the new task keeps a link back to the Slack message. The slash command /krokul finds a deal by client name and shows its stage and amount.
A colleague pastes a Krokul deal link into a conversation. The Krokul app unfurls it with the client, stage and amount for people who have access to the deal, so colleagues see them without opening Krokul.
| Slack | Direction | Krokul | When |
|---|---|---|---|
| Channel message (Block Kit) in the pipeline channel | Krokul → Slack | Deal won, lost or moved to a stage | The deal event happens |
| Channel message in the finance channel | Krokul → Slack | Payment received; invoice paid in full | The payment event happens |
| Approve or Decline button click | Slack → Krokul | Deal stage and a timeline note | A linked user clicks the button |
| Message shortcut or /krokul command | Slack → Krokul | Task; deal lookup | A linked user runs it |
| Unfurled deal link | Krokul → Slack | Deal summary | A Krokul link is posted in a conversation |
card.won, card.statusChanged or payment.received, and verify the x-crm-signature header on every delivery.entity field of the delivery and post it to the Slack channel, since Slack expects ready text.task/api-create.Yes. Krokul integrates with Slack through the Krokul app in Zapier, Make, n8n and Albato, and through its API and webhooks. The Krokul app for Slack posts deal and payment events to channels you bind to pipelines.
Yes. For stages you mark as needing approval, the message carries Approve and Decline buttons; a click moves the deal and records who decided.
There is no need. Slack incoming webhooks expect a ready message text, and the Krokul app for Slack writes that message and chooses the channel by pipeline.
Only people who linked their Slack account to a Krokul user. Each click runs with the rights of that user, so Slack never gives more access than Krokul does.
Slack is where the team talks about deals; the deal record, amounts and documents stay in Krokul. A Slack user acts in Krokul only after linking a Krokul account, and only with the rights of that account.
Tell us which service you use and what should move between it and Krokul. We reply with the way to do it and when it will be ready.
Request received. We reply to your email.
Slack is a trademark of Slack Technologies, LLC. Krokul is not affiliated with Slack.