Getting Started
What this is
This page explains the customer-facing Hookshot model: Proteges, Integrations, Event Feed, Audit, and Settings.
When to use it
Read this page before building your first Protege or when you need a fast refresher on how Hookshot fits together.
What you need first
A Hookshot workspace
Access to at least one external app you want to connect
Permission to create or edit Proteges in your workspace
Steps
1. Understand the core objects
A Protege is an automation you define in plain language.
An Integration connects Hookshot to tools like Slack, GitHub, Linear, or Asana.
Trigger Access controls what can start a Protege.
Tool Access controls what a Protege can do after it starts.
The Event Feed shows incoming activity and whether Proteges ran.
Audit shows the history and outcome of Protege runs.
Think of Hookshot as a control plane for automations. You describe the workflow, connect the right systems, and then use Event Feed and Audit to verify behavior.
2. Learn the three questions every Protege answers
What starts it?
What does it decide?
What does it produce?
If you can answer those three questions clearly, you are ready to draft a useful Protege.
3. Map the main dashboard sections
Proteges: create, review, enable, disable, and refine automations
Integrations: connect apps, review tool access, review trigger access, and repair broken connections
Event Feed: inspect live events and see whether Hookshot ran, skipped, or is still evaluating
Audit: inspect completed or in-progress runs and verify outcomes
Settings: manage workspace profile, retention, teams, and people
How to verify
You understand the model well enough to continue when you can explain:
Which app or schedule starts your Protege
Which action or outcome the Protege should produce
Where you will confirm activity in Event Feed
Where you will confirm success or failure in Audit
Common failures
Treating a Protege like a chat bot instead of an automation with a clear trigger
Confusing Trigger Access with Tool Access
Turning on a Protege before checking readiness blockers
Looking only at Audit when the Event Feed is the faster place to confirm whether the event arrived
Next step
Last updated
Was this helpful?