Triggers and schedules
The four ways work starts on its own: schedules, app events, webhooks, and a manual run button.
A trigger is the reason work starts. Workflows have exactly one trigger as their first node; employees can have several, listed under Triggers on their Workspace tab.
On a schedule
Pick a frequency: Every hour, Daily, Weekly, or Monthly, with a time picker, day of week, or day of month where it applies. If you need something irregular, Custom Cron Expression accepts standard cron, like 0 9 * * * for 9am daily.
When something happens in an app
App events fire when the outside world changes: a new email arrives, a Slack message lands, a form is submitted, a Shopify order comes in, a GitHub issue opens, a row is added to a sheet. Pick the event as the trigger, connect the app, and configure what counts. Some apps notify Verse instantly; others are checked on a short polling loop, so an event can take a minute or two to register.
When a webhook is received
The webhook trigger gives you a copyable URL. Anything that can send an HTTP request can start the run: your product, an internal tool, another automation platform. The payload it sends becomes data your steps can reference. Use Test Webhook once while building so Verse can learn the payload's shape.
Run manually
The manual trigger means “only when I press the button.” Good for checklists you want standardised but not automatic, and for anything you're still learning to trust.
Note
Employees in Autonomous mode are their own fifth trigger: they check in on their goals every few minutes and start work themselves. Pause the employee to stop that.