WP Crontrol 2.0.0 has 25 actions and 18 filters, read directly from its source code on Nov 17, 2026. The list updates automatically when a new version is released.
How to use these hooks
Actions let you run your own code at a specific moment. Filters let you change a value before the plugin uses it. Put your code in a child theme's functions.php or a code-snippets plugin, never in the plugin's own files, because updates overwrite them.
// Run your own code when WP Crontrol fires an action
add_action( 'crontrol/deleted_event', function( $event ) {
// Your code runs here.
}, 10, 1 );
// Change a value WP Crontrol is about to use
add_filter( 'crontrol/log_retention_days', function( $value ) {
// Change $value here.
return $value;
}, 10, 1 );Parts of a name in {braces} are filled in at runtime (for example a post type or field ID). Choose Example on any hook for a ready-to-edit snippet.
All hooks
-
/** * This action is documented in wp-crontrol.php */ do_action( 'crontrol/deleted_event', $event ); -
/** * Filters the number of days that cron event log entries are kept. */ apply_filters( 'crontrol/log_retention_days', LOG_RETENTION_DAYS ); -
/** * This action is documented in src/bootstrap.php */ do_action( 'crontrol/paused_hook', $hook ); -
/** * This action is documented in src/bootstrap.php */ do_action( 'crontrol/resumed_hook', $hook ); -
/** * Fires after a new cron event is added. */ do_action( 'crontrol/added_new_event', $event ); -
/** * Fires after a new PHP cron event is added. */ do_action( 'crontrol/added_new_php_event', $event ); -
/** * Fires after a new cron schedule is added. */ do_action( 'crontrol/added_new_schedule', $name, $interval, $display ); -
/** * Fires after a new URL cron event is added. */ do_action( 'crontrol/added_new_url_event', $event ); -
/** * Fires after all cron events with the given hook are deleted. */ do_action( 'crontrol/deleted_all_with_hook', $hook, $deleted ); -
/** * Fires after a cron schedule is deleted. */ do_action( 'crontrol/deleted_schedule', $name ); -
/** * Fires after a cron event is edited. */ do_action( 'crontrol/edited_event', $event, $original ); -
/** * Fires after a PHP cron event is edited. */ do_action( 'crontrol/edited_php_event', $event, $original ); -
/** * Fires after a URL cron event is edited. */ do_action( 'crontrol/edited_url_event', $event, $original ); -
/** * Filters the output for a custom column on the cron event list table. */ apply_filters( "crontrol/event_table_column_output_{$column_name}", '', $event ); -
/** * Filters the filter types on the cron event listing screen. */ apply_filters( 'crontrol/filter-types', $types, $hooks_type ); -
/** * Filters the available filtered events on the cron event listing screen. */ apply_filters( 'crontrol/filtered-events', $filtered, $events ); -
/** * Filters whether the arguments of a cron event are stored in its log entry. */ apply_filters( 'crontrol/log_event_args', false, $hook ); -
/** * Filters the number of days that aggregated cron metrics are kept. */ apply_filters( 'crontrol/metric_retention_days', METRIC_RETENTION_DAYS ); -
/** * Filters the hook name prefixes that count as a scheduled backup. */ apply_filters( 'crontrol/promos/backup_hooks', array( 'duplicator', 'updraft_backup', 'backwpup', 'backupbuddy', 'pb_backupbuddy', 'solid_backups', 'wpvivid', 'jetpack_backup', 'vaultpress', 'blogvault', 'ai1wm', 'boldgrid_backup', 'bmi_', 'xcloner', 'wptc_', ) ); -
/** * Filters the backup plugins that stop the "No scheduled backups" suggestion * while they're active. */ apply_filters( 'crontrol/promos/backup_plugins', array( 'duplicator/duplicator.php', 'duplicator-pro/duplicator-pro.php', 'updraftplus/updraftplus.php', 'backwpup/backwpup.php', 'backwpup-pro/backwpup.php', 'backupbuddy/backupbuddy.php', 'solid-backups/solid-backups.php', 'wpvivid-backuprestore/wpvivid-backuprestore.php', 'wpvivid-backup-pro/wpvivid-backup-pro.php', 'jetpack-backup/jetpack-backup.php', 'vaultpress/vaultpress.php', 'blogvault-... ); -
/** * Filters the suggested plugins. */ apply_filters( 'crontrol/promos/plugins', $plugins ); -
/** * Fires after a cron event is scheduled to run manually. */ do_action( 'crontrol/ran_event', $event ); -
/** * Fires after a logged cron event run is finished and saved. Used by WP * Crontrol's alerts. */ do_action( 'crontrol/run_finished', $run ); -
/** * Filters whether cron event runs in the current request should be logged. */ apply_filters( 'crontrol/should_log', $doing_cron ); -
do_action( 'crontrol/debug', sprintf( __( 'HTTP %1$s request to %2$s returned status code %3$s', 'wp-crontrol' ), $method, '{url}', '{code}' ), array( 'url' => $safe, 'code' => intval( wp_remote_retrieve_response_code( $response ) ), ) ); -
do_action( 'crontrol/error', $error ); -
do_action( 'crontrol/manage/eventname', $existing ); -
apply_filters( 'cron_request', array( 'url' => add_query_arg( 'doing_wp_cron', $doing_wp_cron, site_url( 'wp-cron.php' ) ), 'key' => $doing_wp_cron, 'args' => array( 'timeout' => 3, 'blocking' => true, 'sslverify' => apply_filters( 'https_local_ssl_verify', false ), ), ), $doing_wp_cron ); -
apply_filters( 'crontrol/event_admin_messages', $messages, $hook, $message ); -
apply_filters( 'crontrol/event_table_columns', $cols ); -
apply_filters( 'crontrol/event-actions', $links, $event ); -
apply_filters( 'crontrol/links', $links ); -
do_action( 'crontrol/manage/args', $existing ); -
do_action( 'crontrol/manage/hookcode', $existing ); -
do_action( 'crontrol/manage/hookname', $existing ); -
do_action( 'crontrol/manage/method', $existing ); -
do_action( 'crontrol/manage/next_run', $existing ); -
do_action( 'crontrol/manage/schedule', $existing ); -
do_action( 'crontrol/manage/url', $existing ); -
do_action( 'crontrol/tab-header', $tab, $tabs ); -
apply_filters( 'crontrol/tabs', $tabs ); -
apply_filters( 'https_local_ssl_verify', false );
Generated from WP Crontrol's GPL-licensed source code. Hooks inside bundled third-party libraries are not listed.
Done for you
Rather have it built for you?
Tell us what should change and we’ll write and test the code using these hooks.
Custom hook snippet
from $49
A small, update-safe change built on the plugin’s own hooks.
- Code written against the plugin’s actions and filters
- Tested on a staging copy of your site
- Install instructions included
Typical turnaround: 2–3 business days
Choose thisPlugin customisation
from $149
New features or changed behaviour, without editing the plugin’s files.
- Built as a companion plugin, so updates never wipe it
- Exact quote before we start
- Tested on staging, then deployed
Typical turnaround: 3–7 business days
Choose thisNot sure which fits? Describe what you need and we’ll suggest the simplest option.
Can't find the right hook?
We can build the customisation for you. Describe what you need: