Webhooks & Automation
Connect BusyBee.Day to any tool with incoming and outgoing webhooks
Outgoing webhooks fire on 11+ event types - task lifecycle, comments, habits, focus time, projects. Incoming webhooks accept HTTP from any source to create or update tasks. Field mapping, JSON path extraction, and signature verification are built in.
Webhooks configuration - outgoing on 11+ events, incoming with JSON path mapping.
What is webhooks & automation?
A webhook is a user-defined HTTP callback that fires when an event happens. BusyBee.Day webhooks let you wire BusyBee.Day into any other system: get a Slack message when a task closes, create a BusyBee.Day task from a Stripe payment, or pipe data through Zapier and Make.
How to set up a webhook in BusyBee.Day
Configure outgoing or incoming webhooks for custom automation.
- 1
Open Webhooks
Navigate to /app/webhooks. Pick + Outgoing or + Incoming.
- 2
Configure outgoing
Pick events to fire on (task.created, task.completed, etc.), target URL (e.g., https://hooks.slack.com/...), and add a signing secret.
- 3
Configure incoming
BusyBee.Day generates a unique URL. Map JSON paths to task fields (e.g., $.email.subject → title, $.email.priority → priority).
- 4
Test the webhook
Click Test to send a sample payload. Inspect delivery log to verify the receiver got it.
- 5
Enable and monitor
Toggle the webhook live. Delivery logs show every fire with status code, payload, and response.
Who uses webhooks & automation?
Slack notifications on task completion
Outgoing → task.completed → Slack incoming webhook. Channel gets a message every time a high-priority task closes.
Stripe payment → BusyBee.Day task
Incoming webhook receives Stripe charge.succeeded; creates a "Send invoice" task with customer email mapped to a custom field.
Zapier multi-step automation
BusyBee.Day outgoing webhook fires a Zap that creates a row in Airtable, sends an email, and posts to Discord.
Github PR closed → mark BusyBee.Day task done
Incoming webhook from GitHub matches PR title to BusyBee.Day task and marks it completed.
Capabilities at a glance
- Outgoing webhooks for 11+ event types
- Events: task created/updated/completed/deleted/status_changed/assigned
- Events: comment.created, habit.completed, focus_time.started/ended, project.created
- Incoming webhooks to create or update tasks from any source
- Field mapping from webhook payload to task properties
- JSON path extraction for nested payloads
- HMAC signatures for secure verification
- Test webhook delivery before deploying
- Event history and delivery logs
BusyBee.Day Webhooks vs Zapier vs Make vs n8n
| Capability | BusyBee.Day | Zapier | Make | n8n |
|---|---|---|---|---|
| Native task event triggers | 11+ events | No (per app) | No (per app) | No (per app) |
| Incoming webhooks → task | Yes | Yes | Yes | Yes |
| Field mapping with JSON path | Yes | Yes | Yes | Yes |
| HMAC signature verification | Yes | Yes (paid) | Yes | Yes |
| Free outgoing webhooks/month | Unlimited | 100 (free) | 1k (free) | Unlimited (self-host) |
Comparison reflects publicly listed features and pricing as of May 5, 2026. Subject to change.
Frequently asked questions
What events can trigger outgoing webhooks?
Can I connect BusyBee.Day to Slack via webhooks?
Can I connect BusyBee.Day to Zapier or Make?
How are webhooks secured?
Are webhook deliveries reliable?
Related features
Ready to try Webhooks & Automation?
Start free - no credit card. Upgrade to Pro any time for teams, advanced analytics, and unlimited automation.