Linear
Your customers connect their Linear workspace once and Askel handles the API key, the request signing, and the data mapping. Issue states, cycle progress, and project health flow into your product without a line of custom code on your end.
What you can do
Read and write issues across any team
Pull open issues, create new ones, or update state and assignee. Askel resolves team IDs and state IDs automatically so you never hardcode workspace-specific values.
Track cycle and project progress in real time
Query active cycles, scope counts, and completion percentages. Your product can surface engineering progress to non-Linear users without asking them to log in.
Filter by label, priority, and assignee
Narrow down issues to exactly what your workflow needs. Labels like 'customer-reported' or 'p0-blocker' are pulled dynamically from the customer's workspace so your filters stay accurate.
Listen for state changes via webhook
Askel registers a Linear webhook on the customer's workspace and forwards events to your product. When an issue moves to Done or a new bug is filed, your workflows fire immediately.
Create issues on behalf of end users
Let your users report bugs or request features directly from your product. Askel posts the issue to the correct Linear team and links the Linear URL back to the originating record.
Sync project and team metadata
Pull the list of teams, projects, milestones, and members on demand. Use this to build dropdowns, routing rules, or onboarding checklists that reflect the customer's actual workspace.
Surfacing engineering progress to a customer success portal
Meridian DevTools sells a developer productivity platform. Their customers each have a Linear workspace where their engineering teams track work. Meridian's customer success portal needs to show each account's open issues, active cycle name, and the count of issues labelled 'customer-reported' without requiring CS reps to have Linear access.
- 1
Customer connects Linear
Apex Systems' IT admin generates a personal API key in their Linear account settings and pastes it into Meridian's onboarding wizard. Askel stores the key; it never reaches Meridian's servers.
- 2
Workspace discovery
Askel reads Apex Systems' Linear workspace: three teams (Platform, Mobile, Infra), their issue states (Backlog, In Progress, In Review, Done, Cancelled), labels including 'customer-reported' and 'regression', and the current active cycle named 'Apex Q2-Sprint-4'.
- 3
Mapping to Meridian's data model
Meridian's CS portal needs three fields: open issue count, active cycle name, and customer-reported count. Askel maps these to Linear's GraphQL fields and stores the mapping against Apex Systems' workspace ID.
- 4
Scheduled pull and webhook
Askel polls Linear every 15 minutes and also registers a webhook for issue state-change events. When Apex Systems' team closes an issue labelled 'customer-reported', the portal counter drops in near real time.
- 5
CS rep view goes live
Meridian's CS reps open the Apex Systems account page and see 'Active cycle: Apex Q2-Sprint-4, 12 open issues, 3 customer-reported'. No Linear login required, no manual status updates from Apex Systems' engineering team.
API token
Customer's Linear admin generates a personal API key in their Linear settings (Account -> API -> Personal API keys) and pastes it into Askel. Askel sends it as a raw Authorization header per request; the key never reaches your servers.
How Askel sits between your product and the customer's system
FAQ for Linear
Does this work with Linear's free plan or only paid workspaces?+
Can we scope the API key to read-only access?+
What happens if the customer rotates or revokes their API key?+
Are Linear webhooks reliable enough to use as the primary data source?+
catching drift before it breaks, and hitting go-live dates.
© 2025 Askel.ai. All rights reserved.