Linear Integration with SmythOS
Want to build automations for modern software teams? Connect Linear to SmythOS and empower your agents to create issues and manage your product development lifecycle programmatically.
List of Linear Components
Quickly compare Linear components by what they do and their key I/O. Click any component name to jump directly to its detailed guide.
Component | Action | What it Does | Inputs | Key Outputs | Use Case |
---|---|---|---|---|---|
Create Issue | Write | Creates a new issue in a specified team's backlog. | required title , description , teamId | issueId | Automatically creating a bug report from a customer ticket. |
List Teams | Read | Retrieves a list of all teams in your Linear workspace. | required trigger | teamId , teamName | Finding the correct team ID to create an issue in. |
Prerequisites
Before you begin, please ensure you have the following:
- An active SmythOS account. (Sign up here).
- A Linear account.
- Your Linear personal API Key.
Getting Started With Linear
The connection between SmythOS and Linear is configured using a secure, personal API Key.
Step 1: Get Your Linear API Key
- Log in to your Linear account.
- Navigate to Settings > API.
- Under Personal API Keys, give your new key a descriptive label (e.g., "SmythOS Agent") and click Create key.
- Copy the API Key immediately. It will not be shown again for security reasons.
Step 2: Store Your API Key in SmythOS Vault
Your API Key is a sensitive credential. Use the SmythOS Vault
to store it securely.
- In your SmythOS dashboard, navigate to the Vault.
- Create a new secret and paste your Linear API Key as the value. Give it a memorable name, like
linear_api_key
. - For more details, see the Vault Documentation.
Step 3: Configure a Linear Component
- In your SmythOS agent graph, drag and drop any Linear component.
- Click the component to open its Settings panel.
- In the
API Key
field, select the secret you saved in the Vault (e.g.,linear_api_key
). - Your connection is now configured for that component.
Which Linear Component Should I Use?
If you need to… | Target | Use this Component | Why this one? |
---|---|---|---|
Create a new bug report or feature request | A teamId and a title | Create Issue | The primary method for programmatically adding new items to your Linear boards. |
Find the ID for your "Engineering" or "Design" team | Your workspace | List Teams | This is an essential first step to get the teamId required to create issues. |
Component Details
This section provides detailed information for each Linear component.
Create Issue
Creates a new issue within a specified team in your Linear workspace.
Inputs
Field | Type | Required | Notes |
---|---|---|---|
title | string | Yes | The title of the issue you want to create. |
description | string | Yes | The main body content of the issue. Supports Markdown for formatting. |
teamId | string | Yes | The unique ID of the team where the issue will be created. |
Outputs
Field | Type | Description |
---|---|---|
issueId | string | The unique identifier of the newly created issue. |
Response | object | The full, raw JSON response from the Linear API, containing the complete issue object. |
Headers | object | The HTTP headers from the API response. |
{
"component": "linear.createLinearIssue",
"title": "User cannot log in with SSO",
"description": "A user reported the following error: 'Authentication failed. Please try again.'\\n\\n**User Email:** user@example.com\\n**Timestamp:** 2025-06-12T10:00:00Z",
"teamId": "a1b2c3d4-e5f6-7890-a1b2-c3d4e5f6g7h8"
}
List Teams
Retrieves a list of all teams within your Linear workspace. (Formerly "Get Team Information").
Inputs
Field | Type | Required | Notes |
---|---|---|---|
trigger | any | Yes | Any input value can be used to trigger the component's execution. |
Outputs
Field | Type | Description |
---|---|---|
teamId | string | The unique ID of the first team found. For a full list, parse the Response . |
teamName | string | The name of the first team found. |
Response | object | The raw JSON response, containing a list of all team objects with their IDs and names. |
Headers | object | The HTTP headers from the API response. |
{
"component": "linear.getTeamInformation",
"trigger": "start"
}
Best Practices & Advanced Tips
- Secure Your API Key: Your Linear API Key grants access to your workspace. Always store it in the SmythOS
Vault
and never expose it. - Use the GraphQL API for Advanced Queries: While these components cover common actions, Linear's power lies in its GraphQL API. For complex queries (e.g., getting all issues with a specific label assigned to a specific user), you may need to use a generic GraphQL component in SmythOS.
- Find Your Team ID: The most common prerequisite for creating issues is the
teamId
. Use theList Teams
component first to programmatically find the correct ID rather than hardcoding it. - Automate Your Triage: Combine the
Create Issue
component with other tools to build a powerful triage system. An agent can receive an alert, use an LLM to determine its priority and relevant team, find theteamId
, and then create a well-formatted issue.
Troubleshooting Common Issues
-
Error:
401 Unauthorized
- Cause: The API Key is incorrect, has been revoked, or is missing.
- Solution: Verify that the API Key in your SmythOS Vault is correct and active. Generate a new key in your Linear settings if necessary and update your Vault secret.
-
Error:
404 Not Found
- Cause: The
teamId
provided is incorrect or does not exist. - Solution: Use the
List Teams
component to get a valid list of team IDs and ensure you are using the correct one.
- Cause: The
-
Error:
400 Bad Request
/ Validation Error- Cause: A required field like
title
orteamId
is missing from the request. - Solution: Check that all required inputs are provided and are not empty strings.
- Cause: A required field like
What's Next?
You are now ready to build powerful development workflows with the SmythOS Linear Integration!
Consider these ideas:
-
Build an Agent That...
- Connects to your customer support software (like Zendesk or Intercom). When a user reports a bug, the agent automatically creates a new, detailed issue in your engineering team's Linear backlog.
- Monitors a GitHub repository. When a new pull request is opened that mentions a specific issue ID in its title (e.g.,
[LIN-123]
), the agent finds that issue in Linear and posts a comment with a link to the PR. - Acts as a "bug reporter" in Slack. A team member can use a slash command to trigger an agent, which asks them for a title and description, and then creates the issue in Linear for them.
-
Explore Other Integrations:
- When a new issue is created in Linear, trigger an agent to create a corresponding channel in Microsoft Teams or Slack for discussion.
- Connect Linear to your CI/CD pipeline. When an issue is moved to "Done," an agent could trigger a deployment process.
- Log the time spent on issues by syncing data between Linear and a time-tracking application.