engineering · 1 min read
Scheduled Triggers: Cron, Webhooks and Event Streams
A workflow only runs when something triggers it. Here are the trigger types Bhogar AI supports and the trade-offs of each.
BABhogar AI TeamProduct & Engineering
A workflow without a trigger is just a script. Bhogar AI supports cron, webhooks, file events, message-bus events and on-demand HTTP - covering the full spectrum from scheduled batches to real-time streams.
Why it matters
The right trigger depends on freshness, volume and idempotency needs. Cron for nightly jobs, webhooks for SaaS events, event streams for high-volume real-time, on-demand for user-initiated.
How Bhogar AI approaches it
Every workflow can declare multiple triggers. Bhogar AI manages the underlying schedulers, webhook signing, and consumer-group coordination so you can mix triggers without operational pain.
- Cron schedules with timezone handling
- Signed webhooks with replay protection
- Kafka, Pub/Sub and SQS event-stream consumers
- On-demand HTTP triggers with per-token rate limits
- Per-trigger telemetry and SLA monitoring
What you get
Mixing trigger types in one workflow lets teams cover scheduled, real-time and on-demand traffic from a single deployable artefact.