# GitHub + Krokul CRM

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.

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

## What your team gets

### A change request becomes an Issue

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.

### Client bug reports counted against the SLA

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.

### A merged Pull Request resolves the request

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.

### Releases noted on the client deal

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.

## What moves between GitHub and Krokul

| GitHub | Krokul | Direction | When |
|---|---|---|---|
| Issue | Task | Krokul → GitHub | A client request is recorded as a task |
| Issue (opened by a client) | Ticket with an SLA deadline | GitHub → Krokul | `issues` event, action `opened` |
| Issue (closed or reopened) | Task status, ticket status | GitHub → Krokul | `issues` event, actions `closed`, `reopened` |
| Pull Request (merged) | Task `done`, ticket `resolved` | GitHub → Krokul | `pull_request` event, action `closed` with `merged: true` |
| Issue comment | Comment on the ticket or deal | GitHub ↔ Krokul | A comment is added on either side and passes the filter |
| Release (published) | Comment on the deal | GitHub → Krokul | `release` event, action `published` |

## How to connect today

### Krokul app in Zapier, Make or n8n

1. Connect the Krokul app with an API key.
2. Pair the Krokul trigger Task Created with the GitHub action Create Issue and Add Labels to Issue.
3. For the way back, use the GitHub trigger Issue Closed or New Release with a Krokul action such as Update Task, Update Ticket or Create Comment.

### Custom flow through the Krokul API and webhooks

1. Create a Krokul API key with scopes for tasks, tickets and activities.
2. Subscribe a Krokul webhook to `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`.
3. Add a repository or organization webhook for `issues`, `issue_comment`, `pull_request` and `release`, with a secret.
4. Check `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`.

**Triggers:** New Issue; Issue Closed; New Pull Request; New Release; New Mention.

**Actions:** Create Issue; Update Issue; Create Comment; Add Labels to Issue; Find or Create an Issue.

### For integrators

Both sides sign webhooks with HMAC-SHA256. GitHub puts the signature in `X-Hub-Signature-256`, and Krokul puts it in `x-crm-signature` over the timestamp and body, with `x-crm-delivery` for deduplication and a delivery log with redelivery. Krokul external keys hold the GitHub issue number for tasks, tickets and projects, so a service resolves the record before it writes. A sandbox company with an API key is one call away.

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

## Questions and answers

### Can I connect GitHub issues to Krokul CRM?

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.

### Which GitHub events does Krokul use?

The main events are `issues` (opened, closed, reopened), `issue_comment`, `pull_request` (closed and merged) and `release` (published).

### Does Krokul read our code?

No. The app asks for access to issues, pull requests and releases in the repositories you choose. Code and diffs stay in GitHub.

### Can a GitHub issue count hours on a Krokul project?

GitHub issues have no time field. Hours come from your time tracker, and Krokul ties them to the ticket that the issue resolved.

### Do I need Zapier for this?

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.

## Limits

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.

## Related services

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

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

GitHub is a trademark of GitHub, Inc. Krokul is not affiliated with GitHub.

Updated: 2026-10-12

---

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