AtlasWork, planned itself.

The AI-native, all-in-one work platform. Tasks, projects, CRM, contracts, and analytics in one calm workspace.

All systems operational
  • SOC 2 II
  • ISO 27001
  • HIPAA
  • GDPR

Product

  • Overview
  • PDF tools
  • Diagram tools
  • People & HR
  • Integrations
  • Marketplace
  • Pricing

Resources

  • Guides
  • Glossary
  • Compare
  • Docs
  • API reference
  • Support
  • Changelog
  • Status

Company

  • About
  • Careers
  • Press
  • Contact

Legal & trust

  • Trust center
  • Security
  • Privacy
  • Terms
  • DPA
  • GDPR
  • SLA
  • Refunds
  • Google API data
Atlas, a product by wrxstack.com·© 2026 wrxstack·All rights reserved
PrivacyTermsSecurityStatus
Skip to documentation
Docs
Back to Atlas

Start here

  • Overview

Developer

  • REST API guide
  • Authentication
  • API reference
  • MCP (AI agents)
  • SDKs
  • Quick actions

Webhooks

  • Overview
  • Quickstart
  • Events
  • Payloads and headers
  • Security and signing
  • Delivery and retries
  • Managing via API

Connect

  • Connectors
  • Integrations

Product

  • Collaboration and chat

Reference

  • Glossary
  • Keyboard shortcuts
  • Module reference
Linear logo

Work management

Linear

Connect Linear through Atlas OAuth and verify bounded GraphQL operations.

AuthOAuth 2.0UpdatesReal-timeAvailable

What this connector does

  • Start the Linear OAuth consent flow from Atlas and store encrypted connector tokens server-side.
  • Show persisted connection status from the shared connector store.
  • Run bounded Linear GraphQL issue reads/writes from explicit operator actions.
  • Keep background task sync and webhook ingestion as separately verified scheduler workflows.

Before you begin

  • You can edit the Atlas tenant Integrations settings.
  • Your Atlas deployment has Linear OAuth client credentials configured.
  • You can approve the Linear workspace that Atlas should connect to.

Get your credentials

1

Configure the Linear OAuth app

Create or open the Linear OAuth app used by Atlas and confirm the callback URL points at the Atlas connector callback route. Linear app settings

2

Set Atlas OAuth credentials

Set LINEAR_CLIENT_ID and LINEAR_CLIENT_SECRET on the Atlas API and restart the service if your platform requires it.

3

Start OAuth from Atlas

Open the Atlas Linear connector page, click Connect, approve Linear consent, and return to Atlas.

4

Verify the connection

Use the issue-read verification action to prove the stored credential can reach Linear GraphQL.

5

Operate background sync deliberately

Turn on scheduled task sync only after the team has retained workflow evidence for the deployment environment.

Required scopes and permissions

Read Linear workspace dataread
Write Linear issue updateswrite
Create Linear issuesissues:create

Setup checklist

  1. Confirm LINEAR_CLIENT_ID and LINEAR_CLIENT_SECRET are configured for the Atlas API.
  2. Click Connect and complete Linear OAuth consent.
  3. Confirm Atlas shows the persisted Linear workspace connection.
  4. Run the issue-read verification and confirm the operation completes without exposing provider payloads.
  5. Enable background sync only after the scheduler workflow has retained operational proof.

Troubleshooting

  • API key rejected

    Use the OAuth Connect button for new installs. Legacy API-key registration is supported only for compatibility clients.

  • Verification cannot reach Linear

    Confirm the OAuth app credentials, callback URL, and workspace consent before rerunning the issue-read check.

  • Verification fails before connect

    Complete Linear OAuth consent before running provider operations.

Webhooks

Atlas can verify Linear webhook signatures when the deployment is configured for webhook delivery. Background ingestion is operated separately from the manual verification console.

Events Atlas listens for

  • Issue create
  • Issue update
  • Project status update

Provider docs: https://developers.linear.app/docs/graphql/webhooks

Disconnect and data deletion

  1. Click Disconnect on the Atlas Linear connector page to revoke the stored Atlas connection.
  2. Open Linear workspace settings and remove the Atlas OAuth app grant if you want to revoke provider-side access immediately.
  3. Atlas does not cache Linear provider payloads in the browser.

Once you have the credentials above, paste them into the live connector page to finish connecting Linear.

Open the Linear connector page

On this page

  • What this connector does
  • Before you begin
  • Get your credentials
  • Required scopes and permissions
  • Setup checklist
  • Troubleshooting
  • Webhooks
  • Disconnect and data deletion