Linear Connector

Who can do this: Owners, Admins, and Editors can add and manage project connectors. See Roles and Permissions for details.

Connect your Linear workspace and build visibility tools for every audience. Sprint boards for engineers, blocker dashboards for managers, delivery views for executives, and voting boards for customers. All powered by your real Linear data.

What you can do

Access your workspace data:

• Read issues with status, priority, and assignee
• Browse projects, cycles, and milestones
• View workflow states and team structures
• Track labels, estimates, and due dates

Build visibility tools:

• Sprint boards with your actual workflow states
• Blocker timelines showing stuck issues
• Delivery dashboards for leadership
• Feature voting boards for customer input

Create issues from external input:

• Public voting boards that create Linear issues
• Feature request forms that feed your backlog
• Bug reports that land in triage
• Customer feedback that becomes actionable

Two ways to connect

Linear works with Sticklight at two levels, depending on what you’re building.

Connector (for building)

The Linear connector lets Sticklight access your workspace while you build. Connect once and Sticklight can read your issues, understand your workflow states, and show you live data in the editor.

Use this for: Dashboards, sprint boards, blocker views, anything that displays your Linear data.

API key (for live updates and writes)

When you build something that needs to stay in sync with Linear or create new issues, like a public voting board that submits feature requests, Sticklight needs your Linear API key. This lets your published app read fresh data and write back to Linear.

Use this for: Voting boards, feature request forms, bug submission tools, anything where your app creates or updates Linear issues.

Sticklight prompts you for the API key when it’s needed. You don’t have to set it up in advance.

Available data

Once connected, your project can access:

Data	What you get
Issues	Title, description, status, priority, assignee, labels
Projects	Names, status, milestones, target dates
Cycles	Sprint names, dates, progress, scope
Workflow states	Your custom columns like Backlog, In Progress, Done
Teams	Team names, members, settings

Common use cases

Sprint board your way

A Kanban view built from your actual Linear workflow states. Cards show priority, assignee, and key metadata. Filter by team, cycle, or project. Click any card to open it in Linear.

“Build a sprint board from my Linear workspace. Use my workflow states as columns, show priority and assignee on each card, and let me filter by team and current cycle.”

Connection needed: Connector only

Blockers timeline

A dashboard that surfaces issues stuck in progress. See how long each blocker has been waiting, sorted by duration. Spot the issues dragging down your sprint before they derail delivery.

“Create a blockers dashboard showing issues that have been In Progress for more than 3 days. Display them as a timeline sorted by how long they’ve been stuck, with assignee and priority.”

Connection needed: Connector only

Public feature voting board

A public board where users submit and upvote feature ideas. Top-voted items automatically create Linear issues for your team to triage. Keep your backlog connected to real customer demand.

“Build a public feature voting board where visitors can submit ideas and upvote others. When an idea gets 10 votes, automatically create a Linear issue in my Feature Requests project.”

Connection needed: Connector + API key

Delivery dashboard

A leadership view of engineering progress. See active projects, cycle completion rates, and team velocity. Give executives visibility without asking them to learn Linear.

“Create an executive dashboard showing our active Linear projects with completion percentage, current cycle progress, and issues closed this week by team.”

Connection needed: Connector only

Connecting Linear

Step 1: Connect the connector

You can connect from chat or from your project settings.

From chat:

“Connect my Linear workspace”

From project settings: Open Settings, go to Connectors, and select Linear.

When you start the connection:

1. Click Connect Account.
2. Log in to Linear when the authorization window opens.
3. Review the permissions Sticklight is requesting.
4. Click Authorize to complete the connection.

Once connected, Sticklight can access your Linear workspace while you build.

Step 2: Add your API key (when needed)

If you’re building something that creates issues or needs live data after publishing, Sticklight enables Cloud Backend automatically. This provides the backend function needed to securely connect to Linear. Then it prompts you for your Linear API key.

To create an API key:

1. In Linear, go to Settings → API → Personal API keys
2. Click Create key
3. Name it (e.g., “Sticklight App”)
4. Copy the generated key
5. Paste it into Sticklight when prompted

The key is stored securely and only used by your published app to read from and write to Linear.

Linear structure

When prompting, it helps to understand Linear’s hierarchy:

• Workspace: Your organization’s Linear account
• Team: A group within your workspace (like “Engineering” or “Product”)
• Project: A collection of related issues (like “Q1 Launch” or “Mobile App”)
• Cycle: A time-boxed sprint with a start and end date
• Workflow state: Status columns like Backlog, Todo, In Progress, Done

Good prompt: “Build a sprint board for the Engineering team showing issues in the current cycle, grouped by workflow state.”

What visitors see

When you publish your app, consider your audience:

• Internal dashboards: Team members see sprint progress and blockers
• Leadership views: Executives see delivery health without implementation details
• Public boards: Customers see a voting interface, not your internal issue data

For public-facing tools like voting boards, visitors only see what you choose to display. Your internal issue discussions, assignees, and implementation details stay private unless you explicitly show them.

Limitations

• Workspace-level access. The connector accesses one Linear workspace per connection. For multiple workspaces, create separate projects.
• Permission-based. You can only access teams and projects your Linear account has permission to view.
• API rate limits. Linear limits API requests. High-frequency updates may be throttled.
• Write moderation. Public forms that create issues should include moderation to prevent spam or duplicate submissions.

FAQ

Does connecting Linear cost anything?

No. Connecting is free. You only spend credits when you build something.

Will this change anything in my Linear workspace?

Read-only dashboards don’t modify your data. If you build features that create issues, like voting boards or submission forms, those create new issues in Linear. You control whether write features are included.

What’s the difference between the connector and the API key?

The connector lets Sticklight read your Linear data while you build. The API key lets your published app read fresh data and create new issues. Dashboards only need the connector. Voting boards and submission forms need both.

Do I need to know how to code?

No. Describe what you want in plain language and Sticklight builds it. If you do write code, the files are there to open and edit.

How do I get the best results?

Name your specific team, project, or cycle. Instead of “build a sprint board,” try “build a sprint board for the Engineering team showing the current cycle with workflow states as columns and priority badges on each card.”

Can I build dashboards for stakeholders without giving them Linear access?

Yes. That’s a primary use case. Build a focused view showing delivery progress, and stakeholders never need to log into Linear.

How do I prevent spam on public voting boards?

Consider adding rate limiting, requiring email verification, or building a moderation queue before ideas create Linear issues. You can also set vote thresholds before issues are created.

Can I connect multiple Linear workspaces?

Each project connects to one Linear workspace. For multiple workspaces, create separate projects.