| 开发者 | codeleftover |
|---|---|
| 更新时间 | 2026年9月18日 02:15 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
routinekit folder to /wp-content/plugins/No. RoutineKit does not touch your site settings, run tasks automatically, or make changes on your behalf. It guides a human through a predefined process - your team member still opens each settings page, makes the changes, and marks each step complete. What RoutineKit adds is structure, consistency, and a full audit trail proving the work was done correctly.
RoutineKit is built for WordPress agencies and freelancers managing multiple client sites. If you've ever onboarded a new client, launched a WooCommerce store, or hardened a site's security - and done it slightly differently each time - RoutineKit solves that. The core benefit: you build a workflow once, and every team member follows the exact same steps on every site, with a record proving it was done. It's most useful when you manage 5 or more client sites, have team members executing repetitive setup tasks, or need to show clients proof that their site was configured correctly. If you're a solo developer with one or two sites, the free plan still works - but the biggest value unlocks when you're managing a fleet.
When you start a workflow, a floating panel appears on every WordPress admin page showing your current step, instructions, and a direct link to the exact settings page you need. You complete each step, add notes or evidence if required, and move to the next. The runner stays visible as you navigate between pages so you never lose your place. When all required steps are done, the execution completes and the full audit trail is saved.
Yes - no trial period, no credit card, no expiry. The free plan is a fully functional WordPress plugin you install directly from the WordPress.org directory. You get unlimited workflows, unlimited runs, and all core features on your own site with no account needed. The paid Agency plans add cross-site fleet management via RoutineKit Cloud, which requires an account and a license key.
Yes. RoutineKit has role-based access controls. You decide which WordPress roles can run workflows or edit them. A team member can be given run access without being a full administrator - they'll see the runner panel and complete steps, but won't be able to create or modify workflows.
No. RoutineKit is complementary to multi-site management tools. It focuses on what needs to be configured on each site and provides a guided runner to do it, rather than managing plugin updates or security scans.
Yes. On any plan, you can export a workflow as JSON and import it on another site manually. On the free plan, you can also connect up to 3 sites to RoutineKit Cloud for direct push. Agency plans let you push any workflow to an entire group of client sites in one click - no exporting, no importing, no repeating yourself.
When you navigate to a WordPress settings page and save changes, RoutineKit detects which wp_options values changed and shows a notification offering to add them as a workflow step. The step includes a snapshot of the exact settings you changed.
On the free plan, all data stays on your own site. Agency plans optionally connect to RoutineKit Cloud for cross-site management - connection requires an explicit license key and can be revoked at any time from Settings > Cloud Connection.
Deactivating preserves all your workflows and data. Deleting the plugin also preserves your data by default, so you can reinstall without losing anything. If you want a clean removal, enable Settings > Danger Zone > Delete All Data on Uninstall before deleting - RoutineKit will then drop its tables and options when the plugin is deleted.
Yes - each run is tracked separately as an execution with its own audit trail. Multiple people can run the same workflow on different sites simultaneously.
pass or access_oauth2_refresh are now redacted before reaching Auto-Capture - previously only names built from a recognizable word plus a suffix (like stripe_secret_key) were caught, so a plugin that named its own password field just pass wrote it to the capture buffer in plain text.wp_options - Wordfence and similar plugins previously went unnoticed no matter what was changed.