LINEAR n8n INTEGRATION: AUTOMATE LINEAR WITH N8N

Creating issues programmatically is the foundation of most Linear automation workflows. This action lets you automatically generate new issues in any of your Linear teams, complete with titles, descriptions, and any additional properties you need.

Key parameters:

• Credential to connect with: Select your authenticated Linear account from the dropdown—this is required to establish the API connection
• Resource: Set to "Issue" to work with Linear issues
• Operation: Set to "Create" to generate new issues
• Team Name or ID: Specify which team should own the issue—enter the team identifier or name (required)
• Title: The issue title that will appear in Linear—supports both fixed text and dynamic expressions
• Additional Fields: Expandable section for optional properties like description, priority, labels, assignee, and more

Use cases:

• Automatically create bug reports when error monitoring tools like Sentry detect new issues
• Generate feature request issues from customer feedback forms
• Create onboarding task issues when new team members join via your HR system
• Transform Slack messages into trackable Linear issues with a simple workflow trigger

This action is perfect for teams that want to centralize issue creation from multiple sources while maintaining consistent formatting and team assignment.

When you need to retrieve detailed information about a specific issue, this action fetches all data associated with a single Linear issue using its unique identifier. It's essential for workflows that need to check issue status, pull descriptions for notifications, or verify issue existence before performing other operations.

Key parameters:

• Credential to connect with: Dropdown to select your Linear account credential for API authentication (required)
• Resource: Set to "Issue" to target Linear issues
• Operation: Set to "Get" to retrieve a single issue's data
• Issue ID: Text field where you enter the unique identifier of the issue you want to fetch (required)

Use cases:

• Pull issue details to include in Slack notifications or email updates
• Check if an issue exists before attempting to update it
• Retrieve issue data for syncing with external project management tools like Asana or ClickUp
• Fetch issue information to populate reports or dashboards

This action returns comprehensive issue data including title, description, status, assignee, labels, and timestamps—everything you need for downstream workflow steps.

Need to work with multiple issues at once? The "Get Many" action retrieves a batch of issues from Linear, making it ideal for reporting, bulk operations, or syncing issue lists with other systems.

Key parameters:

• Credential to connect with: Dropdown for selecting your Linear account credential (required)
• Resource: Set to "Issue" to fetch issues from Linear
• Operation: Set to "Get Many" to retrieve multiple records
• Return All: Toggle switch that determines whether to fetch all available issues or limit results—turning this off enables the Limit parameter
• Limit: Numeric field that caps the number of issues returned when "Return All" is disabled—default is 50

Use cases:

• Generate weekly issue reports by fetching all issues created in the past 7 days
• Sync your Linear backlog with an external analytics dashboard
• Create automated summaries of open issues for stakeholder updates
• Bulk export issues for migration or archival purposes

💡 Pro tip: Combine this action with n8n's filtering capabilities to narrow down results after retrieval—filter by status, assignee, or any other property to work with exactly the issues you need.

Keeping issues current is just as important as creating them. This action modifies existing issues in Linear, allowing you to update any field—status, title, description, assignee, priority, and more.

Key parameters:

• Credential to connect with: Dropdown to select your Linear account for authentication (required)
• Resource: Set to "Issue" to target issues
• Operation: Set to "Update" to modify existing issues
• Issue ID: Text field for the unique identifier of the issue to update (required)
• Update Fields: Expandable section where you add specific fields to modify—use the "Add Field" button to select which properties to change

Use cases:

• Automatically move issues to "In Review" when pull requests are opened
• Update issue priority based on customer tier or urgency signals
• Change assignees when team capacity shifts or on-call rotations change
• Add or modify descriptions with additional context from other tools

This action is particularly powerful when combined with webhook triggers from other platforms—imagine issues updating their status in real-time based on CI/CD pipeline events or customer support ticket changes.

Sometimes issues need to be removed entirely—duplicates, test entries, or deprecated items. This action permanently deletes an issue from Linear, so use it carefully in your automated workflows.

Key parameters:

• Credential to connect with: Dropdown for Linear account credential selection (required)
• Resource: Set to "Issue" to operate on Linear issues
• Operation: Set to "Delete" to remove issues permanently
• Issue ID: Text field where you specify the exact issue to delete (required)

Use cases:

• Automatically clean up test issues created by QA workflows
• Remove duplicate issues detected by automated deduplication logic
• Delete cancelled or invalid issues based on specific criteria
• Implement data retention policies by archiving and then deleting old issues

Important consideration: Deletions are permanent in Linear. Consider implementing a confirmation step or logging mechanism in your workflow before executing deletions, especially in production environments.

Linking external resources to issues creates valuable context for your team. This action attaches URLs to existing Linear issues—documentation, design files, external tickets, or any web resource that provides relevant information.

Key parameters:

• Credential to connect with: Dropdown for selecting your authenticated Linear account (required)
• Resource: Set to "Issue" to work with issues
• Operation: Set to "Add Link" to attach URLs
• Issue ID: Text field for the identifier of the issue receiving the link (required)
• Link: Text field for the URL you want to attach to the issue (required)

Use cases:

• Automatically link GitHub pull requests to their corresponding Linear issues
• Attach Figma design files when issues are created from design review workflows
• Connect customer support tickets to related bug reports
• Link documentation pages when issues reference specific features

This action helps maintain traceability across your entire toolchain, ensuring that anyone viewing an issue has immediate access to all related resources.

Keep your team informed with automated comments on Linear issues. This action posts comments to specific issues, enabling real-time updates from external systems, status notifications, and cross-platform communication.

Key parameters:

• Credential to connect with: Dropdown for Linear account credential authentication (required)
• Resource: Set to "Comment" to work with issue comments
• Operation: Set to "Add Comment" to post new comments
• Issue ID: Text field for the unique identifier of the issue to comment on (required)
• Comment: Text field where you write the comment content (required)
• Additional Fields: Optional expandable section for extra comment properties

Use cases:

• Post deployment notifications when issues are shipped to production
• Add customer feedback directly to related issues from support platforms like Zendesk or Intercom
• Comment build status updates from CI/CD pipelines
• Notify the team when external dependencies are resolved

Automated comments create a living audit trail on your issues, helping team members stay synchronized without manual status updates.