Title: RoutineKit Ìtumọ̀ Yorùbá: – Repeatable WordPress Workflow Checklists for Agencies Author: Zeeshan Rasool Published: Ọwẹ́wẹ̀ 3, 2026 Last modified: Ọwẹ́wẹ̀ 17, 2026 --- Ṣàwárí àwọn plugin ![](https://ps.w.org/routinekit/assets/banner-772x250.png?rev=3680033) ![](https://ps.w.org/routinekit/assets/icon-256x256.png?rev=3700684) # RoutineKit Ìtumọ̀ Yorùbá: – Repeatable WordPress Workflow Checklists for Agencies Láti ọwọ́ [Zeeshan Rasool](https://profiles.wordpress.org/codeleftover/) [Ṣe ìgbàsílẹ̀](https://downloads.wordpress.org/plugin/routinekit.1.0.6.zip) * [Àwọn àlàyé](https://yor.wordpress.org/plugins/routinekit/#description) * [Àwọn àgbéyẹ̀wò](https://yor.wordpress.org/plugins/routinekit/#reviews) * [Ìgbéwọlẹ̀](https://yor.wordpress.org/plugins/routinekit/#installation) * [Ìdàgbàsókè](https://yor.wordpress.org/plugins/routinekit/#developers) [Ìrànlọ́wọ́](https://wordpress.org/support/plugin/routinekit/) ## Àpèjúwe **RoutineKit** solves the agency problem of replicating the same WordPress configuration changes across dozens or hundreds of client sites. Unlike fleet-management tools that handle updates and monitoring, RoutineKit focuses on the human configuration work itself Ìtumọ̀ Yorùbá: – the guided checklist and audit trail for what actually needs to be set up on each site. Build reusable, step-by-step configuration checklists inside one site, then run them anywhere. Each step includes instructions, a direct deep-link to the exact settings page, and optional evidence capture Ìtumọ̀ Yorùbá: – so your team always knows what was done, when, and by whom. Learn more at [Website](https://routinekit.dev/) | [Changelog](https://routinekit.dev/changelog) #### All Core Features (Completely Free) Everything below works with no payment required. Every feature works on a single site (checklists could be manually imported to unlimited sites) with no account at all; items marked * require a free RoutineKit account. * Workflow Builder Ìtumọ̀ Yorùbá: – create reusable configuration checklists with step-by-step instructions * Guided Runner Ìtumọ̀ Yorùbá: – a floating sidebar that walks your team through each step and links directly to the right settings page. Put it in the admin bar, or hide it, if you would rather it stayed out of the way * Auto-Capture Ìtumọ̀ Yorùbá: – RoutineKit watches wp_options changes as you configure a site and offers to turn them into workflow steps automatically, with the exact values recorded for later * Evidence Capture Ìtumọ̀ Yorùbá: – attach screenshots or PDFs to a step as proof of what was done * Step Notes Ìtumọ̀ Yorùbá: – add private notes to any step while running a workflow * Audit Trail Ìtumọ̀ Yorùbá: – a timestamped log of who completed what and when, with before/after option snapshots * Run History Ìtumọ̀ Yorùbá: – review past executions per workflow * 25+ Deep-Links Ìtumọ̀ Yorùbá: – pre-built links to the most common WordPress, WooCommerce, Yoast SEO, Wordfence, and UpdraftPlus settings pages * 5 Starter Templates Ìtumọ̀ Yorùbá: – New Site Setup, Security Hardening, WooCommerce Launch, SEO Setup, Site Migration * JSON Export/Import Ìtumọ̀ Yorùbá: – share workflows between sites via JSON file * Paste a Checklist Ìtumọ̀ Yorùbá: – paste any list from Notion, Google Docs, or plain notes and it becomes a workflow instantly * Unlimited workflows Ìtumọ̀ Yorùbá: – no cap on the number of workflows per site * Up to 3 connected sites Ìtumọ̀ Yorùbá: – connect up to 3 sites to your free RoutineKit account * * RoutineKit Cloud dashboard Ìtumọ̀ Yorùbá: – manage connected sites from one place* * Fleet push & assignment Ìtumọ̀ Yorùbá: – push a workflow to connected sites and assign it to a site group * (up to 3 sites on free) #### Pro Features (Agency / Agency Pro) Pro is about scale. The features above keep working exactly as they do on the free plan; Pro raises the limits and adds the fleet-management layer on top. * Up to 50 sites (Agency) or unlimited sites (Agency Pro) Ìtumọ̀ Yorùbá: – connect your full client roster, not just 3 * Multiple site groups Ìtumọ̀ Yorùbá: – organise sites into as many groups as you need, then push to a whole group at once * Team members Ìtumọ̀ Yorùbá: – invite colleagues to your RoutineKit account so they can manage and run workflows across sites * Notes sharing Ìtumọ̀ Yorùbá: – include step notes in a push so receiving sites see them alongside the workflow * Progress sync Ìtumọ̀ Yorùbá: – see run completions from every connected site in your central dashboard * Priority support Ìtumọ̀ Yorùbá: – dedicated email support (Agency Pro only) ### External Services RoutineKit communicates with an external service **only when you explicitly connect to RoutineKit Cloud**. No data is sent to any external server without an active connection. #### RoutineKit Cloud When you enter a license key and connect to RoutineKit Cloud, this plugin sends data to and receives data from `https://app.routinekit.dev`. **Data sent:** * Your site URL, site name, and WordPress version (on connect and heartbeat) * RoutineKit plugin version (on heartbeat) * Workflow structure (title, steps) when you push a workflow to a site group * Execution completion status when a runner finishes a SaaS-assigned workflow **Data received:** * Workflow assignments pushed from your central dashboard * Template library available for your plan * License plan status **When this happens:** Only after you explicitly enter a license 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. This service is operated by the plugin author. It is optional Ìtumọ̀ Yorùbá: – the plugin is fully functional without it. * Service endpoint: https://app.routinekit.dev * Privacy policy: https://routinekit.dev/privacy * Terms of service: https://routinekit.dev/terms ### Privacy Policy 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. 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. 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. If you connect to RoutineKit Cloud (Pro), please review the RoutineKit Cloud privacy policy at https://routinekit.dev/privacy. ### Third-Party Libraries This plugin includes the following third-party library: * **html2canvas** (v1.4.1, MIT License) Ìtumọ̀ Yorùbá: – https://html2canvas.hertzen. com Used to capture screenshots of the admin screen for step evidence. Bundled once, as `assets/js/html2canvas.min.js`. ## Àwọn àwòrán ìbòjú [⌊Workflow Manager - list of all workflows with status and last-run date⌉⌊Workflow Manager - list of all workflows with status and last-run date⌉[ Workflow Manager Ìtumọ̀ Yorùbá: – list of all workflows with status and last-run date [⌊Import built-in Templates - Choose a template from the library⌉⌊Import built-in Templates - Choose a template from the library⌉[ Import built-in Templates Ìtumọ̀ Yorùbá: – Choose a template from the library [⌊Guided Runner - floating sidebar walking through each step⌉⌊Guided Runner - floating sidebar walking through each step⌉[ Guided Runner Ìtumọ̀ Yorùbá: – floating sidebar walking through each step ## Ìgbéwọlẹ̀ 1. Upload the `routinekit` folder to `/wp-content/plugins/` 2. Activate the plugin from the Plugins screen in WordPress 3. Go to **RoutineKit > Workflows** to create your first workflow 4. Use the **Run** button to open the guided Runner sidebar ## FAQ ### Is RoutineKit an automation tool? 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 Ìtumọ̀ Yorùbá:– 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. ### Who is it for? RoutineKit is built for WordPress agencies and freelancers managing multiple client sites. If youÌtumọ̀ Yorùbá: ’ve ever onboarded a new client, launched a WooCommerce store, or hardened a siteÌtumọ̀ Yorùbá: ’s security Ìtumọ̀ Yorùbá: – and done it slightly differently each time Ìtumọ̀ Yorùbá: – 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Ìtumọ̀ Yorùbá: ’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Ìtumọ̀ Yorùbá: ’re a solo developer with one or two sites, the free plan still works Ìtumọ̀ Yorùbá: – but the biggest value unlocks when youÌtumọ̀ Yorùbá: ’re managing a fleet. ### How does the guided runner work? 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. ### Is the free plan really free? Yes Ìtumọ̀ Yorùbá: – 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. ### Can my team use it? 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 Ìtumọ̀ Yorùbá: – theyÌtumọ̀ Yorùbá: ’ll see the runner panel and complete steps, but wonÌtumọ̀ Yorùbá: ’t be able to create or modify workflows. ### Does RoutineKit replace MainWP or ManageWP? 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. ### Can I share workflows between sites? 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 Ìtumọ̀ Yorùbá: – no exporting, no importing, no repeating yourself. ### How does Auto-Capture work? 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. ### Is my data sent anywhere? On the free plan, all data stays on your own site. Agency plans optionally connect to RoutineKit Cloud for cross-site management Ìtumọ̀ Yorùbá: – connection requires an explicit license key and can be revoked at any time from Settings > Cloud Connection. ### What happens if I deactivate the plugin? 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 Ìtumọ̀ Yorùbá: – RoutineKit will then drop its tables and options when the plugin is deleted. ### Can multiple team members run the same workflow? Yes Ìtumọ̀ Yorùbá: – each run is tracked separately as an execution with its own audit trail. Multiple people can run the same workflow on different sites simultaneously. ## Àwọn àgbéyẹ̀wò Kò sí àwọn àgbéyẹ̀wò fún plugin yìí. ## Àwọn Olùkópa & Olùgbéejáde “RoutineKit Ìtumọ̀ Yorùbá: – Repeatable WordPress Workflow Checklists for Agencies” jẹ́ ètò ìṣàmúlò orísun ṣíṣí sílẹ̀. Àwọn ènìyàn wọ̀nyí ti ṣe ìkópa sí plugin yìí. Àwọn Olùkópa * [ Zeeshan Rasool ](https://profiles.wordpress.org/codeleftover/) [Túmọ̀ “RoutineKit Ìtumọ̀ Yorùbá: – Repeatable WordPress Workflow Checklists for Agencies” sí èdè rẹ.](https://translate.wordpress.org/projects/wp-plugins/routinekit) ### Ṣe o nífẹ̀ẹ́ sí ìdàgbàsókè? [Ṣàwárí koodu](https://plugins.trac.wordpress.org/browser/routinekit/), ṣàyẹ̀wò [ibi ìpamọ́ SVN](https://plugins.svn.wordpress.org/routinekit/), tàbí ṣe àgbékalẹ̀ sí [àkọsílẹ̀ ìdàgbàsókè](https://plugins.trac.wordpress.org/log/routinekit/) nípasẹ̀ [RSS](https://plugins.trac.wordpress.org/log/routinekit/?limit=100&mode=stop_on_copy&format=rss). ## Àkọsílẹ̀ àwọn àyípadà #### 1.0.6 * Fixed: a site disconnected from the RoutineKit Cloud dashboard now notices. Until this release it went on believing it was connected Ìtumọ̀ Yorùbá: – the hourly sync failed silently every hour, the Cloud tab still showed Connected, and nothing said otherwise. The plugin now detects it, stops syncing, and explains what happened. * Improved: your license key is kept when this happens. The license is still valid and still covers your team Ìtumọ̀ Yorùbá: – only this siteÌtumọ̀ Yorùbá: ’s registration was withdrawn Ìtumọ̀ Yorùbá: – so reconnecting is one click rather than a hunt for the key. * Fixed: Sync now reported success when the connection was already dead. It now says what is actually wrong, and no longer suggests trying again when retrying cannot help. * Changed: refreshed the RoutineKit logo and admin icons Ìtumọ̀ Yorùbá: – the sidebar menu, admin bar and page header now carry the new mark. #### 1.0.5 * Security: credentials stored under short field names like `pass` or `access_oauth2_refresh` are now redacted before reaching Auto-Capture Ìtumọ̀ Yorùbá: – 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. * Improved: Auto-Capture now sees settings some plugins store in their own database tables instead of `wp_options` Ìtumọ̀ Yorùbá: – Wordfence and similar plugins previously went unnoticed no matter what was changed. * Improved: Auto-Capture now snapshots every option, not only the ones WordPress marks for autoloading. Some plugins store their entire configuration in a non- autoloaded option, which was invisible to captures before this. * Fixed: activating a plugin no longer fills the capture queue with the defaults it seeds on install. Only genuine settings changes are offered as workflow steps now. * Improved: the runner and toast notifications now sit above other plugins’ floating admin UI instead of being covered by it. * Improved: the plugin download is around 200KB smaller Ìtumọ̀ Yorùbá: – the screenshot library used for step evidence was being bundled twice. * Improved: that screenshot library now loads only when you actually take a screenshot, rather than on every admin page. #### 1.0.4 * New: a short guide below the workflow table covering the two ways to use Start Workflow Ìtumọ̀ Yorùbá: – working through a checklist, and building one as you go by adding steps from the runner while you make the changes. * Improved: deleting a workflow now says whether it worked, and when it is refused it gives the reason rather than failing quietly. * 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. * 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. * Changed: a workflow assigned to this site from the cloud can no longer be deleted here. Withdrawing an assignment is the sending siteÌtumọ̀ Yorùbá: ’s to do, and a deleted copy only returned on the next check. Archive it to take it out of the way. * 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. * Fixed: stopping a run left the workflow list showing it as still running until the page was reloaded. #### 1.0.3 * New: choose where the launcher lives Ìtumọ̀ Yorùbá: – 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. * New: assigning a group asks whether to tag it only or to push straight away, so you can line up several groups before distributing. * Improved: workflow table actions are now in a single ··· menu on each row, replacing the inline text links under the title. * 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. * 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 Ìtumọ̀ Yorùbá:– the copy is a separate workflow you can edit and push on its own terms. * Changed: toast notifications are off by default on new installs. Existing sites keep whatever they had set. * 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. * Fixed: steps could not be added, edited, reordered or deleted on a pushed workflow even where the screen offered it Ìtumọ̀ Yorùbá: – the change was rejected on save. Screens no longer offer an edit that would be refused. * 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. #### 1.0.2 * Improved: captures now record which settings screen they came from. * Security: sensitive option values Ìtumọ̀ Yorùbá: – passwords, API keys, tokens and salts Ìtumọ̀ Yorùbá: – are now redacted before they reach the Auto-Capture buffer. Values captured by earlier versions are overwritten automatically on upgrade. * 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. * Fixed: a settings save could write the same capture more than once. * Security: removed an unused diagnostic that kept recent REST request and response data in a browser variable on admin screens. #### 1.0.1 * New: Paste a Checklist Ìtumọ̀ Yorùbá: – 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. * Changed: plan buttons on the Upgrade screen now open the pricing page at routinekit. dev while self-serve signup is being finished * Fixed: a workflow whose steps are all optional no longer marks itself complete as soon as the first step is done * Fixed: completing optional steps after the last required one no longer resends the completion email or re-pushes the run to RoutineKit Cloud * Fixed: dismissing the “run is paused” notice in the Runner now sticks instead of reappearing on the next admin page #### 1.0.0 * Initial release * Workflow Builder with step editor and deep-link selector * Guided Runner floating sidebar * Auto-Capture engine for wp_options changes * 5 starter workflow templates * JSON export and import (file and URL) * Import from URL (requires connected RoutineKit account) * Auto-Capture retention configurable by all users (default: 30 days) * Pro: SaaS dashboard for cross-site fleet management and assignment push * Pro: notes sharing across sites * Pro: evidence upload per step * Pro: full audit trail with user attribution and option snapshots ## Àkójọpọ̀ Meta * Ẹ̀yà **1.0.6** * Ìgbàgbọ́hùn tó kẹ́yìn **ọ̀sẹ̀ 2 sẹ́yìn** * Àwọn ìgbéwọlẹ̀ tó ṣiṣẹ́ **100+** * Ẹ̀yà WordPress ** 6.0 tàbí ju bẹ́ẹ̀ lọ ** * Dánwò dé **7.1.2** * Ẹ̀yà PHP ** 7.4 tàbí ju bẹ́ẹ̀ lọ ** * Èdè * [English (US)](https://wordpress.org/plugins/routinekit/) * Àwọn àmì * [agency](https://yor.wordpress.org/plugins/tags/agency/)[audit trail](https://yor.wordpress.org/plugins/tags/audit-trail/) [checklist](https://yor.wordpress.org/plugins/tags/checklist/)[onboarding](https://yor.wordpress.org/plugins/tags/onboarding/) [site management](https://yor.wordpress.org/plugins/tags/site-management/) * [Ìwòye Tó Péye](https://yor.wordpress.org/plugins/routinekit/advanced/) ## Àwọn ìbò Kò sí ìwádìí tí a tíì fi ránṣẹ́. [Your review](https://wordpress.org/support/plugin/routinekit/reviews/#new-post) [Wo gbogbo àwọn àgbéyẹ̀wò](https://wordpress.org/support/plugin/routinekit/reviews/) ## Àwọn Olùkópa * [ Zeeshan Rasool ](https://profiles.wordpress.org/codeleftover/) ## Ìrànlọ́wọ́ Nǹkan wà tí o fẹ́ sọ? Ṣé o nílò ìrànlọ́wọ́? [Wo àpéjọ ìrànlọ́wọ́](https://wordpress.org/support/plugin/routinekit/)