Triggers
Schedule
Hourly, daily, weekdays, weekly, or a custom five-field cron, in a time zone you pick. It runs at most every 15 minutes. A run more than an hour late is skipped, and the schedule moves on to its next time.GitHub event
Pull request opened or updated, opened, or labeled; issue opened or labeled; checks failed; or commits pushed. The repository must be one Vespin’s GitHub App can reach. By default, only events from people start a run. Turn on From Vespin’s agents or From other bots to include those. A push by Vespin’s own agents never starts a run.Webhook
Save the automation first. Its page then shows the address to POST to and a secret, which is shown only once:Idempotency-Key header to ignore repeated calls. New secret replaces the secret, and the old one stops working.
Sentry
New issues or triggered alerts, filtered by project, environment, and level. An owner or admin first installs the Sentry integration from the trigger’s settings. For alerts, set the Sentry alert rule’s action to notify the Vespin integration. The same issue starts a run again only after a cooldown, 24 hours by default.What the agent gets
The agent gets your prompt, then a note saying which automation started it and why, then the event itself: the GitHub event, the webhook body, or the Sentry issue. No one watches the run as it goes, so write the prompt to say what done looks like. Under Runs land in, choose New agent each run, or Same agent to send every run to one agent as a new message.Limits
A run that would go over a limit is skipped, not queued, and shows as Skipped on the Runs tab.
The editor keeps the defaults. To raise a limit, ask an agent to change the automation, through Create with an agent or Vespin MCP.
Run now starts a run at any time, even when the automation is off, within the same limits.