A loop runs Begin AI on its own: on a schedule, or when something happens, such as a shift being
created. It reads and changes your workspace with its owner’s access. Loops replaced Scheduled
tasks: every one became a loop with its name and run history, and a bookmarked scheduled-task
link still opens it.
Loops has its own role permission. Managers and administrators have it by default; if you
cannot see Loops in the sidebar, ask an administrator to give your role access.
Create a loop
Start from New loop on the Loops page. Describe what you want in a sentence and Begin AI drafts the whole loop: its name, description, instructions and when it runs. Or pick one of the templates, or choose Create from scratch for an empty form. A draft or a template opens the editor already filled in, and nothing is saved until you publish.1
Choose how it starts
One picker holds both. On a schedule reads as one sentence, for example “Every 2 weeks on
Monday at 09:00, starting 14 September 2026”, in your workspace’s timezone. Choose an event
instead, such as Shift created, and the loop waits for that event. Narrow it with criteria
on the line beneath, each reading is or is not a position, a location, a department, a
role or a person.
2
Tell it what to do
Write the instructions yourself, or choose Configure with AI to send your current draft to
Begin AI. Review its suggestion, then choose Apply to instructions to replace the
instructions in your open draft. If you change the draft, choose Generate again for a fresh
suggestion. Applying does not publish the loop. Instructions are required before you can
publish; a title or event details do not replace them.
3
Decide what it may do on its own
Turn Web search on or off and set Changes to Never or Apply everything.
4
Publish
Publish turns your draft into the version that runs.
Create a loop that checks tomorrow's schedule every evening and flags anything still unpublished.
Know who authorises a change
Edit access lets you change a loop’s setup; only its owner’s permissions ever run it. Who can edit is set by the owner or an administrator. Publishing makes a new version live: the owner’s publish takes effect at once; anyone else’s becomes a pending revision, and the loop keeps its last authorised version until the owner authorises it. The owner or publisher may discard it instead. Published versions lists every one; Restore prepares a revision the owner authorises, like any change. A new owner pauses it the same way, clearing web search, changes and connectors until they authorise it. Before asking Begin AI in an ordinary chat to edit a loop with a pending revision, authorise or discard that revision. Those edits start from the last authorised setup; Configure with AI uses the draft you have open.Run it, and see what happened
Run now starts one straight away. For an event loop, Run loop on… picks an item, such as a shift or a person, as if the event had just happened to it. Run history lists every run’s outcome; opening one shows the instructions used, its transcript and changes made. New loop runs share their results with everyone who can see the loop. Type in Ask a follow-up at the bottom of the run to continue the conversation: it carries on under Follow-up, beneath the result, and the same Visible to audience can read and continue it. Every change asked for there waits for approval, because the follow-up opens by quoting the run’s result. Follow-ups carried over from Scheduled tasks that already contain a personal reply remain private to their original creator. An untouched context-only follow-up becomes shared when it is reopened. A deleted transcript cannot be replied to.Needs attention means the loop stopped before a step that always needs a person; changes
already made are kept. That step’s card is cancelled once the run closes, so you do it yourself
instead.
Pause, duplicate, hand over or delete
Open the ⋯ menu beside a loop, right-click its row, or press and hold the row on a touch screen:Next
Taking actions
Approval mode for an ordinary chat; a loop’s own Changes setting works differently.
Triggers and conditions
React to a loop finishing from a workflow of your own.
Still need help?
Contact support
Email the Begin team and we’ll get back to you.
Ask Begin AI
Open the AI assistant and get instant answers based on these docs.