Yes. Krokul CRM integrates with GitHub. A client request recorded in Krokul opens an issue in the right repository. Issues filed by a client become Krokul tickets with an SLA deadline, and a closed issue or merged pull request resolves the matching task or ticket. Teams wire it with the Krokul app in Zapier, Make or n8n, or with a repository webhook and the Krokul API.
Automation platformsZapierMaken8n
An account manager records a change request as a Krokul task linked to the client deal. The GitHub App opens an Issue in the repository mapped to that client, with the title, due date, a label for such requests and a link back to Krokul. The issue number stays on the task, so both sides point at one record.
Some clients file bugs straight in a shared repository. An Issue opened there from their account becomes a Krokul ticket on the client company, with the response deadline from your SLA settings. Support sees the clock in Krokul, and engineers keep working in GitHub.
When a Pull Request that references the issue is merged, or the issue itself is closed, the linked Krokul task becomes done and the ticket moves to resolved. If someone reopens it, the ticket goes back to in_progress, and the SLA report keeps counting its time.
A published Release in a client repository adds a comment to the client deal with the tag and its link. Sales knows what shipped before the next call, without reading release notes in GitHub.
| GitHub | Direction | Krokul | When |
|---|---|---|---|
| Issue | Krokul → GitHub | Task | A client request is recorded as a task |
| Issue (opened by a client) | GitHub → Krokul | Ticket with an SLA deadline | issues event, action opened |
| Issue (closed or reopened) | GitHub → Krokul | Task status, ticket status | issues event, actions closed, reopened |
| Pull Request (merged) | GitHub → Krokul | Task done, ticket resolved | pull_request event, action closed with merged: true |
| Issue comment | GitHub ↔ Krokul | Comment on the ticket or deal | A comment is added on either side and passes the filter |
| Release (published) | GitHub → Krokul | Comment on the deal | release event, action published |
task.created, verify its x-crm-signature header, open the Issue through the GitHub API and keep the issue number on the task with externalRef/api-upsert.issues, issue_comment, pull_request and release, with a secret.X-Hub-Signature-256, read the event from X-GitHub-Event, and call Krokul routes such as ticket/api-create, ticket/api-update or task/api-updateStatus.Yes. Krokul integrates with GitHub through the Krokul app in Zapier, Make and n8n, and through its API and webhooks. Issues and pull requests stay linked to Krokul tasks and tickets.
The main events are issues (opened, closed, reopened), issue_comment, pull_request (closed and merged) and release (published).
No. The app asks for access to issues, pull requests and releases in the repositories you choose. Code and diffs stay in GitHub.
GitHub issues have no time field. Hours come from your time tracker, and Krokul ties them to the ticket that the issue resolved.
No. A repository webhook with a short service and the Krokul API covers the usual flows. The Krokul app in Zapier, Make or n8n saves you hosting for that service.
Code, branches, reviews and CI stay in GitHub. Krokul reads issue, pull request and release events from the repositories you grant, and keeps the client side of each request, with who asked, by when and what was shipped.
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.
GitHub is a trademark of GitHub, Inc. Krokul is not affiliated with GitHub.