Features
Webhooks
Queuety can send HTTP POST notifications to external URLs when specific events occur. Use webhooks to integrate with monitoring systems, Slack, or custom dashboards.
Supported events
| Event | Fired when |
|---|---|
job.completed | A job finishes successfully |
job.failed | A job throws an exception |
job.buried | A job exhausts all retry attempts |
workflow.completed | A workflow finishes all steps |
workflow.failed | A workflow step fails permanently |
Registering webhooks
Via PHP:
$id = Queuety::webhook_notifier()->register( 'job.buried', 'https://hooks.slack.com/services/...' );Via CLI:
wp queuety webhook add job.buried https://hooks.slack.com/services/...
wp queuety webhook add workflow.failed https://monitoring.example.com/queuetyListing webhooks
$webhooks = Queuety::webhook_notifier()->list();wp queuety webhook listRemoving webhooks
Queuety::webhook_notifier()->remove( $webhook_id );wp queuety webhook remove 3Payload format
When an event fires, Queuety sends an HTTP POST request with a JSON body:
{
"event": "job.buried",
"job_id": 42,
"handler": "send_email",
"queue": "emails",
"error_message": "Connection timed out",
"timestamp": "2025-03-15T14:30:00+00:00"
}For workflow events:
{
"event": "workflow.failed",
"workflow_id": 7,
"workflow_name": "generate_report",
"current_step": 2,
"total_steps": 4,
"error_message": "API rate limit exceeded",
"timestamp": "2025-03-15T14:30:00+00:00"
}Use cases
- Slack alerts. Get notified when jobs are buried or workflows fail.
- PagerDuty integration. Trigger incidents for critical job failures.
- Custom dashboards. Stream events to your own monitoring infrastructure.
- Audit trail. Forward events to an external logging service.