Yes. Krokul CRM integrates with Jira. A won deal opens an issue in the Jira project you map to the pipeline, a status change in Jira moves the linked task in Krokul, and worklogs arrive as hours on the client project. You set it up with the Krokul app in Zapier, Make, n8n or Albato, or with the Krokul API and webhooks.
Automation platformsZapierMaken8nAlbato
When a deal reaches a won stage, the connector creates an Issue in the Jira project mapped to that pipeline, with the type you chose. The summary carries the deal title, and the description holds the client company, the amount and a link back to the deal. The Jira issue key is stored next to the Krokul project, so the delivery team and sales talk about the same record.
An account manager creates a task for engineering in Krokul, and the connector opens a matching Issue. Once the issue lands in a status of the Done category, the Krokul task turns done. If the manager closes the task in Krokul first, Krokul runs the Jira transition you mapped to done, so neither side keeps a stale item.
Each Worklog on a linked issue becomes a row of hours on the Krokul project, with the work date and the person. An edited or deleted worklog corrects that entry. The project shows how much of the sold package is used, and the month-end act of work is drafted from those rows.
A client reports a defect, and support records it as a ticket in Krokul with an SLA deadline. Escalation creates a Jira Issue linked to it. When engineering resolves the issue, the ticket moves to resolved, and the client company feed shows when and why.
A Comment on a linked issue appears in the deal feed with the issue key and author. A filter in the connector settings keeps internal remarks in Jira, so sales reads only what can be repeated to the client.
| Jira | Direction | Krokul | When |
|---|---|---|---|
| Issue (delivery) | Krokul → Jira | Won deal and client project | A deal reaches a won stage |
| Issue | Krokul ↔ Jira | Task | A task for engineering is created, or closed in either system |
| Issue status (Done category) | Jira → Krokul | Task status done or cancelled | The issue transitions |
| Issue (escalation) | Krokul ↔ Jira | Ticket | Support escalates a ticket; the issue is resolved |
| Worklog | Jira → Krokul | Hours on the project | A worklog is added, edited or deleted |
| Comment | Jira → Krokul | Comment in the deal feed | A comment passes the connector filter |
Yes. Krokul integrates with Jira through the Krokul app in Zapier, Make, n8n and Albato, and through its API and webhooks.
Jira Cloud. The flow signs in with an Atlassian account and works with the projects that account can see.
Yes. A new worklog adds hours, an edited one updates the row, and a deleted one removes it. Krokul flags the project when its hours budget is exceeded.
No. The issue closes the linked task or ticket. The deal stage stays a sales decision, made in Krokul.
No. Engineers plan and ship in Jira. Krokul shows sales and support the part of that work that concerns the client.
Backlogs, sprints, boards and code links stay in Jira. Krokul keeps the client side of the same work, which means the deal, the task the account manager follows, the support ticket and the hours billed to the client.
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.
Jira is a trademark of Atlassian. Krokul is not affiliated with Atlassian.
