Automations overview
Start an agent from a connected-app event, a recurring schedule, or an incoming HTTP request.
An automation starts agent work without waiting for someone to open Hivy. It runs a named agent for a team, where the responsible team can see the request, result, follow-ups, and cost.
Video placeholder
Start in Automations and create a connected-app trigger, a schedule, and a webhook; finish on the resulting session from one run. The form controls and session text need to remain readable.
Choose how the work starts
Begin with the signal your system already produces; Hivy turns it into a regular agent session instead of sending the work to a separate automation workspace.
Scope every run before you automate it
The team puts every new session beside related work and limits the agent picker to that team's agents. Automated and manual sessions therefore follow the same access boundary.
Choose an agent prepared for the job and describe the finished result in its instructions. Event triggers add connected-app data or an HTTP payload; a schedule sends the saved task each time it runs.
Manage automations in one place
Open Automations, then switch between Triggers, Schedules, and Webhooks. Each list has search and filters; open an item to check its scope or status.
A team member can create an automation for a team they manage. Workspace owners and admins control existing automations: they can edit them, pause or disable them, or delete them.
Each run becomes a session
When an event arrives or a scheduled time comes due, Hivy creates a session for the chosen team and gives the task to the agent. Open the session to check its work and cost; if the result needs a change, ask there.
Review automation runs