Yes. Krokul CRM integrates with Linear. Each client company in Krokul has a matching Customer in Linear, a product request heard on a deal becomes a Customer Request on a Linear issue with a link back to the deal, and the account manager sees in Krokul when that issue ships. Tasks for the product team turn into Linear issues and close in Krokul when the issue is completed. You connect it through the Krokul app in Zapier, Make, n8n or Albato, or through the Krokul API and webhooks.
Automation platformsZapierMaken8nAlbato
When a client company appears in Krokul, the connector calls customerUpsert with its domains and the Krokul company ID as externalId. Linear merges the record with a customer that already has the same domain. Product managers filter requests by real clients, and no duplicate appears.
A manager hears a feature request on a deal and logs it from the deal card. Krokul finds the matching Linear issue or creates one, then adds a Customer Request with customerNeedCreate, the client as customerExternalId and the deal URL as attachmentUrl. The product team sees who asked. One click opens the deal.
Linear sends an Issue webhook with the action update when the issue moves to a completed state. Krokul looks up the deals that carry a request for that issue and adds a comment with the issue identifier to each of them, plus a task for the owner to tell the client.
An account manager creates a task in Krokul for the product team. The connector opens a Linear Issue in the team you mapped and stores its ID on the task. Completion in Linear sets the Krokul task to done, and cancellation sets it to cancelled.
A Comment on a linked issue appears in the deal feed with its author. A label filter in the connector settings keeps internal threads in Linear.
| Linear | Direction | Krokul | When |
|---|---|---|---|
Customer (customerUpsert) | Krokul → Linear | Client company | A client company is created or its domain changes |
Customer Request (customerNeedCreate) | Krokul → Linear | Request logged on a deal | A manager logs a product request |
| Issue state (completed) | Linear → Krokul | Comment on each deal with a request and a task for the owner | The issue is completed |
| Issue | Krokul ↔ Linear | Task for the product team | The task is created in Krokul; the issue changes state in Linear |
| Comment | Linear → Krokul | Comment in the deal feed | A comment passes the label filter |
| Issue attachment | Krokul → Linear | Link back to the deal | Together with the request |
Yes. Krokul integrates with Linear through the Krokul app in Zapier, Make, n8n and Albato, and through its API and webhooks. Client companies, product requests and engineering tasks stay linked on both sides.
Krokul calls customerUpsert with the company domains and its own ID as the external ID. Linear keeps domains unique and merges a match into the existing customer.
Yes. Each request is a separate Customer Request on the same issue, and each links back to its own deal. When the issue is completed, every one of those deals gets a comment.
No. The deal stage stays a sales decision in Krokul. Completion closes the linked task and tells the account manager.
Linear stays the home of product work. Cycles, projects, triage and roadmaps live there. Krokul keeps the commercial side of the same requests, which means which client asked, on which deal and for what amount.
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.
Linear is a trademark of Linear Orbit, Inc. Krokul is not affiliated with Linear.
