Linear has one of the cleanest developer APIs in the project management space — a well-documented GraphQL API with a simple API key for authentication. It's one of the more rewarding OpenClaw integrations to build.
How OpenClaw Integrations Work
OpenClaw is a self-hosted AI assistant that runs on your own server — typically an EC2 instance — and connects to Slack. It uses Claude under the hood to process requests. Out of the box, OpenClaw doesn't ship with pre-built connections to third-party tools. Instead, integrations are built using the skills system: markdown files in ~/.openclaw/skills/ that give Claude instructions for a particular domain, combined with HTTP tool calls to any API you expose to it.
In practice, adding a real integration means: getting API credentials from the third-party service, building or configuring a small proxy/endpoint that OpenClaw can call, and writing a skill file that tells Claude how to use it. For some tools this is an afternoon of work. For others — like Linear — it's considerably more involved.
Connecting OpenClaw with Linear: Step by Step
Step 1: Get Your Linear API Key
Go to Linear → Settings → API and create a Personal API Key. This key authenticates all requests to Linear's GraphQL API at https://api.linear.app/graphql. No OAuth flow required for personal or service account usage.
Step 2: Learn the GraphQL Schema
Linear's API is GraphQL-only. Use the Linear API explorer to understand the schema before building your proxy. Key objects: Issue, Cycle, Project, Team, User. Queries are flexible — you can request exactly the fields you need.
Step 3: Build the Proxy and Skill File
Your proxy will accept simple HTTP requests from OpenClaw and translate them into GraphQL queries. Write ~/.openclaw/skills/linear.md with your team identifiers and the types of queries available. Linear's consistent naming makes skill file writing relatively straightforward.
Challenges and Caveats
GraphQL Adds a Layer of Complexity
If your proxy developer isn't familiar with GraphQL, there's a learning curve. REST is more familiar territory — GraphQL query construction, pagination with cursors, and error handling work differently.
No Webhooks Without a Public Endpoint
Linear supports webhooks, but your EC2 instance needs a publicly accessible HTTPS endpoint to receive them. If you want OpenClaw to proactively notify your Slack channel when an issue is updated, you'll need to set up SSL and a public endpoint on your server.
Skip All of This — Use Cody Instead
Cody has Linear integration built in. Query issues, cycles, and team workload from Slack — no GraphQL proxy required.
Related Guides
- Connecting OpenClaw with Jira: A Practical Guide
- Connecting OpenClaw with Github: A Practical Guide
- Connecting OpenClaw with Notion: A Practical Guide
Need the model-flexible version? See: How to Connect Linear to OpenClaw: Setup, Models, and Workflow Guide.