Create a Linear issue from a GitHub issue

This recipe creates a Linear issue when GitHub sends an issues webhook with the opened action.

GitHub Issues Trigger → Filter action = opened → Linear Create Issue

Before you begin

• Install the FastHook GitHub App for the required repository or organization.
• Connect the Linear workspace and confirm the account can create issues in the target team.
• Decide whether every opened GitHub issue should be copied or only selected repositories, labels, or authors.

1. Create the GitHub Trigger

1. Create a GitHub Source from New Workflow.
2. Choose the Issues event definition.
3. Restrict repositories when the installation contains more than the Workflow needs.
4. If the Source dialog exposes an Actions filter, set it to opened.
5. Create the Workflow with an outcome-oriented name such as Create Linear issues from GitHub support repo.

The Trigger sample and real payload expose fields such as:

{
  "action": "opened",
  "repository": { "full_name": "example/support" },
  "sender": { "login": "octocat" },
  "issue": { "number": 123, "title": "Checkout fails" }
}

2. Protect against non-opened actions

GitHub uses the same issues webhook type for opened, edited, closed, reopened, assigned, labeled, and other actions. If the Source is not already restricted, insert a Filter:

trigger.action exactly matches opened

This prevents an edit or label change from creating another Linear issue.

3. Add Linear Create Issue

1. Add Linear → Create Issue after the Filter.
2. Select the Linear account and Team.
3. Optionally select a Project, Assignee, State, and priority from 0 through 4.
4. Map the required Title and optional Description.

Suggested title:

[{{trigger.repository.full_name}} #{{trigger.issue.number}}] {{trigger.issue.title}}

Suggested description:

Created from GitHub by {{trigger.sender.login}}.

{{trigger.issue.body}}

GitHub: {{trigger.issue.html_url}}

Use the field picker. Some optional fields, including body or URL, may not appear in the generic sample until a real issue event has been received.

4. Activate and test

Activate the Workflow and open one test issue in an allowed repository. In Audit, verify that the Filter continued, the Linear mapped input is correct, and the Action output identifies the created issue.

Then edit the GitHub issue. The new GitHub event should produce a run in which the Filter stops the Linear branch rather than creating a duplicate.

Production hardening

• Add filters for repository, label, or sender when the Source subscription must remain broad.
• Include the GitHub issue number or URL in Linear so operators can correlate records.
• Before replaying a failed run, search Linear for an issue that may have been created even if the response was lost.
• Add an error route that alerts on Linear permission, validation, or rate-limit failures.
• Use a separate Workflow for GitHub issue updates instead of overloading the create path.

See Connected accounts for GitHub installation and Linear permission troubleshooting.