Support

Linear + DarhimLabs

Connect Linear to AI Inbox, agents and automations without rebuilding your current stack.

Connect Linear View API

Linear integration health

Status is powered by separate read-only health checks and never treats missing data as success.

UnknownView full history

Uptime 30d

No data

Avg latency

No data

Active workspaces

Collecting

Last 28 days

No measurement

Gray bars mean days without data. History will fill automatically after the next health checks.

What it does

What the Linear integration does

The scenarios, limits and implementation notes live in MDX so the page stays SEO-ready and easy to update.

Official Linear website

Scenarios

Linear in DarhimLabs connects support with AI Inbox, agents and automations. The most common scenario is ticket triage, SLA routing, support automation, but the connector is not just a simple "send event". DarhimLabs maintains object mapping, last sync status, health check scopes and audit log of configuration changes in one place.

In practice, the team sees customer conversation, AI recommendations, integration status and sync result without switching between tools. If an AI agent qualifies a lead, escalates an issue or updates data, Linear receives only the fields explicitly selected in workspace configuration.

Use cases

Automatic conversation enrichment with context from Linear.
Synchronization of qualification results, statuses or documents without manual rewriting.
Escalation to human with AI decision history and source link in Linear.
Integration effectiveness reporting in Command Center.
Test delivery and replay for ticket.created and ticket.updated events without touching production data.
Health check of token, scopes, rate limits and last successful sync before enabling automation.

When to use this integration

Use Linear when your team already works in this tool and you want DarhimLabs to act as an AI layer over your current stack. The integration is particularly useful for flows: ticket triage, SLA routing, support automation.

The biggest return appears when customer conversations create real operational tasks: a lead needs to reach sales, an issue needs support, a document needs the knowledge base, a payment needs verification or a deadline needs the calendar. DarhimLabs then enforces the rule: first context and workflow consent, only then write to external system.

Limitations

Sync scope depends on DarhimLabs plan and permissions granted in Linear.
DarhimLabs does not overwrite fields outside configured field mapping.
For sensitive data we recommend a separate test workspace before enabling production.
If Linear restricts API with rate limits or plan-based access, health check shows this as configuration risk instead of promising full realtime.
Coming soon or beta mode is not presented as production connector. Integration status is visible in marketplace and on this page.

What we sync

Synchronization covers objects: Tickets, Customers, SLA events. Each object has explicit sync direction, fields, trigger and implementation note in integration data table.

Typical flow looks like this: conversation arrives at AI Inbox, agent evaluates intent, DarhimLabs records summary and confidence score, and connector sends only approved fields to Linear. For outbound write, retry/backoff and delivery log are available, and for inbound read, source freshness is visible.

Implementation notes

Before production launch, perform token test, field mapping test and webhook event test. All errors go to audit log and health check section in integration dashboard.

Recommended rollout sequence:

Connect Linear in sandbox or test workspace.
Run read-only sync for Tickets and Customers objects.
Verify field mapping with business process owner.
Enable write only for one workflow, e.g. ticket triage.
After 24 hours check health check, audit log and retry delivery.

Objects & field sync

Co synchronizujemy z Linear

Tabela obiektow, kierunkow synchronizacji, pol i triggerow
Object	Direction	Fields	Trigger	Notes
Tickets	bidirectional	ticket_id, subject, priority, status	ticket escalated	Field mapping is configurable per workspace.
Customers	inbound	customer_id, email, plan	SLA risk detected	Field mapping is configurable per workspace.
SLA events	outbound	sla_id, deadline, risk	customer updated	Field mapping is configurable per workspace.

Setup guide

Linear setup, step by step

Every step has a concrete goal, and the validation step does not create production data.

Open the integration marketplace

Go to Dashboard -> Integrations -> Linear.

Real DarhimLabs integrations dashboard screenshot with provider catalog, setup, health checks and API controls

Authorize Linear

Use OAuth, API key or webhook setup depending on the connector. DarhimLabs does not store user passwords.

Review required permissions

Grant only the scopes required for the selected workflow. Each scope has a business explanation.

This is an administrative step and does not require a separate screen.

Configure field mapping

Choose how DarhimLabs fields map to Linear objects.

Run a synchronization test

The health check verifies token, scopes, sample read and test event without creating production data.

Screenshots

Widoki konfiguracji Linear

Screenshoty pokazuja realny przeplyw DarhimLabs: overview, autoryzacje, mapping, health check i logike setupu.

Demo embed

Wstaw dzialajace demo na strone

Pokaz Linear + DarhimLabs w praktyce bez formularza i bez logowania. Embed otwiera pelne demo w nowej karcie, a iframe wysyla resize event do strony nadrzednej.

Otworz pelne demoStory: ModaNova Store

HTML iframe

<iframe
  src="https://demo.darhimlabs.pl/embed/ecommerce"
  width="100%"
  height="600"
  frameborder="0"
  loading="lazy"
  title="Demo DarhimLabs - ModaNova Store"
></iframe>

React component

import { DarhimLabsDemoEmbed } from "@darhimlabs/demo-embed";

<DarhimLabsDemoEmbed story="ecommerce" autoresize />

Permissions

Uprawnienia wymagane przez Linear

Kazdy scope ma opis biznesowy. Write access jest pokazany jawnie.

Tabela scope, typu dostepu, powodu i wrazliwosci
Scope	Access	Why needed	Sensitive
tickets.read	read	Read access is used to match records and prevent duplicates in Linear.	Nie
tickets.write	write	Write access is used only for approved workflow actions in Linear.	Tak
customers.read	read	Read access is used to match records and prevent duplicates in Linear.	Nie

Security notes

Secure implementation without black boxes

The integration page helps IT teams assess risk before the trial, not only during procurement.

OAuth/API secrets are stored as references and can be revoked without deleting sync history.

The audit log records authorization, field mapping changes, retries and health check errors.

Health checks verify tokens, scopes and a test event without creating production data.

Workspace-level RLS limits access to connector configuration and sync logs.

Linear has an explicit Native status, so we do not hide whether the connector is native, beta, manual or webhook-based.

Recommended stack

Polecane dla branzy

Customer SupportB2B SaaSE-commerce

WhatsApp Business30 minutes

API & custom extension

Rozszerz Linear przez API

Jezeli natywny connector nie pokrywa calego workflow, doloz REST API, OpenAPI spec albo webhooki v2 z HMAC, retry/backoff i sandbox test delivery.

API docs Webhooks OpenAPI Sandbox

REST API

Tworzenie i aktualizacja webhook endpointow, custom actions i integracji workspace.

OpenAPI spec

Specyfikacja pod codegen, review security i automatyczne testy kontraktow.

Webhooks v2

Eventy v2 dla leadow, rozmow, handoffow, health checkow i sync statusu.

HMAC signatures

Kazdy delivery moze byc podpisany naglowkiem DL-Signature z timestampem.

Retry/backoff

Retry/backoff dla bledow 5xx i timeoutow: 1 min, 5 min, 15 min, 1h, 24h.

Sandbox/test delivery

Sandbox payload, test delivery i replay bez dotykania produkcyjnych danych.

Event catalog

ticket.createdticket.updatedconversation.handoff_requestedintegration.health_check_failedlead.createdlead.updatedconversation.createdconversation.resolvedbot.message.sentintegration.sync.startedintegration.sync.completedknowledge.document.indexed

Signed webhook payload

{
  "id": "evt_01J...",
  "type": "conversation.handoff_requested",
  "created_at": "2026-05-07T12:00:00Z",
  "data": {
    "integration": "linear",
    "workspace_id": "wrk_...",
    "conversation_id": "conv_...",
    "lead_score": 87
  }
}

Headers

Content-Type: application/jsonUser-Agent: DarhimLabs-Webhooks/2.0DL-Event: conversation.handoff_requestedDL-Signature: t=timestamp,v1=hmac_sha256

Case study

Linear in a real workflow

The team had customer context split across tools and could not reliably audit AI-assisted decisions.

Operations team

Linear connected support, sales and automation in one workspace

DarhimLabs connected Linear, mapped the key objects and added health checks, webhooks and audit logging.

"The integration made AI operations measurable instead of another disconnected automation."

1 day

Setup time

42%

Manual routing reduced

100%

Audit coverage

FAQ

Pytania o Linear

Does DarhimLabs overwrite data in Linear?

Not by default. DarhimLabs updates only fields selected in field mapping and keeps an audit log of every change.

Can I synchronize only selected records?

Yes. You can limit synchronization by status, score, channel, tag, workspace or automation condition.

Can I use read-only permissions?

Yes. Permissions are described scope by scope, and the Linear integration can run read-only if the workflow does not need writes.

What does the health check verify?

It verifies token status, required scopes, last synchronization and rate-limit errors without creating production data.

Does this integration work with webhooks?

Yes. Key lifecycle events are available through DarhimLabs API and webhooks v2.

How long does setup take?

Most teams complete the first setup in minutes. Enterprise rollouts can include a shared implementation plan.

Can I test it without production data?

Yes. You can run test delivery, replay the last event and inspect HMAC logs without sending production data.

Will I see when the connector stops working?

Yes. DarhimLabs shows the last health check, token status, missing scopes and last synchronization error.

Related integrations

Often used together

HubSpot

CRM

Sync contacts, companies, deals and lifecycle stages between HubSpot and DarhimLabs.

View setup

Salesforce

CRM

Connect AI conversations with Salesforce leads, contacts, opportunities and routing.

View setup

Pipedrive

CRM

Create leads, activities and deals in Pipedrive after conversation qualification.

View setup

Zoho CRM

CRM

Sync contacts and sales tasks in Zoho CRM.

View setup

Twilio

Communication

Voice, SMS and WhatsApp transport for AI agents and reminders.

View setup

WhatsApp Business

Communication

Conversations, template messages, opt-in and SLA in one inbox.

View setup

Connect Linear with DarhimLabs

Start a trial, book a demo, or build a custom extension through the API.

Start trial Book a demo API docs