Linear

3 production-ready jobs — feature release content pipelines, bug report sentiment focus groups, and cycle velocity launch planning

Linear’s GraphQL API exposes the full state of your engineering workflow: issues, cycles, labels, projects, and velocity metrics. These three jobs pull structured data from Linear into Mavera (Generate, Focus Groups, Mave Agent) to automate release content from completed features, run synthetic focus groups on customer-reported bugs, and align marketing launch timelines with engineering cycle velocity.

---

API Reference Card

Detail	Value
Base URL	https://api.linear.app/graphql
Auth	Personal API Key or OAuth 2.0
Rate limits	5,000 requests/hr; 250,000 complexity points/hr
Key queries	issues, cycles, projects, teams, issueLabels
Mavera base	https://app.mavera.io/api/v1
Mavera auth	Authorization: Bearer mvra_live_...

All examples use LINEAR_API_KEY (a Personal API Key from Linear Settings → API) and MAVERA_API_KEY. Personal API keys inherit the permissions of the user who created them.

---

Prerequisites

1. Create a Linear API key

   Go to linear.app/settings/api → Personal API Keys → Create Key. Copy the key immediately — it is only shown once.
2. Identify team and project IDs

   Every Linear team, project, cycle, and issue has a UUID. Find them via the API or from URLs: linear.app/{workspace}/issue/{ISSUE-ID}.
3. Mavera API key

   Get your key from Mavera dashboard.
4. Environment variables

   export LINEAR_API_KEY="lin_api_xxxxxxxxxxxxxxxx"
   export MAVERA_API_KEY="mvra_live_xxxxx"
   

---

Jobs

#	Job	Linear Data	Mavera Surface	Output
1	Feature Release → Content Pipeline	Completed issues from recent cycles	Generate	Release notes + blog draft + social copy
2	Bug Report Sentiment → Product Focus Group	Issues labeled “bug” + “customer-reported”	Focus Groups	Severity ratings + workflow impact analysis
3	Cycle Velocity → Launch Planning	Cycle history with completed issue counts	Mave Agent	Marketing timeline aligned to eng capacity

---

Rate Limits & Production Notes

Limit Type	Allowance	Strategy
Request rate	5,000 req/hr	300ms delay between calls; batch with nested queries
Complexity points	250,000 pts/hr	Limit first: on connections; avoid deep nesting
Payload size	5 MB response	Paginate large teams; filter with date ranges

Linear charges complexity points per query based on nesting depth and connection sizes. Monitor usage via X-Complexity response headers and keep queries under 10,000 points each. For production, use Linear webhooks instead of polling to stay within limits.

Production checklist:

• Auth: Personal keys don’t expire but can be revoked. For automations, use OAuth 2.0 with a service account.
• Pagination: Connections accept first (max 250) and after (cursor). Follow pageInfo.hasNextPage.
• Filtering: Use query-level filters (eq, in, gte, contains) instead of client-side filtering.
• Webhooks: For release notes, trigger on issue state changes instead of polling.
• Idempotency: Track processed issue IDs to avoid duplicate content generation.
• Mavera credits: Monitor at Dashboard.

---

All Integrations

Linear API Docs

Focus Groups

Mave Agent

Generate