All GitHub integrationsIntegration

GitHub and Linear

Start a workflow in one and act in the other, with every step on the record. Ask your AI for it, or build it yourself.

GitHub steps
31
Linear steps
10

Ideas for GitHub and Linear

Each one is a real trigger and action. Ask your AI for any of them, in your own words, and it builds the workflow.

  • WhenNew pull requestThenCreate an issue
  • WhenNew issueThenCreate branch
  • WhenUpdated pull requestThenUpdate issue state
  • WhenIssue changedThenCreate comment
  • WhenNew issueThenAdd a comment to an issue
  • WhenNew issueThenCreate issue

What each app adds

GitHub

Triggers

  • New pull requestRuns when a pull request is opened in a GitHub repository.
  • Updated pull requestRuns when a pull request in a GitHub repository is updated.
  • New issueRuns when an issue is opened in a GitHub repository.
  • Updated issueRuns when an issue in a GitHub repository is updated.
  • Label added to an issueRuns when a label is added to an issue in a GitHub repository, whether the issue was just opened with it or labelled later, such as when a bug is triaged. Each label starts a run once per issue. Labels an issue already had when the workflow was turned on don't start it.
  • New push to branchRuns for each new commit pushed to a branch of a GitHub repository.

Actions

  • Create branchCreate a new branch in a repository. Points the new branch at the tip of an existing branch (defaults to the repository's default branch) unless you supply a specific commit SHA.
  • Delete branchDelete a branch from a repository.
  • Get branchGet details of a specific branch, including its latest commit SHA.
  • Create commentAdd a comment to an issue or pull request. Use the issue or pull request number, since both share the same numbering.
  • Create issueCreate a new issue in a repository.
  • Get issueGet details of a specific issue.
See all 31 on the GitHub page

Linear

Triggers

  • New issueRuns when a new issue is created in a Linear team.
  • Issue changedRuns when an issue in a Linear team changes, such as its status, assignee or priority, and when one is created. Changes made before the workflow is turned on don't start it.

Actions

  • List teamsFetch available Linear teams for the connected workspace.
  • Create an issueCreate a new Linear issue with optional project, description, priority, and assignee.
  • Update issue stateMove a Linear issue to a different workflow state, such as Todo or Done, using the new state's ID.
  • Add a comment to an issuePost a comment on a Linear issue thread.
  • List issues for a teamFetch the latest Linear issues for a specific team.
  • Get issue detailsRetrieve detailed information for a Linear issue.
See all 10 on the Linear page

How to connect GitHub and Linear

  1. Connect your AI

    Add Lodol to Claude, ChatGPT, Cursor or any MCP tool in one step, or open the editor.

  2. Connect GitHub and Linear

    Sign in to each once in your workspace. Their keys are encrypted and used by name.

  3. Describe it, then turn it on

    Say what should happen, and when. Try a run, then turn it on; every run is traced.

Questions about GitHub and Linear

Yes. Connect each app once in your Lodol workspace and any workflow can use both: 22 actions and 9 triggers in GitHub, and 8 actions and 2 triggers in Linear.

Ask Claude, ChatGPT, Cursor or any AI tool connected to Lodol, in your own words, and it builds the workflow in your workspace. Or add the steps yourself in the visual editor, or start from one of the 1 template that already use both.

Free includes 100 runs a month. Builder starts at $18 a month for 2,500 runs and Pro at $120 for 10,000, and every plan has unlimited seats. A run counts once, however many steps it takes.

Connect GitHub and Linear.

Ask for it in Slack, Claude or ChatGPT. Lodol does it every time, and tells you if anything breaks.

Free plan, no credit card