Connected-app event triggers
Use events from a connected service to start an agent session and include the event payload.
A Slack reaction or GitHub event can hand work to an agent as soon as it happens. Set the account, event source, team, agent, and instructions once; each match starts a new session.
Video placeholder
Keep Automations > Install trigger readable while you configure either a Slack reaction or GitHub event. After sending one matching event, open the session it starts.
Start from a supported event
The trigger catalog lists the event templates Hivy can install today. A template asks only for settings that affect its event.
- Slack reaction
- Run an agent when someone adds the chosen emoji in a selected Slack channel.
- GitHub mention
- Run an agent when someone mentions Hivy on an issue or pull request in a selected repository.
- GitHub code review
- Start a review after someone mentions the review agent or opens a pull request.
Image placeholder
Frame the entire trigger form at a readable size: connection, external resource, team, agent, instructions, and the event value when the form has one.
Connect the account that receives the event
Pick an active provider connection and the resource Hivy should watch. Slack asks for a workspace and channel; GitHub asks for a connection and repository.
Hivy won't install the trigger unless that connection still works and the chosen agent can use the provider connection through a valid connection.
Choose where the agent works
GitHub triggers ask for a team, which determines the available agents. A Slack reaction trigger uses its selected Slack channel as the event source, then creates or reuses the matching session.
A Slack reaction trigger also needs the emoji that counts as its signal. Hivy blocks a duplicate with the same agent, source, event, and value.
Write instructions for the event, not the example
Tell the agent what every matching event should produce. The event brings its repository, message, issue or pull request, sender, and other provider data; the instructions hold the outcome and rules that stay fixed between runs.
Disable a trigger without losing its setup
Open an installed trigger to change its name, resource, team, agent, event settings, or instructions. Turn its status off to ignore matches without losing the setup; delete it when you won't use it again.
Workspace owners and admins can edit, disable, or delete an installed trigger. Other members see only triggers attached to agents and teams they can access.