Schedules
Open the Scheduled tab to see every saved schedule you can manage.Create a schedule
You can also ask for one in Ask (“every Monday at 8am, remind me to review overdue invoices”). Hive reads the time in your own timezone and shows a card; nothing is scheduled until you press Create. See Build from chat.One-time tasks
A task can also run once, at a set date and time: ask for it in Ask (“remind me on 14 Oct at 14:45 to call Sam back”, “tomorrow at 9am”) and press Create on its card. The time must be in the future and at most a year ahead. Its row describes it by that time (“Once on Wed 14 Oct 2026 at 2:45 PM”) and, after it has run, reads Finished: it never runs again, and turning it off and on does not re-arm it. Its time is fixed once made, so the row has no Edit: to change when it runs, delete it and set a new one. Delete it when you no longer need the row. A one-time task runs like any scheduled run, as the member who created it and using the workspace’s credits, and does not count toward the hourly-schedule limit. If Hive is unavailable when it is due, a one-time workflow task runs as soon as Hive is back; a one-time agent task more than five minutes late is skipped, with a receipt, as any missed agent schedule is. If a one-time workflow task cannot start because of a brief problem on Hive’s side, it is tried again 90 seconds later, up to three times, and still runs only once. If it still cannot start, or it was first tried more than 30 minutes after its time, it records one Failed run saying it could not start and will not run again. If its owner holds no seat when it is due, it is skipped with a receipt saying it will not run again. When a one-time agent task does not run, its owner gets a bell card saying so. See How scheduled tasks work.1
Start a schedule
Select New schedule and choose the workflow. The list holds the saved workflows you can
run, and only while you have the Operator role or higher; a draft that has never been saved
is not offered. When there are none, New schedule is unavailable and the tab says why. Give
the schedule a label (up to 120 characters), or leave it empty to name it after when it runs,
for example “Every day · 9:00 AM”.A schedule on a workflow you cannot run stays in the list, but its Run now, Edit,
Delete and on/off controls are unavailable to you.
2
Choose when
Choose the Frequency:
- Hourly — at the Minute past each hour you pick: :00, :15, :30 or :45;
- Daily — at the Time you pick from a list in 15-minute steps;
- Weekly — on the days you toggle, at the Time you pick. Weekdays and Weekends select those days in one go.
3
Set the timezone
Enter an IANA timezone such as
Europe/London or America/New_York. The schedule follows local
time, including daylight-saving changes. The timezone also sets what “today” is for the runs
it starts: the dates relative to the run
a read takes and the date AI steps are told.4
Create it
Leave Start enabled on to arm it now, then select Create schedule.
Manage a schedule
- The row’s switch turns the schedule on or off without deleting it, and reads On or Off.
- Edit changes when it runs. Delete stops its future runs; past runs keep their receipts.
- Run now starts a production run immediately, as you, using your own connected accounts. It is greyed out while the workflow is not deployed or is paused; hover it to see why.
- Open workflow opens the workflow the schedule belongs to in the builder.
Whose accounts a schedule uses
A scheduled run acts as the member who created the schedule, through their connected accounts, and only while they still have the Operator role or higher. The schedule is pinned to the release that member scheduled and follows their own later deploys. If someone else’s release becomes live, the schedule stops and waits for its owner to review and turn it back on — nobody’s accounts run a version they have not seen. An admin can turn another member’s schedule off, but never on.When a schedule is held back
A schedule does not run while the kill switch is on, while a payment is overdue, or while the workspace is read-only because its trial ended without a plan, its plan was cancelled or a payment has been overdue for 14 days (see Trial and payments). It also does not start a run once the workflow has used its Monthly credit limit or Runs per hour. Each held-back schedule records one Failed run naming the reason. The schedule’s owner always gets a bell card, and so does anyone already listed under Notification recipients (see Failure notifications). When the hold clears, the schedule runs once and then carries on at its normal times; it does not catch up on every run it missed. See When runs do not start. A scheduled run that finds the workspace out of credits is not dropped: it waits up to 72 hours and starts once credits return (see Waiting for credits). Its AI steps run on Efficient or Balanced models; a step pinned to a Frontier model is refused in a scheduled run, unless your organisation’s own model key is in use. If a scheduled run cannot start because of a brief problem on Hive’s side, it is normally tried again about a minute later, and still runs only once. It is not tried again once 30 minutes have passed since its scheduled time (or one interval of the schedule, if that is shorter), or if the schedule was changed in the meantime: it then counts as skipped, and the schedule carries on at its next time. A run skipped after 30 minutes records one Failed run saying it could not start. A schedule whose owner has left the workspace or can no longer run workflows does not run.Schedule triggers
A workflow whose trigger is Schedule runs on the trigger’s own cadence, in UTC, once deployed — but only while it has no saved schedules. The trigger’s settings say that its times are in UTC and, when the workflow has schedules on the Scheduled tab, that those schedules decide when it runs and the canvas schedule is not used. Pick the trigger’s Time from a list in 15-minute steps (Minute past each hour for hourly), and for a weekly cadence toggle the days on the M T W T F S S buttons. A line under the time shows what it is on your own clock today, for example “09:00 UTC — 10:00 in London today.”, and warns when your local time moves by an hour as the clocks change. To run at a local time all year, add a schedule from the Scheduled tab: saved schedules work with any trigger and take over from the trigger’s cadence. See Schedule.Public forms
A public form lets anyone with its link submit the form without a Hive account. Each submission starts one production run. On Business there is no limit on how many public forms the workspace can have; an earlier plan allows 1 on Starter and 25 on Team. Each form starts at most 500 runs a day and 5,000 a month (days in UTC), and on Business each run counts as one of the workflow owner’s workflow runs. A later submission is refused: the person submitting it is told it was not sent (“This form has reached today’s submissions, so yours was not sent. Try again tomorrow.”), it starts no run, and Past runs records the refusal, naming the day or the month. If your forms need more, contact Hive support: only Hive staff can raise both limits, for the whole workspace. During a trial, public forms and public agent links run 100 times in total, and 100 more for each further week if Hive extends the trial. After that, a form tells the people submitting it “This form is not taking submissions at the moment, so yours was not sent.”, Past runs records that the trial’s public runs are used, and the workspace’s Owners and Admins are told once, in the Inbox under Needs you. Choosing a plan opens the form again. A submission refused because the workflow reached its credit limit, or the workspace is out of credits, read-only or past due, gets the same answer. If a form’s runs in an hour reach 10 times its usual hourly level, and at least 100, Hive pauses it until the hour ends: submissions are refused (“This form is busy, so your submission was not sent. Try again later.”), Past runs records each one, and the workspace’s Owners and Admins are told. A new or quiet form is never paused below 100 runs in an hour. The form starts runs again in the next hour. Someone whose submission was refused can send it again from the same page once the form is taking submissions: a refused submission is never treated as already sent.Publish a form link
1
Use a Public form trigger
Select the trigger and choose Public form. The form starts with the workflow’s name as its
title, which visitors read as the page heading; change it if you like. Add the fields from
Add a field: Name, Email, Phone, Company, Website, Message and
Amount each add a field already named and typed, and Other field adds a blank one that
opens for you to fill in. Each field is a compact row you select to edit its label, type and
whether it is required. Optionally add a Description (optional), shown under the title, and
a confirmation message. See Forms.
2
Deploy
Deploy the workflow.
3
Create the link
Select Form link in the builder header, then Create form link.
4
Copy and share
Select Copy link, or Open form to see the page visitors get.
Find or reset the link
Select Form link again at any time to see the live link and copy it. Opening the dialog never changes the link, so the one you already shared keeps working. Reset link creates a new link and immediately stops the current one. Hive asks you to confirm first, because anyone you shared the old link with needs the new one. Reset when a link has reached people it should not have. You can reset the link of the live release even while an unpublished draft has a different trigger. A link created before 5 October 2026 cannot be shown again. The dialog says a form link is live, with the last characters of its token, but can’t be shown here, and asks you to reset it to get a link you can copy. Each time the dialog shows a live link, the workspace’s audit log records who opened it, for which workflow and release. The link itself is never written to the log. Only members who can manage the workflow see its form link. It is never available to AI clients through the Hive MCP server. The link opens a Hive-hosted page at/forms?token=… on your Hive app address. To submit from your
own site or another system instead, use the public form API.
When a link stops working
A link belongs to the form step it was created for, not to one release. Deploying again or re-activating another version keeps it working, as long as the live release still has that form step: visitors then see the live release’s title, description and fields, and each submission runs the live release. Changes to the form reach visitors when you deploy them, with the same link. Only members who can manage sharing on the workflow (its owner) carry the link over when they deploy or re-activate a version, and the audit log records which release the link now serves. When someone who can edit the workflow but not manage its sharing deploys or re-activates a release that has the form step, Hive turns the link off instead and shows the warning “The public form link was turned off because you can’t manage sharing on this workflow. Ask its owner to create a new link.” The deploy dialog shows that warning before you deploy, Hive shows it again with the result of the deploy or re-activation, and the audit log records it. The owner then creates a new link and shares it. Resuming a paused workflow, or re-activating the release a link was created on, never turns the link off, whoever does it: the link already serves that release. Any other deploy or re-activation made through an AI client (the Hive MCP server) turns the link off, even when the workflow’s owner made it, with the warning “The public form link was turned off because this release was made through an AI client. Create a new link in Hive.” AI clients can’t create or see form links, so they can’t move one onto a release either. Create a new link from Hive afterwards. A link created before 5 October 2026 keeps the old rule: it works only on the release it was created on, so it stops working the next time the workflow is deployed or another version is re-activated. Reset it once to get a link that keeps working across deploys. A link stops working when:- the link is reset — a reset ends every earlier link of the workflow;
- the live release no longer has that form step — you removed it, or replaced the trigger with a new one — until a release that has it is live again;
- someone who can’t manage sharing on the workflow deploys a new release, or re-activates a release other than the live one or the one the link was created on;
- anyone does the same through an AI client (MCP);
- it was created before 5 October 2026 and the workflow is deployed again;
- the workflow is paused, returned to draft or deleted;
- the workflow’s owner can no longer run it.
Runs from a form
A submission runs as the workflow owner, through the owner’s connected accounts. Its action steps are carried out like any other workflow’s, whatever the owner’s accounts are set to, except that a step that sends to a value from the form waits for approval: anyone can fill in a public form, so its values do not decide where the workflow sends. The one exception is an acknowledgement: an email to the address the visitor typed sends with no card when everything else in it is text typed into the step or values from that same form. If it also includes an AI step’s answer, an app’s data, web search text or an app event’s value, it waits too. A held step’s card waits in Review decision on the workflow owner’s Signals page, and the run carries on. See Where a workflow step sends. The workspace’s limits — the kill switch, rate and spend caps, and the workflow’s credit limits — still apply. While the workspace is read-only or a payment is overdue, or when the workspace is out of credits or the workflow reached its credit limit, a submission is refused: the person submitting it is told “This form is not taking submissions at the moment, so yours was not sent.” While the kill switch is on, a submission is still accepted but starts no run. Either way it is recorded as a Failed run naming the reason. A workflow started by a public form cannot run an Agent library step.Credits and models for form runs
On Business, a form run’s AI steps use the AI credits of the workflow’s owner, like their own runs, with no separate public budget. On an earlier plan, they use credits from your workspace’s pool, inside the public budget: at most 25% of the month’s included credits (your trial credits during a trial), for public forms and public agent links together. Rolled-over credits, top-ups and bonus credits don’t raise it. An Owner or Admin can lower it under Settings → Usage → Spend controls. Public traffic never triggers auto top-up, and uses credit top-ups only if an Owner or Admin allows it there. A simple run typically uses about 3 credits. With your organisation’s own model key, a form run’s AI steps run on your key and each model call uses 1 credit from the public budget. A form starts no run while the workflow’s owner holds no seat, just as its scheduled runs don’t: moving the owner’s seat to someone else, or a plan change that suspends it over the limit, turns off the public forms of the workflows they own, and the Owners and Admins are told. Turn a form back on once the workflow’s owner holds a Basic, Pro or Max seat again: nobody else can take over the workflow of a member who is still in the workspace. Model for visitors decides which tier of model a form run’s AI steps use: Efficient by default, or Balanced if you turn it on for a form that needs stronger answers (about 4p a simple run on Business, about 27 credits on an earlier plan). Frontier models never run for a public form. See Model tiers and credits. Submissions are kept with the workflow, so a member with the Operator role or higher can replay one of the last 20 in a test run from the trigger’s Test tab.Related
Public form API
Submit forms from your own site or system.
Scheduled tasks
Every scheduled agent and workflow in one place.
Test and deploy
Releases, pausing and notifications.
Triggers and steps
Form fields and schedule settings.