Integrations

What this is

This section explains how Hookshot connections work and how to reason about integration setup.

When to use it

Use this section when you are connecting an app for the first time or repairing one that is no longer ready.

What you need first

• Permission to manage integrations in your workspace

• Access to the external app you want to connect

Steps

1. Understand the two kinds of access

• Trigger Access: what can start a Protege

• Tool Access: what a Protege can do after it starts

2. Review the integration lifecycle

1. Open the integration

2. Connect the app

3. Review Trigger Access

4. Review Tool Access

5. Verify the setup with a real event or schedule

3. Use a consistent verification loop

For every integration:

• Confirm the connection is active

• Confirm the right trigger source is live

• Confirm the right tools are available

• Confirm Event Feed receives the event

• Confirm Audit shows the run

Engineer note: The safest way to verify an integration is end-to-end. A healthy connection screen alone does not prove that the event path and action path are both working.

How to verify

You are ready to move on when you can answer:

• What will start this Protege?

• What will this Protege do with the integration?

• Where will I verify that behavior?

Common failures

• Approving the connection but not checking trigger scope

• Using the wrong connected account or workspace

• Assuming one integration connection covers every team or project boundary

Next step

• Slack

• GitHub

• Linear

• Asana