Automation Examples: Zapier, n8n, Make, GitHub Issues, and Jira

You do not need a native integration for every tool. The Public API and webhooks are enough to connect NOCK to most automation platforms and to build external adapters for issue trackers.

Zapier: create a NOCK ticket

1. Create a Zap with your preferred trigger.
2. Add Webhooks by Zapier.
3. Choose Custom Request.
4. Method: POST.
5. URL: https://nocknock.cloud/api/v1/tickets.
6. Headers:
   • Authorization: Bearer <NOCK_API_KEY>
   • Content-Type: application/json
7. Body:

{
  "project_id": "NOCK_PROJECT_ID",
  "title": "New support escalation",
  "description": "Map the incoming support message here.",
  "reporter_email": "customer@example.com",
  "category": "bug",
  "page_url": "https://example.com/support"
}

Zapier: receive NOCK events

1. Create a Zap with Webhooks by Zapier -> Catch Hook.
2. Copy the Catch Hook URL.
3. Create a NOCK webhook endpoint with that URL.
4. Select the events your Zap should receive.
5. Add a Code step if the workflow triggers side effects and you need signature verification.

n8n

To create a NOCK ticket from n8n:

1. Add an HTTP Request node.
2. Method: POST.
3. URL: https://nocknock.cloud/api/v1/tickets.
4. Auth: Header Auth or manual Authorization: Bearer <NOCK_API_KEY>.
5. Body: JSON with project_id, title, page_url, and optional fields.

To receive NOCK events:

1. Add a Webhook Trigger node.
2. Use its Production URL as the NOCK webhook endpoint.
3. Add a Code node to verify x-nock-signature before updating other systems.

Make

To create a NOCK ticket from Make:

1. Add HTTP -> Make a request.
2. Method: POST.
3. URL: https://nocknock.cloud/api/v1/tickets.
4. Headers:
   • Authorization: Bearer <NOCK_API_KEY>
   • Content-Type: application/json
5. Request content: JSON with the mapped ticket fields.

To receive NOCK events:

1. Add Webhooks -> Custom webhook.
2. Save the webhook URL in NOCK.
3. Use fields such as event, ticket_id, data.ticket.status, and data.ticket.source in later modules.

GitHub Issues

GitHub Issues can be built as an external adapter:

• NOCK ticket.created webhook creates a GitHub Issue.
• NOCK ticket.status_changed webhook updates a GitHub label, project status, or comment.
• GitHub Issue comments can become NOCK customer-visible replies via POST /api/v1/tickets/{id}/notes.

Store the NOCK ticket ID in the GitHub Issue body, issue metadata, or a small mapping table so updates are idempotent.

Jira

Jira can use the same external adapter pattern:

• NOCK ticket.created webhook creates a Jira issue.
• NOCK ticket.status_changed webhook triggers a Jira transition or comment.
• Jira comments or customer updates can become NOCK customer-visible replies.

Because Jira workflows vary heavily, keep the first adapter narrow: map one NOCK project to one Jira project, choose a small set of statuses, and log the external issue key back into your own mapping table.

Recommended first automation

Start with one direction:

1. NOCK ticket.created webhook.
2. Create the external issue.
3. Store nock_ticket_id, external issue ID, and webhook id.
4. Add idempotency so duplicate deliveries do not create duplicate issues.

Add reverse sync only after the one-way flow is stable.

Related