Linear Integration — Automate Linear with AI on Beauto
Linear is a streamlined issue tracking and project planning tool for modern teams, featuring fast workflows, keyboard shortcuts, and GitHub integrations
Category: project management, task management · 46 actions available
What you can automate with Linear
Beauto connects Linear with 900+ other apps so you can build AI-powered workflows in minutes. Trigger automations from Linear events, enrich Linear data with AI, or sync Linear with the rest of your stack — without writing code.
- Sync Linear data with Gmail, Slack, Notion, HubSpot, Google Sheets, and more
- Trigger AI agents on new Linear events and route the output anywhere
- Schedule recurring Linear tasks — daily reports, cleanups, or bulk updates
- Use natural language to describe the workflow; Beauto builds it for you
Linear actions Beauto supports
- Create attachment — Creates a new attachment and associates it with a specific, existing Linear issue.
- Add reaction to comment — Tool to add a reaction to an existing Linear comment. Use when you want to programmatically react to a comment on an issue.
- Create a comment — Creates a new comment on a specified Linear issue. This action modifies shared workspace data and is not reversible — confirm the target issue and comment content before executing.
- Create linear issue — Creates a new issue in a specified Linear project and team, requiring team_id and title, and allowing optional properties like description, assignee, state, priority, cycle, and due date. All UUID parameters (state_id, a
- Create issue relation — Create a relationship between two Linear issues using the issueRelationCreate mutation. Use this to establish connections like 'blocks', 'duplicate', or 'related' between issues.
- Create a label — Creates a new label in Linear for a specified team, used to categorize and organize issues. Label names must be unique within each team. If a label with the same name already exists, the existing label will be returned.
- Create Project — Creates a new Linear project with specified name and team associations.
- Create Project Milestone — Tool to create a project milestone in Linear with a name and optional target date and sort order. Use when you need to add milestones to track progress within a project.
- Create Project Update — Tool to create a project status update post for a Linear project. Use when you need to post progress updates, status reports, or announcements for a project.
- Delete issue — Archives an existing Linear issue by its ID, which is Linear's standard way of deleting issues; the operation is idempotent. Archiving is permanent with no built-in undo — confirm the issue identifier and title with the
- Download issue attachments — Downloads a specific attachment from a Linear issue; the `file_name` must include the correct file extension.
- Get current user — Gets the currently authenticated user's ID, name, email, and other profile information — this is the account behind the API token, which may be a bot or service account rather than a human user. Use the returned `id` fie
- Get cycles by team ID — Retrieves all cycles for a specified Linear team ID; cycles are time-boxed work periods (like sprints). Results are team-scoped to the given team_id. To identify the active cycle, check that the current date (in UTC) fal
- Get create issue default params — Fetches a Linear team's default issue estimate and state, useful for pre-filling new issue forms.
- Get Linear issue — Retrieves an existing Linear issue's comprehensive details, including id, identifier, title, description, timestamps, state, team, creator, attachments, comments (with user info and timestamps, use issue.comments.nodes f
- Get Linear project — Retrieves a single Linear project by its unique identifier. Use when verifying a newly created or updated project, or when fetching detailed project information by ID.
- List issue drafts — Tool to list issue drafts. Use when you need to fetch draft issues for review or further editing. Check `pageInfo.hasNextPage` in the response to determine if additional drafts exist beyond the current page.
- List issues by team ID — Tool to list all issues for a specific Linear team, scoped by team ID. Use when you need to retrieve issues belonging to a particular team without fetching workspace-wide issues. This is more efficient than workspace-wid
- Get all cycles — Retrieves all cycles (time-boxed sprint iterations) org-wide from the Linear account; no filters applied. In large multi-team workspaces this produces heavy responses — filter client-side by team ID and date range using
- List Linear issues — Lists non-archived Linear issues; if project_id is not specified, issues from all accessible projects are returned. Can filter by assignee_id. Only project_id and assignee_id server-side filters are supported; label, sta
- Get labels — Retrieves labels from Linear. If team_id is provided, returns labels for that specific team; if omitted, returns all labels across the workspace. Label names are not unique across teams — always use returned IDs, not nam
- List linear projects — Retrieves all projects from the Linear account. Returns a flat array (not a GraphQL connection) with fields id and name; use LINEAR_RUN_QUERY_OR_MUTATION for progress, state, issues, or team linkage. No server-side filte
- List Linear states — Retrieves all workflow states for a specified team in Linear, representing the stages an issue progresses through in that team's workflow. Returned state IDs are team-scoped — never reuse a stateId across different teams
- Get teams — Retrieves all teams with their members and projects. Use stable team IDs or keys (not display names) for subsequent operations — names are non-unique. Results reflect only teams visible to the authenticated token scope;
- List Linear users — Lists all workspace users (not team-scoped) with their IDs, names, emails, and active status. Display names are non-unique — use email to disambiguate before extracting an ID. Only assign users with `active: true`. Retur
- Remove label from Linear issue — Removes a specified label from an existing Linear issue using their IDs; successful even if the label isn't on the issue. Operation is irreversible — obtain explicit user approval before executing. Use this tool instead
- Remove reaction from comment — Tool to remove a reaction on a comment. Use when you have a reaction ID and need to delete it.
- Run Query or Mutation — Execute any GraphQL query or mutation against Linear's API. USE WHEN: No dedicated action exists, need complex filtering, custom fields, or schema discovery. *** INTROSPECTION FIRST - NEVER GUESS FIELD NAMES *** Run intr
- Search Linear issues — Search Linear issues using full-text search across identifier, title, and description. Use when you need to find issues by keywords or specific identifiers. Note: This endpoint only supports full-text search; for structu
- Update issue — Updates an existing Linear issue using its `issue_id`; requires at least one other attribute for modification, and all provided entity IDs (for state, assignee, labels, etc.) must be valid UUIDs — only `issueId` accepts
- Update a comment — Tool to update an existing Linear comment's body text. Use when you need to edit or modify the content of a previously created comment.
- Update Project — Tool to update an existing Linear project. Use when you need to modify project properties like name, description, state, dates, or lead. All fields except project_id are optional - only provide the fields you want to upd
Linear triggers
- Comment Received Trigger — Triggered when a comment is received.
- Issue Created Trigger — Triggered when a new issue is created.
- Issue Updated Trigger — Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.