Skip to main content
connic

Linear

Run connic agents on issues and comments in your Linear teams. Agents reply in the comment thread or create new issues.

Modes
Inbound, Outbound
Set up in
Dashboard or connectors/*.yaml
Documentation
Linear docs
Publisher
By connic

Answer issues and comments

When an issue or comment in the team matches an inbound connector's events, every agent linked to it starts. An outbound connector on the same Connection posts the result as a comment.

Pick events and actions
Issue reacts to new and updated issues, Issue.create only to new ones. The same works for comments.
Several connectors per team
Each connector has its own webhook, so you can watch issues with one and comments with another, or use one per environment.
No loops, no double runs
Changes by the API key's member are ignored, and an event that Linear delivers again doesn't start a second run.
  1. Something happens in the team

    Someone creates or updates an issue, or writes a comment.

    Issue.create
  2. connic checks and confirms the event

    It verifies the signature with the webhook's secret, rejects deliveries older than a minute and answers Linear well within its 5 seconds.

    Linear-Signature
  3. Linked agents start

    The run gets the event and action, the issue ID and title, the text in Markdown, a link and who caused it.

    Comment.create
  4. The answer lands in the thread

    An outbound connector on the same Connection comments on the issue, in the thread of the comment that started the run.

One API key, the webhook is registered for you

You paste a personal API key once. Saving an inbound connector registers a signed webhook for its team in Linear, and deleting the connector removes it.

Your key, your workspace
The key belongs to a member of your Linear workspace, and you can revoke it in Linear at any time. Admins decide whether members may create keys.
One team per connector
Enter the team by its key, like ENG. Private teams work when the key's member belongs to them.
Nothing to copy back
connic generates the webhook's secret and checks every delivery with it. You find the webhook in Linear's API settings.
linear-webhook.json
{
  "url": "https://connect.connic.co/linear/<connector-id>",
  "teamId": "<ID of team ENG>",
  "resourceTypes": ["Issue", "Comment"],
  "secret": "<generated by connic>",
  "label": "connic"
}

Comment on issues or create new ones

An outbound Linear connector posts the agent's output, whether the run answers an issue or comes from another connector or a schedule.

Routing
An issue_id in the output wins. Without one, a run started from an issue on the same Connection comments there, and any other run creates an issue in the connector's team.
Three ways to send
Send after every completed run, give the model a tool to call, or call send_connector from middleware when your code decides.
Rate limits handled
When Linear rate-limits a comment or issue, connic waits and sends it again.
output.json
{
  "title": "EUR totals are rounded twice at checkout",
  "body": "Orders in EUR are one cent off since 2.14.0."
}
connector-payload.json
{
  "body": "Reproduced: the total is rounded twice.",
  "issue_id": "ENG-42"
}

Where Linear fits

Pick a setup to see what reaches the agent and what it posts back to Linear.

Someone creates an issue, and the agent asks for missing details and names the likely area.

New issue
Inbound Linear
issue-triage
Comment on the issue
linear-payload.json
{
  "event": "Issue",
  "action": "create",
  "issue": "ENG-418",
  "title": "Refund button does nothing",
  "text": "Clicking Refund on an order shows no error and no refund.",
  "url": "https://linear.app/acme/issue/ENG-418/refund-button-does-nothing",
  "actor": "Jane Doe"
}
output.json
{
  "body": "Likely the refunds service. Which order ID and browser?"
}

Someone asks a question in a comment, and the agent answers in the same thread.

New comment
Inbound Linear
codebase-helper
Reply in the thread
linear-payload.json
{
  "event": "Comment",
  "action": "create",
  "issue": "ENG-421",
  "title": "Round EUR totals once",
  "text": "Which services still round on their own?",
  "url": "https://linear.app/acme/issue/ENG-421/round-eur-totals-once#comment-7f3e",
  "actor": "Jane Doe"
}
output.json
{
  "body": "The cart and invoice services. Both call round() before payment."
}

Your helpdesk sends a bug report, and the agent turns it into a Linear issue.

Helpdesk
Inbound webhook
bug-reporter
New issue in ENG
ticket.json
{
  "ticket_id": "T-20931",
  "customer_id": "C-1042",
  "subject": "Invoice PDF shows the wrong VAT rate",
  "message": "Since Monday our invoices show 16% instead of 19%."
}
output.json
{
  "title": "Invoice PDF uses 16% VAT instead of 19%",
  "body": "Reported in T-20931: invoices since Monday use 16%."
}

Your monitoring reports a new error, and the agent creates an issue with what it knows.

Error monitoring
Inbound webhook
error-triage
Issue for the error
alert.json
{
  "service": "checkout-api",
  "error": "Order ord_88412 has no currency",
  "first_seen": "2026-11-16T09:12:04Z",
  "events_last_hour": 214
}
output.json
{
  "title": "checkout-api: orders without a currency fail",
  "body": "214 errors in the last hour, first seen at 09:12 UTC."
}

Linear FAQ

A personal Linear API key, which you create under Settings, Account, Security & Access. Inbound connectors register a webhook for their team, which Linear only allows workspace admins, so they need an admin's key.

From the Linear member the API key belongs to. connic ignores events that member causes, so an agent doesn't start itself again. Create the key for a member just for your agents, so everyone else's changes start runs.

No. Saving an inbound connector registers a webhook for its team with a secret connic generates, and deleting the connector removes it. Private teams work when the key's member belongs to them.

Yes, with type: linear, the team key, and the name of a Linear Connection that holds the API key.