Quickstart for Power Users

What this is

This quickstart helps a non-technical but high-agency user create a first Protege and confirm that it works.

When to use it

Use this path if you want a working automation quickly and do not need deep operational detail yet.

What you need first

• A Hookshot workspace

• Access to one supported app such as Slack, GitHub, Linear, or Asana

• A simple workflow goal with one clear trigger and one clear outcome

Tip: Start with a narrow workflow. A first Protege should watch one source and produce one obvious result.

Steps

1. Pick a simple workflow

Good first examples:

• Summarize important Slack activity into one destination

• Create or update work items when an issue appears in GitHub or Linear

• Send a reminder when a tracked task still needs attention

2. Connect the app you need

1. Open Integrations.

2. Choose the app you need.

3. Complete the connection flow.

4. Check both Trigger Access and Tool Access for that integration.

If the integration connects but the Protege still cannot start or act, the usual cause is incomplete Trigger Access or Tool Access, not the Protege itself.

3. Create a Protege

Write the Protege in plain language:

• What starts it: the event or schedule

• What it decides: the logic or conditions

• What it produces: the action, message, or update

Example:

When a new issue is created in Linear, check whether it is urgent. If it is urgent, post a summary to the right Slack channel.

4. Review setup blockers

Before you enable anything, confirm:

• The required integration is connected

• The trigger source is ready

• Any setup blocker is resolved

• The Protege has a clear result you can verify

5. Trigger the workflow

• Use a live event from the connected app, or

• Use a schedule if the Protege is time-based

6. Check Event Feed first

Open Event Feed and confirm:

• The event arrived

• The right Protege was associated with it

• The status moved to a useful outcome such as ran

7. Check Audit second

Open Audit and confirm:

• A run exists for the Protege

• The run result matches what you expected

• The outcome is understandable enough to share with a teammate

How to verify

You’re done when...

• The integration shows as connected

• The Protege has no unresolved setup blockers

• Event Feed shows the event and the Protege response

• Audit shows the resulting run and outcome

Common failures

• The event never appears in Event Feed

• The event appears but the Protege is skipped

• The run exists but the outcome is not the result you expected

• The Protege is too broad and reacts to more items than intended

Next step

• Go-live checklist

• Create a Protege

• Event Feed