Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Linear

Issue tracking for modern software teams

CategoryProductivity
Authenticationcustom
Version0.6.1
Published scopes0 published scopes
Last updatedSeptember 30, 2026

Overview

Connect Linear with Flows360

Issue tracking for modern software teams

Use the Linear connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 6 actions and 7 triggers.

Available actions

  • Create Issue
  • Update Issue
  • Create Project
  • Update Project
  • Create Comment
  • Raw GraphQL query

Available triggers

  • New Comment
  • New Issue
  • Updated Issue
  • Removed Issue
  • New Project
  • Project Status Updated
  • Plus 1 additional declared trigger.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Linear
  • Package: @activepieces/piece-linear@0.6.1
  • Exact artifact digest: sha256:85deef83edaee1b3cef877e905512070c4608617c8ab23481e7dac3e7b4d3bb8
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Issue (linear_create_issue), Create a new issue in Linear workspace Classification: read.
  • Update Issue (linear_update_issue), Update a issue in Linear Workspace Classification: read.
  • Create Project (linear_create_project), Create a new project in Linear workspace Classification: read.
  • Update Project (linear_update_project), Update a existing project in Linear workspace Classification: read.
  • Create Comment (linear_create_comment), Create a new comment on an issue in Linear workspace Classification: read.
  • Raw GraphQL query (rawGraphqlQuery), Perform a raw GraphQL query Classification: read.

Trigger contracts

  • New Comment, webhook.
  • New Issue, webhook.
  • Updated Issue, webhook.
  • Removed Issue, webhook.
  • New Project, webhook.
  • Project Status Updated, webhook.
  • Removed Project, webhook.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

Authenticationcustom
Supported objects13
Supported actions6
Triggers7

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Issue Yes No Create a new issue in Linear workspace
Update Issue Yes No Update a issue in Linear Workspace
Create Project Yes No Create a new project in Linear workspace
Update Project Yes No Update a existing project in Linear workspace
Create Comment Yes No Create a new comment on an issue in Linear workspace
Raw GraphQL query Yes No Perform a raw GraphQL query
New Comment Yes No webhook trigger declared by the pinned package.
New Issue Yes No webhook trigger declared by the pinned package.
Updated Issue Yes No webhook trigger declared by the pinned package.
Removed Issue Yes No webhook trigger declared by the pinned package.
New Project Yes No webhook trigger declared by the pinned package.
Project Status Updated Yes No webhook trigger declared by the pinned package.
Removed Project Yes No webhook trigger declared by the pinned package.

Supported actions

Create Issue · Read

Create a new issue in Linear workspace

linear_create_issue · Risk: low · Retry: safe

Inputs

  • team_id · string · Required, The team for which the issue, project or comment will be created
  • title · string · Required
  • description · string · Optional
  • state_id · string · Optional, Status of the Issue
  • labels · array · Optional, Labels for the Issue
  • assignee_id · string · Optional, Assignee of the Issue / Comment
  • priority_id · string · Optional, Priority of the Issue
  • template_id · string · Optional, ID of Template
Update Issue · Read

Update a issue in Linear Workspace

linear_update_issue · Risk: low · Retry: safe

Inputs

  • team_id · string · Required, The team for which the issue, project or comment will be created
  • issue_id · string · Required, ID of Linear Issue
  • title · string · Optional
  • description · string · Optional
  • state_id · string · Optional, Status of the Issue
  • labels · array · Optional, Labels for the Issue
  • assignee_id · string · Optional, Assignee of the Issue / Comment
  • priority_id · string · Optional, Priority of the Issue
Create Project · Read

Create a new project in Linear workspace

linear_create_project · Risk: low · Retry: safe

Inputs

  • team_id · string · Required, The team for which the issue, project or comment will be created
  • name · string · Required
  • description · string · Optional
  • icon · string · Optional
  • color · string · Optional
  • startDate · string · Optional
  • targetDate · string · Optional
  • state · string · Optional, The status of the project
Update Project · Read

Update a existing project in Linear workspace

linear_update_project · Risk: low · Retry: safe

Inputs

  • team_id · string · Required, The team for which the issue, project or comment will be created
  • project_id · string · Required, ID of Linear Project
  • name · string · Required
  • description · string · Optional
  • icon · string · Optional
  • color · string · Optional
  • startDate · string · Optional
  • targetDate · string · Optional
  • state · string · Optional, The status of the project
Create Comment · Read

Create a new comment on an issue in Linear workspace

linear_create_comment · Risk: low · Retry: safe

Inputs

  • team_id · string · Required, The team for which the issue, project or comment will be created
  • user_id · string · Optional, Assignee of the Issue / Comment
  • issue_id · string · Required, ID of Linear Issue
  • body · string · Required, The content of the comment
Raw GraphQL query · Read

Perform a raw GraphQL query

raw_graphql_query · Risk: low · Retry: safe

Inputs

  • query · string · Required
  • variables · object · Optional

Triggers

New Comment · Webhook

Triggers when a new comment is created on a Linear issue

Inputs

  • team_ids · array
  • author_ids · array
New Issue · Webhook

Triggers when Linear receives a new issue

Inputs

  • team_id · string
Updated Issue · Webhook

Triggers when an existing Linear issue is updated

Inputs

  • team_id · string
  • changed_fields · array
Removed Issue · Webhook

Triggers when an existing Linear issue is removed

Inputs

  • team_id · string
New Project · Webhook

Triggers when a new project is created in Linear

Project Status Updated · Webhook

Triggers when the status of an Linear project is updated

Inputs

  • team_ids · array
  • project_status · string
Removed Project · Webhook

Triggers when an existing Linear project is removed

Setup

Setup

  1. Add the Linear connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-linear@0.6.1; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 6 actions and 7 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Runtime execution evidence is managed separately from package metadata.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Linear connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-linear@0.6.1 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com