Skip to main content
October 20, 2026 A Bolt run started by an incoming webhook now gets the request body. Before, the body was ignored, so every run looked the same no matter which event started it.
  • In commands. The run gets PARADIME_WEBHOOK_EVENT_ID and, when the body is a JSON object or array of 64 KB or less, PARADIME_WEBHOOK_PAYLOAD. A script or dbt command can read the event from there.
  • In DinoAI agents. A paradime dinoai command gets the body added to its task as data, not as instructions. An agent that runs on a Jira, PagerDuty, or GitHub webhook can now work on the one ticket, alert, or pull request that started it.
  • Retries keep the payload. Retrying a run sends the same event again.
  • Agent-only schedules overlap. A schedule that only runs paradime dinoai starts a new run for each request, up to 5 at a time, so one event doesn’t wait for another.
Two more changes make incoming webhooks easier to set up:
  • Schedules as code. Set trigger_on_webhook: true in paradime_schedules.yml, deploy, then create the URL on the schedule page.
  • Before the first deploy. On a new schedule, pick Incoming webhook as the trigger and create its Trigger URL on the form. Deploy needs an active Trigger URL. See On a new schedule.
See Use the request body in a run. Shipped in Paradime v6.20.0.