integrations

Connecting Linear to OneClik

Turn a captured bug report into a Linear issue on the right team — with the page URL, browser, and reporter attached, and a link back to the full developer trace.

~5 minutesWorkspace admin required3 phases

Before you start

  • A Linear account with access to the workspace and team you want issues created in.
  • A OneClik workspace admin role — every Linear setting, including just viewing the connection status, is admin-only.

1Generate an API key

1Open Linear's API settings

In Linear, go to Settings → Security & access → Personal API keys (or your workspace's equivalent under account settings).

2Create the key

Select New API key, label it OneClik integration, and confirm.

3Copy it immediately

Linear shows the key exactly once. Copy it now — you'll paste it into OneClik in the next phase.

2Connect in OneClik

1Open the Linear integration settings

In OneClik, go to Settings → Integrations → Linear and paste the API key from Phase 1. Unlike Jira, there's no site address to enter — Linear's API lives at one fixed address for every workspace.

2Pick a team from the dropdown

As soon as the key validates, OneClik asks Linear which teams it can see and fills the dropdown automatically:

Team — select where issues will be created
EngineeringENG
DesignDES
GrowthGRO

Don't see the team you want? Type its team key directly — the short code Linear shows before every issue number in that team, like ENG in ENG-214.

3Save the connection

Select Connect. The API key and team key are both verified against Linear before anything is saved, so a typo or a revoked key is caught immediately rather than at the first real push.

Verify it worked

✓Check the connection status

The Linear settings page shows a live status checked against Linear's API every time it's opened, so a revoked key surfaces immediately rather than only at the next push.

2Send a test issue

Push any existing OneClik issue to Linear and open it in the connected team. The issue carries the page URL, browser, reporter, and timestamp, plus a link back to View developer information — the console logs and network trace OneClik keeps in its own portal rather than copying into Linear.

Troubleshooting

OneClik can't verify the connection

Most often this means the API key was revoked or mistyped. Go back to Linear's Settings → Security & access → Personal API keys, generate a fresh one, and paste it in again — Linear keys, unlike Jira tokens, don't show a separate "expired" state; a bad one just fails outright.

The team dropdown is empty or missing a team

The account behind the key doesn't have access to that team in Linear. Ask a Linear workspace admin to add the account to the team, or type the team key directly if you already know it.

"TeamKey is required: no team is stored for this workspace"

This appears if you try to update just the API key without ever having picked a team. Go through the connection form once with both the key and a team selected — after that, either can be updated alone.

I disconnected Linear — will old issue links still work?

Yes. Disconnecting removes the stored key so no new issues can be created, but every issue already pushed to Linear keeps its permalink back from OneClik, so historical tickets stay reachable.

Next upWeb Widget

OneClik · Integrations documentation. Need help? Contact support