DMSI Webhooks fires the following WordPress actions that you can hook into.

dmsi_webhooks_process_event #

Fired by dmsi_trigger_webhook() when an event is triggered. The default handler (QueueManager::enqueue()) is hooked here. You can add your own handler for every event.

Parameters: ($event_name, $data, $context)

add_action('dmsi_webhooks_process_event', function($event_name, $data, $context) {
// Custom logging for every webhook event processed
error_log("Webhook event triggered: {$event_name}");
}, 10, 3);

dmsi_webhooks_delivery_failed #

Fired when a webhook delivery fails. The RetryHandler is hooked here to evaluate retry logic. Add your own handler to react to failures (custom alerts, external logging, etc.).

Parameters: ($log_id, $log_object, $endpoint_object)

add_action('dmsi_webhooks_delivery_failed', function($log_id, $log, $endpoint) {
// Send a Slack alert for any failure on a critical endpoint
if ($endpoint->name === 'Production CRM') {
my_slack_alert("Webhook failed to {$endpoint->url}: {$log->error_message}");
}
}, 10, 3);

dmsi_webhooks_unregistered_event #

Fired when dmsi_trigger_webhook() is called with an event name that is not registered in the EventRegistry. Useful for debugging custom event registrations.

Parameters: ($event_name, $data)

add_action('dmsi_webhooks_unregistered_event', function($event_name, $data) {
error_log("Attempted to trigger unregistered webhook event: {$event_name}");
}, 10, 2);

Related Topics #

• Available WordPress Filters
• Public API Functions
• Registering Custom Events