NOCK Linear Integration: Overview and How It Works

The Linear integration lets teams that already use Linear turn NOCK tickets into Linear issues and keep status changes in sync. It is optional. NOCK works as a standalone ticket system with its own dashboard, Customer Portal, notes, replies, Public API, and webhooks.

How the workflow fits together

Once you connect NOCK to your Linear workspace, the integration handles three distinct moments in the lifecycle of a piece of feedback:

1. Ticket created in NOCK - A visitor submits feedback, a team member logs a report, or an automation creates a ticket. NOCK can create a linked issue in the configured Linear team and project.
2. Engineers work in Linear - Your team triages, assigns, and resolves the issue in Linear when that is the preferred engineering workflow.
3. Status syncs back to NOCK - When the Linear issue moves through statuses, NOCK updates the corresponding ticket status automatically. Customers checking the Customer Portal see a clean status without seeing internal Linear details.

Is this integration required?

No. The Linear integration is entirely optional. If your team does not use Linear, you can skip this section completely. NOCK works as a standalone ticket system, and other integrations can be built through the Public API and Webhooks.

What you can do with the integration

• Automatically create Linear issues from every new NOCK ticket
• Route issues to a specific Linear team and project
• Match NOCK ticket categories to available Linear labels by name
• Import existing Linear issues into NOCK as tickets
• Keep ticket statuses in NOCK in sync with Linear issue states

When to use Public API instead

Use the Public API and webhooks when you want to connect tools other than Linear, such as GitHub Issues, Jira, Zapier, n8n, Make, Slack, or custom internal systems. GitHub Issues and Jira are not native NOCK adapters today; build them as external adapters so NOCK tickets stay first-class.

Next steps