External Adapters: GitHub Issues, Jira, Zapier, n8n, Make, and Custom Code
Build integrations around NOCK-native tickets using the Public API, signed webhooks, and an external mapping layer.
NOCK has one native project-management integration today: Linear. GitHub Issues, Jira, Zapier, n8n, Make, Slack, CRMs, and internal tools can still integrate with NOCK, but they do it through the Public API and signed webhooks rather than built-in NOCK adapters.
This keeps NOCK tickets first-class. External systems can mirror, enrich, or act on tickets without becoming the source of truth for the feedback itself.
Recommended architecture
sequenceDiagram
participant N as NOCK
participant A as Adapter or automation
participant E as External system
N->>A: ticket.created webhook
A->>E: Create external issue or task
A->>A: Store nock_ticket_id + external_id
E-->>A: Status, comment, or workflow event
A->>N: Public API update or customer-visible noteThe adapter can be a no-code workflow, a serverless function, a small backend service, or an AI agent with a scoped API key.
What the adapter should store
Store a small mapping record for every external object you create:
| Field | Why it matters |
|---|---|
nock_ticket_id | Lets the adapter update the original NOCK ticket. |
external_system | Identifies whether the object lives in GitHub, Jira, Slack, a CRM, or another tool. |
external_id | Stores the external issue key, issue ID, task ID, or URL. |
last_nock_delivery_id | Helps prevent duplicate webhook side effects. |
last_synced_at | Makes debugging and reconciliation easier. |
GitHub Issues
There is no native GitHub Issues adapter in NOCK today. To connect GitHub Issues:
- Create a NOCK webhook for
ticket.created. - Receive the webhook in GitHub Actions, a serverless endpoint, n8n, Make, Zapier, or custom code.
- Create a GitHub Issue using the GitHub API.
- Store the NOCK ticket ID in a mapping table, issue body, issue comment, or issue metadata.
- When GitHub changes, call the NOCK Public API to update the ticket or add a customer-visible reply.
Jira
There is no native Jira adapter in NOCK today. Jira can use the same pattern:
- Receive NOCK ticket events through signed webhooks.
- Create or update a Jira issue through Jira automation or the Jira API.
- Store the Jira issue key next to the NOCK ticket ID.
- Translate Jira transitions into NOCK statuses with
PATCH /api/v1/tickets/{id}. - Send useful customer-facing Jira comments back to NOCK as notes when appropriate.
Because Jira workflows vary heavily, start narrow: one NOCK project, one Jira project, and a small status mapping. Add reverse sync only after the one-way flow is stable.
No-code tools
Zapier, n8n, and Make are usually enough for first integrations:
- Use the NOCK Public API when another system should create or update tickets.
- Use NOCK webhooks when another system should react to ticket lifecycle events.
- Add signature verification before workflows trigger sensitive side effects.
- Use webhook delivery IDs for idempotency.
When to build a native adapter later
A native adapter is worth building only when many customers need the same workflow and the integration needs first-class UI, managed credentials, status mapping, logs, retries, and support ownership inside NOCK.
Until then, the API and webhook model is the right default: flexible, cheaper to maintain, and available for every tool.