Action & Filter Hooks

MailFuz adheres to strict WordPress hook hygiene. You can modify payloads, inject custom headers, and listen for delivery events.

Action Hooks

mailfuz_before_send

Fires immediately before dispatching via the active transport.

add_action( 'mailfuz_before_send', function( $message, $transport ) {
    // Access $message->get_to(), $message->get_subject()
}, 10, 2 );

mailfuz_after_send

Fires after a message has been processed by the delivery transport.

add_action( 'mailfuz_after_send', function( $result, $message, $transport ) {
    if ( $result->is_success() ) {
        // Log custom analytical event
    }
}, 10, 3 );

mailfuz_failover_triggered

Fires when the primary transport fails and the standby backup is engaged.

add_action( 'mailfuz_failover_triggered', function( $primary_id, $backup_id, $error_msg ) {
    // Send Slack alert or PagerDuty incident
}, 10, 3 );

---

Filter Hooks

mailfuz_message_payload

Modify the outgoing message object before it is passed to the transport.

add_filter( 'mailfuz_message_payload', function( $message ) {
    $message->add_header( 'X-Custom-Tenant-ID', 'tenant_8482' );
    return $message;
} );

---

WP-CLI Commands

MailFuz registers native WP-CLI commands for command-line queue processing:

# Process next 50 pending queue messages
wp mailfuz queue process --limit=50

# Inspect queue status
wp mailfuz queue status

# Flush failed queue jobs
wp mailfuz queue retry-failed