# Linear + Krokul CRM

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.

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

## What your team gets

### Every client company is a Linear customer

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 request from a call reaches the product team

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.

### A shipped issue goes back to the account manager

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.

### Tasks for engineers become Linear issues

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`.

### Comments that clients may read

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.

## What moves between Linear and Krokul

| Linear | Krokul | Direction | When |
|---|---|---|---|
| Customer (`customerUpsert`) | Client company | Krokul → Linear | A client company is created or its domain changes |
| Customer Request (`customerNeedCreate`) | Request logged on a deal | Krokul → Linear | A manager logs a product request |
| Issue state (completed) | Comment on each deal with a request and a task for the owner | Linear → Krokul | The issue is completed |
| Issue | Task for the product team | Krokul ↔ Linear | The task is created in Krokul; the issue changes state in Linear |
| Comment | Comment in the deal feed | Linear → Krokul | A comment passes the label filter |
| Issue attachment | Link back to the deal | Krokul → Linear | Together with the request |

## How to connect today

### Krokul app in Zapier, Make, n8n or Albato

1. Connect the Krokul app with a Krokul API key and sign in to Linear.
2. Pair the Krokul trigger Company Created with the Linear action Create Customer.
3. Use the Krokul trigger Task Created with Create Issue, then store the issue ID with the Krokul action Set External Key.
4. For the way back, start from Updated Issue or New Issue Comment and use the Krokul actions Update Task Status or Add Comment.

### Custom flow through the Krokul API and webhooks

1. Create a Krokul API key with scopes for client companies, deals and tasks, and a Linear webhook for Issues, Issue comments and Customer Requests.
2. Subscribe a Krokul webhook to clientCompany.created and task.created, verify x-crm-signature and call customerUpsert or issueCreate at api.linear.app/graphql.
3. Save the Linear IDs on the Krokul records with externalRef/api-upsert.
4. On each Linear delivery, check the Linear-Signature header, resolve the issue ID with externalRef/api-resolve and close the task with task/api-updateStatus.

**Triggers:** New Issue; Updated Issue; New Issue Comment; New Customer; Updated Customer; New Customer Need; New Project Update.

**Actions:** Create Issue; Update Issue; Create Comment; Create Customer; Create Customer Need; Create Issue Attachment; Find Issue by ID; Find Customer by ID.

### For integrators

Linear exposes one GraphQL endpoint and accepts a personal API key or an OAuth2 token, with OAuth2 recommended for apps used by other workspaces. Webhooks carry the actions create, update and remove and are signed with HMAC-SHA256 in `Linear-Signature`. A delivery that takes longer than 5 seconds counts as failed and is retried up to 3 times, so answer fast and process in a queue.

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

## Questions and answers

### Does Krokul integrate with Linear?

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.

### How does Krokul avoid duplicate customers in Linear?

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.

### Can one Linear issue carry requests from several deals?

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.

### Does completing an issue move the deal stage?

No. The deal stage stays a sales decision in Krokul. Completion closes the linked task and tells the account manager.

## Limits

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.

## Related services

- [Jira](https://krokul.com/en/integrations/jira/index.md)
- [GitHub](https://krokul.com/en/integrations/github/index.md)
- [Asana](https://krokul.com/en/integrations/asana/index.md)
- [ClickUp](https://krokul.com/en/integrations/clickup/index.md)
- [Notion](https://krokul.com/en/integrations/notion/index.md)
- [Zendesk](https://krokul.com/en/integrations/zendesk/index.md)

[Projects and tasks](https://krokul.com/en/integrations/category/project-management/index.md)

Linear is a trademark of Linear Orbit, Inc. Krokul is not affiliated with Linear.

Updated: 2026-10-14

---

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