Linear

What this integration can do

Linear commonly serves as:

• A source of issue activity

• A system of record for operational workflows

• A target for Proteges that summarize, triage, or enrich work

Prerequisites

• Access to the Linear workspace, team, or project you want to automate

• Permission to complete the connection flow

• A clear boundary for the workflow

Connect

1. Open Integrations.

2. Select Linear.

3. Complete the connection flow.

4. Confirm the integration is connected.

Trigger Access

Use Trigger Access when Linear should start the Protege.

Examples:

• A new issue in a selected team

• Another configured Linear activity pattern

Tool Access

Use Tool Access when the Protege should read or support work based on Linear data.

Examples:

• Retrieve issue context

• Route work to another destination

• Support issue-based review workflows

Permissions and scopes

Review the connection scope carefully. In practice, Hookshot needs permission to:

• Observe the Linear items that should start the workflow

• Access enough issue context to support the intended action

Keep the scope limited to the relevant team or project whenever possible.

How to verify

• Confirm Linear shows as connected

• Confirm the intended trigger source is available and ready

• Create a safe test item in the selected team or project

• Check Event Feed for the incoming activity

• Check Audit for the resulting run

Common mistakes

• Using the wrong Linear team boundary

• Connecting Linear successfully but not validating the trigger source

• Assuming every issue type should activate the same Protege

Troubleshooting

• If the test issue does not appear in Event Feed, review Trigger Access and the selected connection.

• If the issue appears but the Protege is unevaluated or skipped, review the Protege design and live source mapping.

• If the Protege runs but does not produce the expected downstream result, inspect the destination integration in Audit.