Using Linear actions in action flows


Linear is an issue tracking and project management tool built for software teams. With the Linear connector for action builder, you can create and manage issues, projects, and comments, search for issues and users, and keep your team's work organized directly from your Zendesk action flows.


What's my plan?







All Suites

Team, Growth, Professional, Enterprise, or Enterprise Plus










Support

Team, Professional, or Enterprise







Summary: ◀▼
You can connect your action flows to Linear to create, update, and manage issues, projects, and comments directly within your workflows. This integration supports searching and looking up issues and users, assigning issues, and organizing projects, helping you streamline project management and issue tracking without switching platforms. Use a dedicated service account for secure and attributed external actions.




By connecting the action builder to external systems, such as Linear, admins
can integrate Zendesk with external systems in automated workflows, improving
collaboration and maintaining a seamless experience across multiple platforms.
Note: The steps associated with external systems in action flows are
referred to collectively as external actions.

Linear is an issue tracking and project management tool built for software teams. With
the Linear connector for action builder, you can create and manage issues, projects, and
comments, search for issues and users, and keep your team's work organized directly from
your Zendesk action flows.
This article contains the following topics:
Connecting Linear to action builder
Using Linear actions in action flows




Connecting Linear to action builder

Before you can include external actions in your action flows, you must connect the
action builder to the external system.
When connecting to external systems for use in action flows, the following best practices are recommended:
All external actions performed by an action flow are attributed to the user who connected the
external system. Therefore, it's a best practice to use a dedicated service
account rather than personal credentials when connecting to each external
system.
All integrations request access to necessary scopes. However, it's important that you review and validate the scopes before authorizing the connection to the external system.
When managing credentials for API key-based tools, such as OpenAI, it's best to store keys in a secure vault or credential manager.



To connect action builder to Linear
In Admin Center, click
Apps and integrations in the sidebar, then select Actions > Action
flows.

Create or edit an action flow.
Open the step sidebar.
Under External actions, click Linear.
Click Connect.
Follow Linear's prompts to authenticate and complete the connection. The
Linear connection uses OAuth 2.0 with the authorization code grant type.
When you authorize the connection, you'll be redirected to Linear to
grant permissions to your Zendesk account.

Note: All external actions performed by an action flow
are attributed to the user who connected the external system. Therefore,
it is a best practice to use a dedicated service account rather than
personal credentials when connecting to each external
system.



After you've connected to the system, you'll see an indicator that it's connected and
details about the instance you're connected to, as well as the actions available for
Linear.



Using Linear actions in action flows

Linear action steps can be used to look up forms and search for survey responses.
The following Linear actions are available:
Create issue
Update issue
Lookup issue
Search issues
Add comment to
issue
Lookup user
Search users
Create project
Update project
Add issue to
project
Assign issue to a
member




Creating an issue

Use the Create issue action to create a new issue in Linear with specified
details.
This action has the following inputs and outputs:










Variables




Inputs
Required: Title,
Team Optional:
Description,
Project, Assignee
email, Status,
Priority, Due
date, Estimate

Note: Due date should be entered in
YYYY-MM-DD format based on your Linear account's
timezone. Priority options include: No priority, Urgent,
High, Medium, or Low.



Output
Issue details, including ID, identifier, title,
description, URL, project information, assignee information,
status information, priority, due date, estimate, and
timestamps








Updating an issue

Use the Update issue action to update an existing issue's properties in
Linear.
This action has the following inputs and outputs:










Variables




Inputs
Required: Issue Optional:
Title,
Description, Assignee
email, Project,
Status, Priority,
Due date,
Estimate

Note: Due date should be entered in YYYY-MM-DD format based
on your Linear account's timezone.



Output
Updated issue details, including ID, identifier, title,
description, URL, assignee information, status information,
priority, due date, estimate, and update timestamp








Looking up an issue

Use the Lookup issue action to retrieve detailed information about a
specific issue.
This action has the following inputs and outputs:










Variables




Inputs
Required: Issue ID



Output
Issue details, including ID, identifier, title,
description, URL, project information, assignee information,
status information, priority, due date, estimate, and
timestamps








Searching issues

Use the Search issues action to find issues based on various criteria.
This action has the following inputs and outputs:










Variables




Inputs
Optional: Team,
Project, Assignee email,
Status, Order by,
Limit, Cursor



Output
Array of issues with ID, identifier, title, URL, status
information, assignee information, priority, and creation
timestamp; also includes pagination information
(hasNextPage, endCursor)








Adding a comment to an issue

Use the Add comment to issue action to add a comment to an existing
issue.
This action has the following inputs and outputs:










Variables




Inputs
Required: Issue,
Body



Output
Comment details, including ID, body text, author
information (ID and name), and creation timestamp








Looking up a user

Use the Lookup user action to retrieve user information by email or
display name.
This action has the following inputs and outputs:










Variables




Inputs
Required: Lookup by,
Value



Output
User details, including ID, name, display name, email,
avatar URL, and profile URL








Searching users

Use the Search users action to find users matching a search query.
This action has the following inputs and outputs:










Variables




Inputs
Required: Query Optional:
Limit,
Cursor



Output
Array of users with ID, name, display name, email, and
avatar URL; also includes pagination information
(hasNextPage, endCursor)








Creating projects

Use the Create project action to create a new project in Linear.
This action has the following inputs and outputs:










Variables




Inputs
Required: Name,
Team Optional:
Description, Start
date, End date

Note: Start date and End date should be
entered in YYYY-MM-DD format based on your Linear
account's timezone.



Output
Project details, including ID, name, description, URL,
team information (ID and name), start date, end date, and
creation timestamp








Updating projects

Use the Update project action to update an existing project's
properties.
This action has the following inputs and outputs:










Variables




Inputs
Required: Project Optional:
Name, Description,
Start Date, End
Date

Note: Start
date and End date should be entered in YYYY-MM-DD format
based on your Linear account's timezone.



Output
Updated project details, including ID, name, description,
URL, start date, end date, and update timestamp








Adding an issue to a project

Use the Add issue to project action to assign an existing issue to a
project.
This action has the following inputs and outputs:










Variables




Inputs
Required: Issue,
Project



Output
Issue details, including ID, identifier, title, URL, and
project information (ID and name)








Assigning an issue to a member

Use the Assign issue to member action to assign an issue to a team member
by email.
This action has the following inputs and outputs:










Variables




Inputs
Required: Issue, Assignee
email



Output
Issue details, including ID, identifier, title, URL, and
assignee information (ID and name)








{
"@context": "https://schema.org",
"@type": "TechArticle",
"@id": "https://support.zendesk.com/hc/en-us/articles/10630901754522-Using-Linear-actions-in-action-flows",
"url": "https://support.zendesk.com/hc/en-us/articles/10630901754522-Using-Linear-actions-in-action-flows",
"headline": "Using Linear actions in action flows",
"description": "You can connect the action builder to Linear to create, update, and manage issues and projects within automated workflows, enabling integration with an external issue tracking system.",
"articleSection": "Extending Zendesk",
"datePublished": "2026-05-01T00:44:19+00:00",
"dateModified": "2026-05-01T20:48:12.408033+00:00",
"inLanguage": "en-US",
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://support.zendesk.com/hc/en-us/articles/10630901754522-Using-Linear-actions-in-action-flows"
},
"author": {
"@type": "Organization",
"name": "Zendesk",
"url": "https://www.zendesk.com"
},
"publisher": {
"@type": "Organization",
"name": "Zendesk"
},
"isPartOf": {
"@type": "WebSite",
"name": "Zendesk Help",
"url": "https://support.zendesk.com/hc/en-us"
},
"about": {
"@type": "SoftwareApplication",
"name": "Zendesk"
}
}
//
const ai_summary_style = document.createElement('style');
ai_summary_style.innerHTML = `#styled-article-body{padding:0 0 0}#article-body #docs-ai-summary{background-color:#f3f3f3;border:1px solid #d3d3d3;padding:10px 10px 6px;margin-bottom:16px}#article-body #docs-ai-summary #docs-ai-summary-toggle{font-size:.9em;font-weight:700;margin-bottom:4px;cursor:pointer;display:flex;justify-content:space-between;align-items:center}#article-body #docs-ai-summary #docs-ai-summary-toggle #up-triangle{margin-left:auto;padding-right:10px;display:none}#article-body #docs-ai-summary #docs-ai-summary-toggle #down-triangle{margin-left:auto;padding-right:10px}#article-body #docs-ai-summary #docs-ai-summary-content{font-size:.9em;padding-left:25px;padding-right:25px;margin-bottom:12px}`;
document.head.appendChild(ai_summary_style);

const toggleAISummary = () => {
const summary = document.getElementById("docs-ai-summary-content");
const upTriangle = document.getElementById("up-triangle");
const downTriangle = document.getElementById("down-triangle");
if (summary.style.display === "none") {
summary.style.display = "block";
upTriangle.style.display = "none";
downTriangle.style.display = "inline";
} else {
summary.style.display = "none";
upTriangle.style.display = "inline";
downTriangle.style.display = "none";
}
};

document.getElementById("docs-ai-summary-toggle").addEventListener("click", toggleAISummary);
//

