Documentation Index
Fetch the complete documentation index at: https://crewai-devin-1778040886-fix-hitl-pre-review-silent-fallback.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Enable your agents to manage issues, projects, and development workflows through Linear. Create and update issues, manage project timelines, organize teams, and streamline your software development process with AI-powered automation.Prerequisites
Before using the Linear integration, ensure you have:- A CrewAI AMP account with an active subscription
- A Linear account with appropriate workspace permissions
- Connected your Linear account through the Integrations page
Setting Up Linear Integration
1. Connect Your Linear Account
- Navigate to CrewAI AMP Integrations
- Find Linear in the Authentication Integrations section
- Click Connect and complete the OAuth flow
- Grant the necessary permissions for issue and project management
- Copy your Enterprise Token from Integration Settings
2. Install Required Package
3. Environment Variable Setup
To use integrations with
Agent(apps=[]), you must set the
CREWAI_PLATFORM_INTEGRATION_TOKEN environment variable with your Enterprise
Token..env file:
Available Actions
linear/create_issue
linear/create_issue
Description: Create a new issue in Linear.Parameters:
teamId(string, required): Team ID - Specify the Team ID of the parent for this new issue. Use Connect Portal Workflow Settings to allow users to select a Team ID. (example: “a70bdf0f-530a-4887-857d-46151b52b47c”).title(string, required): Title - Specify a title for this issue.description(string, optional): Description - Specify a description for this issue.statusId(string, optional): Status - Specify the state or status of this issue.priority(string, optional): Priority - Specify the priority of this issue as an integer.dueDate(string, optional): Due Date - Specify the due date of this issue in ISO 8601 format.cycleId(string, optional): Cycle ID - Specify the cycle associated with this issue.additionalFields(object, optional): Additional Fields.
linear/update_issue
linear/update_issue
Description: Update an issue in Linear.Parameters:
issueId(string, required): Issue ID - Specify the Issue ID of the issue to update. (example: “90fbc706-18cd-42c9-ae66-6bd344cc8977”).title(string, optional): Title - Specify a title for this issue.description(string, optional): Description - Specify a description for this issue.statusId(string, optional): Status - Specify the state or status of this issue.priority(string, optional): Priority - Specify the priority of this issue as an integer.dueDate(string, optional): Due Date - Specify the due date of this issue in ISO 8601 format.cycleId(string, optional): Cycle ID - Specify the cycle associated with this issue.additionalFields(object, optional): Additional Fields.
linear/get_issue_by_id
linear/get_issue_by_id
Description: Get an issue by ID in Linear.Parameters:
issueId(string, required): Issue ID - Specify the record ID of the issue to fetch. (example: “90fbc706-18cd-42c9-ae66-6bd344cc8977”).
linear/get_issue_by_issue_identifier
linear/get_issue_by_issue_identifier
Description: Get an issue by issue identifier in Linear.Parameters:
externalId(string, required): External ID - Specify the human-readable Issue identifier of the issue to fetch. (example: “ABC-1”).
linear/search_issue
linear/search_issue
Description: Search issues in Linear.Parameters:
queryTerm(string, required): Query Term - The search term to look for.issueFilterFormula(object, optional): A filter in disjunctive normal form - OR of AND groups of single conditions.Available fields:title,number,project,createdAtAvailable operators:$stringExactlyMatches,$stringDoesNotExactlyMatch,$stringIsIn,$stringIsNotIn,$stringStartsWith,$stringDoesNotStartWith,$stringEndsWith,$stringDoesNotEndWith,$stringContains,$stringDoesNotContain,$stringGreaterThan,$stringLessThan,$numberGreaterThanOrEqualTo,$numberLessThanOrEqualTo,$numberGreaterThan,$numberLessThan,$dateTimeAfter,$dateTimeBefore
linear/delete_issue
linear/delete_issue
Description: Delete an issue in Linear.Parameters:
issueId(string, required): Issue ID - Specify the record ID of the issue to delete. (example: “90fbc706-18cd-42c9-ae66-6bd344cc8977”).
linear/archive_issue
linear/archive_issue
Description: Archive an issue in Linear.Parameters:
issueId(string, required): Issue ID - Specify the record ID of the issue to archive. (example: “90fbc706-18cd-42c9-ae66-6bd344cc8977”).
linear/create_sub_issue
linear/create_sub_issue
Description: Create a sub-issue in Linear.Parameters:
parentId(string, required): Parent ID - Specify the Issue ID for the parent of this new issue.teamId(string, required): Team ID - Specify the Team ID of the parent for this new sub-issue. Use Connect Portal Workflow Settings to allow users to select a Team ID. (example: “a70bdf0f-530a-4887-857d-46151b52b47c”).title(string, required): Title - Specify a title for this issue.description(string, optional): Description - Specify a description for this issue.additionalFields(object, optional): Additional Fields.
linear/create_project
linear/create_project
Description: Create a new project in Linear.Parameters:
teamIds(object, required): Team ID - Specify the team ID(s) this project is associated with as a string or a JSON array. Use Connect Portal User Settings to allow your user to select a Team ID.projectName(string, required): Project Name - Specify the name of the project. (example: “My Linear Project”).description(string, optional): Project Description - Specify a description for this project.additionalFields(object, optional): Additional Fields.
linear/update_project
linear/update_project
Description: Update a project in Linear.Parameters:
projectId(string, required): Project ID - Specify the ID of the project to update. (example: “a6634484-6061-4ac7-9739-7dc5e52c796b”).projectName(string, optional): Project Name - Specify the name of the project to update. (example: “My Linear Project”).description(string, optional): Project Description - Specify a description for this project.additionalFields(object, optional): Additional Fields.
linear/get_project_by_id
linear/get_project_by_id
Description: Get a project by ID in Linear.Parameters:
projectId(string, required): Project ID - Specify the Project ID of the project to fetch. (example: “a6634484-6061-4ac7-9739-7dc5e52c796b”).
linear/delete_project
linear/delete_project
Description: Delete a project in Linear.Parameters:
projectId(string, required): Project ID - Specify the Project ID of the project to delete. (example: “a6634484-6061-4ac7-9739-7dc5e52c796b”).
linear/search_teams
linear/search_teams
Description: Search teams in Linear.Parameters:
teamFilterFormula(object, optional): A filter in disjunctive normal form - OR of AND groups of single conditions.Available fields:id,name
Usage Examples
Basic Linear Agent Setup
Filtering Specific Linear Tools
Project and Team Management
Issue Hierarchy and Sub-task Management
Automated Development Workflow
Troubleshooting
Common Issues
Permission Errors- Ensure your Linear account has necessary permissions for the target workspace
- Verify that the OAuth connection includes required scopes for Linear API
- Check if you have create/edit permissions for issues and projects in the workspace
- Double-check team IDs, issue IDs, and project IDs for correct UUID format
- Ensure referenced entities (teams, projects, cycles) exist and are accessible
- Verify that issue identifiers follow the correct format (e.g., “ABC-1”)
- Use LINEAR_SEARCH_TEAMS to get valid team IDs before creating issues or projects
- Ensure teams exist and are active in your workspace
- Verify that team IDs are properly formatted as UUIDs
- Check that status IDs reference valid workflow states for the team
- Ensure priority values are within the valid range for your Linear configuration
- Verify that custom fields and labels exist before referencing them
- Use ISO 8601 format for due dates and timestamps
- Ensure time zones are handled correctly for due date calculations
- Verify that date values are valid and in the future for due dates
- Ensure search queries are properly formatted and not empty
- Use valid field names in filter formulas:
title,number,project,createdAt - Test simple filters before building complex multi-condition queries
- Verify that operator types match the data types of the fields being filtered
- Ensure parent issue IDs are valid and accessible
- Verify that the team ID for sub-issues matches or is compatible with the parent issue’s team
- Check that parent issues are not already archived or deleted
Getting Help
Need Help?
Contact our support team for assistance with Linear integration setup or
troubleshooting.
