Skip to main content
October 16, 2026
A Bolt schedule's Trigger type section with Incoming webhook selected, and the Trigger URLs card listing one webhook URL with Deliveries, an on switch, Send test request, Rotate, and Delete
A Bolt schedule can now start from a single POST request. Pick the new Incoming webhook trigger, create a webhook (the app lists it as a Trigger URL), and give its URL and secret to any tool that can send a request with a header: Jira Automation, Zapier, a CI job, or curl. Each request runs the scheduleโ€™s own commands, and the run shows the webhookโ€™s name, so you know what started it.
  • Manage it from the schedule. Create, pause, rotate, and delete incoming webhooks in the scheduleโ€™s edit form. The secret shows once, with a curl command ready to copy.
  • Test it. Send test request checks a webhook without waiting for the other tool. It starts a real run.
  • See every request. Bolt > Webhooks has a new Incoming tab that lists every incoming webhook in the workspace and each request it received: Run started, Skipped, Rejected, or Failed.
A request that arrives while the schedule is already running is skipped, not queued. See Incoming webhooks. Shipped in Paradime v6.19.0.