A hook tells Haruno what to do when something arrives in a connected account, such as a new email. This page shows how to create one and what it is allowed to do.
Mac appIn developmentSwitched off for every customer. On the Mac it is called automation triggers, and comes with a gallery of ready-made automations and automations Haruno drafts in a chat. The Scheduled screen stays time-based only.
Windows appAvailableRules that start a hook are edited in the advanced view.
In development in the Mac app. It is not available to customers yet. Do not promise it.
A hook is a saved instruction for something that happens while you are not looking. "When a new email comes in, tell me if it needs an answer today" is a hook. When the event arrives, Haruno reads it, does what the hook says, and replies in a sentence or two.
A hook has two halves. This page is the first half: what Haruno should do. The second half is which events start it.
Open Hooks in the navigation pane.
The Hooks page lists your hooks. Each has Edit and Delete.
The page says No hooks yet until you make one. A line under the title tells you where the rules live. In the normal view it says that integration rules are set up in the advanced view, and how to turn that on in Settings ▸ General. In the advanced view it offers Manage integration rules.
Create a hook
Press New hook.
A new hook. Leave Allow powerful tools off unless you trust everyone who can trigger it.
Field
What it is
Name
How you will recognise the hook. A name is required.
Message template
How the incoming event is handed to Haruno. The first template is {message}. Words in curly braces, such as {from} or {subject}, are filled in from the event.
Instruction (system prompt)
What Haruno should do with the event.
Working directory (optional)
A folder for the hook to work in. Press Browse….
Allow powerful tools
Off by default. See below.
AI Optimize beside the template and the instruction turns a short note into a full one. It keeps placeholders such as {from} exactly as you wrote them.
Press Save. To change a hook later, press Edit. Delete removes it.
A hook does nothing yet. It starts to work when a rule connects it to an event. See Connect a hook to events.
What a hook may do
A hook runs by itself, so nobody is there to answer a question or press Allow.
With Allow powerful tools off, a hook can reply through the connector and read files. It cannot run shell commands or change files.
With it on, it can do both.
A tool that you set to Confirm is refused, because nobody can approve it. A tool set to Off stays off.
Powerful tools: anyone who can message you can trigger it
A hook is started by something that arrives from outside, such as a message from another person. With Allow powerful tools on, that person's message could cause Haruno to run commands or change files. The window warns: Only enable for hooks you trust — anyone who can message the chat can trigger it. Keep it off for any hook that reads mail or chat messages.
Good to know
Hooks run inside Haruno, so Haruno has to be running. Turn on Launch at startup in Settings ▸ General to start it in the system tray when you sign in to Windows.
An event that Haruno could not get to within ten minutes is skipped. A long gap, such as a PC that was off, does not turn into a burst of old work.
What a hook did is not in History. You open it from the rule that started it.