# Projects and tasks + Krokul CRM

Krokul CRM integrates with Jira, Asana, ClickUp, Trello, Notion, GitHub, Linear and Basecamp. A won deal opens the delivery work in the tool your team uses, a task closed on either side closes on the other, and tracked time arrives as hours on the client project in Krokul. Other task tools connect through the Krokul app in Zapier, Make, n8n, Albato and the API.

## Services

- [Asana](https://krokul.com/en/integrations/asana/index.md) — Via API and webhooks
- [Basecamp](https://krokul.com/en/integrations/basecamp/index.md) — Via API and webhooks
- [ClickUp](https://krokul.com/en/integrations/clickup/index.md) — Via API and webhooks
- [GitHub](https://krokul.com/en/integrations/github/index.md) — Via API and webhooks
- [Jira](https://krokul.com/en/integrations/jira/index.md) — Via API and webhooks
- [Linear](https://krokul.com/en/integrations/linear/index.md) — Via API and webhooks
- [Notion](https://krokul.com/en/integrations/notion/index.md) — Via API and webhooks
- [Trello](https://krokul.com/en/integrations/trello/index.md) — Via API and webhooks

## What your team gets

### Delivery starts the moment sales closes

A deal reaches a won stage and Krokul fires `card.won`. The connector creates an Asana project from your onboarding template, a ClickUp List, a Trello card with your checklist or a Jira issue, named after the deal with a link back. For hour packages Krokul also opens its own project with the hours budget.

### One piece of work, one status

An account manager asks engineering for a change through a Krokul task, which fires `task.created`, and the connector opens a matching item in the tool the team uses. A done status there, or a merged pull request in GitHub, marks the Krokul task done. Closing it in Krokul closes the item. Client bug reports filed in a repository become Krokul tickets with an SLA deadline.

### Tracked time becomes an act of work

Jira worklogs, Asana time entries and ClickUp time entries arrive as hours on the client project, and an edited or deleted entry corrects the same row. At month end Krokul drafts the act of work from those hours, with overage on its own line.

## What to know

Backlogs, sprints, boards, dependencies and code stay in the task tool. Krokul keeps the client side of the same work, which covers the deal, the task the account manager follows, the ticket and the hours billed. A finished work item closes its Krokul record, and the deal stage stays a sales decision in Krokul.

## Questions and answers

### Do custom statuses work?

Yes. You map each status of the task tool to a Krokul task status once, and the connector follows that map in both directions.

### Where do hours come from when the tool has no time field?

From the time tracker your team uses. Trello and GitHub issues have no time field, so hours reach the Krokul project from that tracker.

## Other categories

- [Customer support](https://krokul.com/en/integrations/category/help-desk/index.md)
- [Team chat](https://krokul.com/en/integrations/category/team-chat/index.md)
- [Automation platforms](https://krokul.com/en/integrations/category/automation/index.md)
- [Files and documents](https://krokul.com/en/integrations/category/files-docs/index.md)

Updated: 2026-10-12

---

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