GitHub logo
Linear logo

Workflow template

Create Linear tasks from new GitHub issues

Create a Linear triage issue when a new GitHub issue is opened in selected repositories. Keep the issue number, title, repository, author, creation time and source link without copying the body, comments or attachments.

How it works

From a GitHub issue opening to a Linear triage item

1 Trigger · 1 Action
GitHub1 · Trigger

Issues

Receive GitHub issue webhook events with Actions prefilled to opened. Select repositories; leaving that selection empty watches every repository granted to the GitHub App installation.

Linear2 · Action

Create the GitHub triage issue

Create an issue in the selected Linear team with [#number] in its title and source metadata/link in its description. No project, assignee or labels are mapped; the team’s normal initial state applies.

The result

A Linear issue linked to the original GitHub report

Example Linear GitHub triage issue

[#42] Improve the project onboarding checklist

Repository: example-studio/project-tracker GitHub issue: #42 Opened by: alex-example Created: 2026-09-15T10:00:00Z Open original issue: https://github.com/example-studio/project-tracker/issues/42 Issue body, comments, and attachments stay in GitHub.

Source-sample title and mapped description. No Linear identifier or state is invented; the destination team must be selected before use.

Before activation

Set up your workflow

  1. Choose the GitHub repositories and opened action

    Connect the FastHook GitHub App and choose the source repositories. Keep Actions set to opened. An empty repository selection includes all repositories granted to the installation.

  2. Select the Linear triage team

    Connect Linear and choose a destination team. Review its members and initial-state defaults; the recipe does not choose a project or assignee.

  3. Wait for Instant before opening a test issue

    Activate and wait for Instant, then open a fictional issue in a repository you control. Verify the number/title and metadata link in Linear and check source access separately.

Details and limitations
  • Only new issue openings create triage items. Existing issues, pull requests, later edits, closures and reopenings are not synchronized. The recipe provides one-way creation without status or comment updates.

  • Bodies and attachments stay in GitHub. Only the issue title, number and repository/author/time/link metadata are mapped. Destination team members can read these values, while the link still requires their own GitHub access. Source text and Markdown pass through as supplied.

  • New runs create new Linear issues. No source-ID upsert or project/assignee mapping is configured. Reruns or ambiguous provider failures can create duplicates, and provider limits apply.

Questions about this template

What if I leave Repositories empty?

The source watches all repositories granted to the GitHub App installation. Select specific repositories if the Linear intake team should receive only a subset.

Are issue bodies, comments or pull requests copied?

No. The title and source metadata/link are copied for newly opened issues. Bodies, attachments, comments, assignees and labels stay in GitHub; pull requests are outside this recipe.

Which Linear project, assignee and state will be used?

Choose the Linear team. The recipe does not select a project or assignee, and the team’s normal initial issue state applies. Add your own mappings if you need a different intake process.

Will closing or reopening GitHub update the Linear issue?

No. The opened action creates a new issue once the source is active. Later edits, closures and reopenings are not synchronized; rerunning an event can create another Linear issue.

Explore connected apps