Webhooks

Webhooks push updates about your work out to a chat channel, so you don't have to sit in Busy Bee watching a task run. Point them at Slack or Discord and your team hears about starts, finishes, failures, and approvals where they already work.

Send updates to Slack or Discord

In your notification settings you can add a Slack webhook URL, a Discord webhook URL, or both. When work hits one of the events you've turned on, Busy Bee posts a message to that channel.

Only real chat webhooks are accepted, over HTTPS:

• Slack — https://hooks.slack.com/services/...
• Discord — https://discord.com/api/webhooks/... (or discordapp.com)

Arbitrary URLs are rejected. Create the incoming webhook in Slack or Discord first, then paste the URL into Busy Bee.

What you get pinged about

Turn events on individually. Available events:

• Task started — an agent picked up a task
• Task completed — a task finished successfully
• Task failed — a task errored out
• Approval required — a stage is waiting on your sign-off
• Approved — a task or stage was approved
• Feedback given — someone left feedback on a task
• Workflow stage completed — a stage in a multi-step run finished
• Preview ready — a preview URL is live
• Heartbeat alert — a heartbeat flagged something that needs attention

Notifications are rate-limited per organization so a busy run doesn't flood your channel.

Triggering work from your systems

Webhooks here are outbound only — there's no inbound webhook you can point your own systems at to start work. To kick off work from your own code or automations, use the REST API with an API key instead.

Where it fits

• API keys — trigger tasks programmatically
• Heartbeats — the source of heartbeat alerts
• Recurring tasks — schedule work that fires these events