Priority support<\/strong> \u2014 dedicated email support (Agency Pro only)<\/li>\n<\/ul>\n\nExternal Services<\/h3>\n\n
RoutineKit communicates with an external service only when you explicitly connect to RoutineKit Cloud<\/strong>. No data is sent to any external server without an active connection.<\/p>\n\nRoutineKit Cloud<\/h4>\n\n
When you enter a license key and connect to RoutineKit Cloud, this plugin sends data to and receives data from https:\/\/app.routinekit.dev<\/code>.<\/p>\n\nData sent:<\/strong>\n* Your site URL, site name, and WordPress version (on connect and heartbeat)\n* RoutineKit plugin version (on heartbeat)\n* Workflow structure (title, steps) when you push a workflow to a site group\n* Execution completion status when a runner finishes a SaaS-assigned workflow<\/p>\n\nData received:<\/strong>\n* Workflow assignments pushed from your central dashboard\n* Template library available for your plan\n* License plan status<\/p>\n\nWhen this happens:<\/strong> Only after you explicitly enter an API key in RoutineKit > Settings > Cloud Connection. The connection can be removed at any time from the same screen, after which no further data is sent.<\/p>\n\nThis service is operated by the plugin author. It is optional \u2014 the plugin is fully functional without it.<\/p>\n\n
\n- Service endpoint: https:\/\/app.routinekit.dev<\/li>\n
- Privacy policy: https:\/\/routinekit.dev\/privacy<\/li>\n
- Terms of service: https:\/\/routinekit.dev\/terms<\/li>\n<\/ul>\n\n
Privacy Policy<\/h3>\n\n
RoutineKit captures wp_options changes made during your admin sessions to help you build workflow steps (Auto-Capture feature). This data is stored locally in your own database and is never sent externally on the free plan.<\/p>\n\n
The Auto-Capture buffer stores: the option name, old value, new value, the URL of the admin page where the change occurred, and the WordPress user ID of the person who made the change. This data is retained for a configurable period (default: 30 days, adjustable in Settings) and deleted automatically. It is fully removed when the plugin is uninstalled.<\/p>\n\n
Execution audit trails store: which user ran a workflow, which steps were completed or skipped, timestamps, and any notes or evidence files uploaded. This data is stored locally in your database.<\/p>\n\n
If you connect to RoutineKit Cloud (Pro), please review the RoutineKit Cloud privacy policy at https:\/\/routinekit.dev\/privacy.<\/p>\n\n
Third-Party Libraries<\/h3>\n\n
This plugin includes the following third-party library:<\/p>\n\n
\n- html2canvas<\/strong> (v1.4.1, MIT License) \u2014 https:\/\/html2canvas.hertzen.com\nUsed to capture screenshots of the admin screen for step evidence. Bundled in
assets\/js\/html2canvas.min.js<\/code> (vanilla capture watcher) and in the webpack chunk assets\/js\/548.js<\/code> (React runner notes).<\/li>\n<\/ul>\n\n\n\n- Upload the
routinekit<\/code> folder to \/wp-content\/plugins\/<\/code><\/li>\n- Activate the plugin from the Plugins screen in WordPress<\/li>\n
- Go to RoutineKit > Workflows<\/strong> to create your first workflow<\/li>\n
- Use the Run<\/strong> button to open the guided Runner sidebar<\/li>\n<\/ol>\n\n\n
\nDoes RoutineKit replace MainWP or ManageWP?<\/h3><\/dt>\nNo. RoutineKit is complementary to multi-site management tools. It focuses on what<\/em> needs to be configured on each site and provides a guided runner to do it, rather than managing plugin updates or security scans.<\/p><\/dd>\nCan I share workflows between sites?<\/h3><\/dt>\nYes \u2014 use the JSON Export button on any workflow, then import the JSON file on another site. Users with a connected RoutineKit account can also import directly from a URL. Pro users can additionally manage and assign workflows across all sites from the central dashboard.<\/p><\/dd>\n
How does Auto-Capture work?<\/h3><\/dt>\nWhen 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.<\/p><\/dd>\n
Is my data sent anywhere?<\/h3><\/dt>\nOn the free plan, all data stays on your own site. Pro users optionally connect to the RoutineKit Cloud dashboard for cross-site management \u2014 connection requires an explicit API key entry and can be revoked at any time.<\/p><\/dd>\n
What happens if I deactivate the plugin?<\/h3><\/dt>\nDeactivating preserves all your workflows and data.<\/p>\n\n
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<\/strong> before deleting \u2014 RoutineKit will then drop its tables and options when the plugin is deleted.<\/p><\/dd>\nCan multiple team members run the same workflow?<\/h3><\/dt>\nYes \u2014 each run is tracked separately as an execution with its own audit trail. Multiple people can run the same workflow on different sites simultaneously.<\/p><\/dd>\n\n<\/dl>\n\n\n
1.0.4<\/h4>\n\n\n- New: a short guide below the workflow table covering the two ways to use Start Workflow \u2014 working through a checklist, and building one as you go by adding steps from the runner while you make the changes.<\/li>\n
- Improved: deleting a workflow now says whether it worked, and when it is refused it gives the reason rather than failing quietly.<\/li>\n
- Improved: the workflow list opens on Active, so the workflows you are likely to run are in front of you. It falls back to All when nothing is active.<\/li>\n
- Improved: workflows now carry a Pushed or Received badge with its own icon, replacing the single Cloud tag, so it is clear at a glance which ones you published and which arrived from another site. Both explain themselves on hover.<\/li>\n
- Changed: a workflow assigned to this site from the cloud can no longer be deleted here. Withdrawing an assignment is the sending site's to do, and a deleted copy only returned on the next check. Archive it to take it out of the way.<\/li>\n
- Fixed: a workflow that had been run but never pushed could not be deleted. Your own workflows are now held back only once pushed, and the reason is given on hover.<\/li>\n
- Fixed: stopping a run left the workflow list showing it as still running until the page was reloaded.<\/li>\n<\/ul>\n\n
1.0.3<\/h4>\n\n\n- New: choose where the launcher lives \u2014 a floating pill, an item in the admin bar, or hidden altogether. The admin bar option keeps RoutineKit to hand without anything sitting over the page.<\/li>\n
- New: assigning a group asks whether to tag it only or to push straight away, so you can line up several groups before distributing.<\/li>\n
- Improved: workflow table actions are now in a single \u00b7\u00b7\u00b7 menu on each row, replacing the inline text links under the title.<\/li>\n
- Improved: choosing to push a workflow to a group now says up front that doing so freezes its steps, rather than leaving it to the confirmation screen.<\/li>\n
- Changed: a workflow freezes once you push it, so the checklist your peers hold always matches the one you kept. To revise it, use Duplicate to edit \u2014 the copy is a separate workflow you can edit and push on its own terms.<\/li>\n
- Changed: toast notifications are off by default on new installs. Existing sites keep whatever they had set.<\/li>\n
- Fixed: a captured step could be filed against a workflow already pushed to the cloud, adding steps to a checklist that was supposed to be frozen. The workflow picker no longer offers those workflows, and the server refuses them.<\/li>\n
- Fixed: steps could not be added, edited, reordered or deleted on a pushed workflow even where the screen offered it \u2014 the change was rejected on save. Screens no longer offer an edit that would be refused.<\/li>\n
- Fixed: pushing an edited workflow overwrote the copy held by sites that already had it, changing what they saw after the fact. Each set of steps is now kept as its own version, and a site only re-imports when a genuinely newer one arrives.<\/li>\n<\/ul>\n\n
1.0.2<\/h4>\n\n\n- Improved: captures now record which settings screen they came from.<\/li>\n
- Security: sensitive option values \u2014 passwords, API keys, tokens and salts \u2014 are now redacted before they reach the Auto-Capture buffer. Values captured by earlier versions are overwritten automatically on upgrade.<\/li>\n
- Fixed: background processes no longer trigger Auto-Capture. Cron jobs, WP-CLI commands, AJAX requests and page-builder saves are excluded, so captures reflect real settings changes only.<\/li>\n
- Fixed: a settings save could write the same capture more than once.<\/li>\n
- Security: removed an unused diagnostic that kept recent REST request and response data in a browser variable on admin screens.<\/li>\n<\/ul>\n\n
1.0.1<\/h4>\n\n\n- New: Paste a Checklist \u2014 paste a list from a Google Doc, Notion page or plain notes and it becomes a workflow. The first line is the title, every line after it becomes a step; bullets, numbering and [ ] checkboxes are stripped automatically. Available from Import Workflow, from the empty state, and once on first run.<\/li>\n
- Changed: plan buttons on the Upgrade screen now open the pricing page at routinekit.dev while self-serve signup is being finished<\/li>\n
- Fixed: a workflow whose steps are all optional no longer marks itself complete as soon as the first step is done<\/li>\n
- Fixed: completing optional steps after the last required one no longer resends the completion email or re-pushes the run to RoutineKit Cloud<\/li>\n
- Fixed: dismissing the \"run is paused\" notice in the Runner now sticks instead of reappearing on the next admin page<\/li>\n<\/ul>\n\n
1.0.0<\/h4>\n\n\n- Initial release<\/li>\n
- Workflow Builder with step editor and deep-link selector<\/li>\n
- Guided Runner floating sidebar<\/li>\n
- Auto-Capture engine for wp_options changes<\/li>\n
- 5 starter workflow templates<\/li>\n
- JSON export and import (file and URL)<\/li>\n
- Import from URL (requires connected RoutineKit account)<\/li>\n
- Auto-Capture retention configurable by all users (default: 30 days)<\/li>\n
- Pro: SaaS dashboard for cross-site fleet management and assignment push<\/li>\n
- Pro: note sharing across sites<\/li>\n
- Pro: evidence upload per step<\/li>\n
- Pro: full audit trail with user attribution and option snapshots<\/li>\n<\/ul>","raw_excerpt":"Reusable site configuration checklists for WordPress agencies \u2014 stop re-doing the same setup tasks on every client site.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/bre.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/359326","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/bre.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/bre.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/bre.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=359326"}],"author":[{"embeddable":true,"href":"https:\/\/bre.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/codeleftover"}],"wp:attachment":[{"href":"https:\/\/bre.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=359326"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/bre.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=359326"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/bre.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=359326"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/bre.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=359326"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/bre.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=359326"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/bre.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=359326"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}