WordPress Automation for Agencies: How to Scale Across Client Portfolios with Krom Automation
Krom Automation is the WordPress automation setup we recommend for agencies managing client portfolios in 2026. Its Enterprise licence covers unlimited sites, workflows export as portable JSON files you redeploy in minutes, and the visual canvas lets non-developers on your team build and maintain automations without writing a line of code. More importantly, it covers something no competitor article discusses: automating the client experience itself, not just your own operations.
Most agency guides stop at plugin updates, backups, and uptime alerts. Those are solved problems with commoditised tools. The real leverage is automating what happens between you and your client: onboarding sequences, progress notifications, approval triggers, and maintenance reporting.
An agency that automates its internal ops saves hours. An agency that also automates the client experience retains clients longer and closes retainers more easily.
This guide covers both layers. We will walk through licence economics across a real portfolio, the workflow reuse system that makes scaling practical, the baseline automation set every client site should run, and the client-facing automations that separate a premium agency offering from a commodity one.
Browse the full Krom Automation feature list to see what is available before you build your first workflow.
The Licence Maths Agencies Actually Need to See
Most automation plugins price per site without offering a meaningful bulk option. That model is fine for a single product business. For an agency billing across 20 or 50 client sites, it compounds fast and often makes per-site billing from an external tool like Zapier look cheaper than it is, until you account for task limits and per-execution charges.
Here is what Krom Automation Pro costs across a real portfolio at each plan tier, compared to what you would spend if you licensed per site at the Basic rate.
| Portfolio Size | Basic ($299 lifetime, 1 site) | Standard ($499 lifetime, 5 sites) | Enterprise ($799 lifetime, unlimited) |
|---|---|---|---|
| 5 sites | $1,495 | $499 | $799 |
| 10 sites | $2,990 | $998 (2 licences) | $799 |
| 25 sites | $7,475 | $2,495 (5 licences) | $799 |
| 50 sites | $14,950 | $4,990 (10 licences) | $799 |
Lifetime figures tell the clearest story for long-term portfolio planning. Annual pricing follows the same curve: Enterprise annual covers unlimited sites for $369 per year, so at 10 sites that is $36.90 per site per year, and at 50 sites it is $7.38 per site per year. No per-execution billing, no task caps, no upsell at 10,000 workflow runs.
The 14-day money-back guarantee applies to every plan, so you can run the full portfolio setup and verify it works before the window closes.
The automation tools that look cheapest per site are rarely cheapest per portfolio. Run the maths at your actual site count before you commit.
Workflow Reuse: The JSON Export System
Licence cost is one axis of the agency value calculation. Time cost is the other. Building the same welcome email sequence, the same new-user role assignment, the same WooCommerce order notification workflow from scratch on every client site is exactly the kind of repetitive work automation is supposed to eliminate.
Krom Automation solves this with portable JSON import and export. Any workflow you build on one site exports as a single JSON file, and you import it on any other site in under a minute.
The workflow arrives complete with its trigger, every action, all conditional branches, delay settings, and merge tags intact. The practical agency workflow looks like this:
- Build and test a workflow on your own staging or internal site.
- Use the workflow simulator to run a dry-run test with zero real side effects before deploying to any client.
- Export the JSON file.
- Import it to each client site in sequence, adjust any client-specific details such as notification email addresses or sender names, and activate.
- Store the JSON files in your project management system or a shared drive as your agency’s reusable automation library.
Over time, your library grows to cover every common scenario your clients need. The second client who needs a membership welcome sequence costs you 5 minutes instead of 90. By the tenth client, that template is battle-tested and the import takes less time than explaining the workflow verbally.
The Baseline Automation Set for Every Client Build
Every new client site should launch with a standard automation stack installed from your library. The following eight workflows cover the scenarios that generate the most manual agency work when left unautomated.
- Welcome email on user registration: Fires the moment a new account is created. Sends a branded onboarding email with login details, next steps, and support contact. Without this, new users either get WordPress’s default notification or nothing.
- Failed login alert to admin: Triggers on repeated failed login attempts and sends a notification email. Catches brute-force attempts before they become a client panic call.
- New comment notification: Notifies the client when a comment is submitted, so they can respond within a business day rather than discovering it weeks later.
- Post published notification: Sends the client a confirmation email when content goes live, including a direct link to the published post. Eliminates the “did it go up?” message.
- WooCommerce order created alert: Notifies the client immediately on each new order. Useful for clients who do not check their WooCommerce dashboard hourly.
- WooCommerce order completed sequence: Triggers when an order reaches Completed status and sends a follow-up email to the customer, optionally adding them to a Mailchimp or FluentCRM list for post-purchase marketing.
- Media upload log: Logs every media upload to the execution history. Provides a lightweight audit trail for client sites with multiple contributors.
- Password reset confirmation: Sends a branded confirmation message when a user resets their password. Replaces the generic WordPress default and reduces support queries.
All eight are buildable with the free version’s 16 triggers and 21 actions. Deploy them from your JSON library and a full client site baseline takes under 20 minutes to configure.
The Layer Nobody Else Covers: Client-Facing Automation
Every guide on agency WordPress automation covers the same ground: bulk plugin updates, backup schedules, uptime monitoring. Those tools are worth using. But none of them addresses what actually drives client satisfaction and retainer renewals: the quality of the client experience your agency delivers.
A client who receives automated progress updates, onboarding confirmations, and monthly maintenance summaries perceives more value from their retainer than a client who gets silence between invoice cycles. The automation does not replace your account management. It fills the gaps between touchpoints with consistent, professional communication that would otherwise fall through the cracks.
Clients who hear from you between invoices cancel retainers less. Automation is what makes consistent communication feasible at scale.
Client Onboarding Workflow
When a new client site goes live, a structured onboarding sequence sets expectations and reduces the first month of support volume significantly. A typical sequence built in Krom Automation looks like this:
- Day 0: Welcome email fires on User Registered trigger, contains login link, support contact, and a link to your client portal or documentation.
- Day 2: Delay action fires a follow-up email asking if they have successfully logged in and if they have questions.
- Day 7: A second follow-up covers the features they are most likely to use incorrectly in the first month.
- Day 30: A check-in email prompts a review call booking or satisfaction survey.
The entire sequence runs automatically once the client’s user account is created. You build it once, export it as JSON, and deploy it on every new client site. The delays and scheduling documentation covers how to configure multi-day sequences with the delay action.
Maintenance Reporting Automation
A common agency pain point is monthly maintenance report generation. Done manually, a five-minute report per client across 20 clients is at minimum two hours of work, plus the cognitive overhead of remembering to do it. At an agency billing rate of $100 to $150 per hour, that is $200 to $300 of unbillable time every month, or $2,400 to $3,600 per year.
Krom Automation’s Schedule trigger (Pro) fires on a recurring monthly basis and can trigger an HTTP Request action that calls an external reporting endpoint, or a Send Email action that delivers a summary directly to the client. Combined with merge tags to inject dynamic data, each client receives a personalised summary without manual input. See the Schedule trigger documentation for setup details.
Form Submission Routing
Client sites that use contact forms, lead forms, or quote request forms often need submissions routed to different destinations: the client’s inbox, your agency’s project management tool, a CRM, and sometimes a Slack channel. Doing this routing manually or through form plugin notification settings alone creates fragile, hard-to-audit chains.
Krom Automation integrates natively with Gravity Forms, WPForms, Contact Form 7, and Fluent Forms. A single form submission can trigger a client notification email, a Slack message to your team, and a contact record creation in FluentCRM, all in one workflow with full execution logging so you can verify every step fired.
What Actually Breaks at Scale, and How to Handle It
Scaling automation across a portfolio introduces failure modes that single-site users never encounter. Knowing them upfront saves hours of debugging.
| Risk | What Goes Wrong | The Fix |
|---|---|---|
| WP-Cron on low-traffic client sites | Delayed workflows fire hours late because nothing visits the site to trigger cron | Configure a real server cron job on hosting, or use a managed host that runs cron independently |
| AI actions without a key configured | Workflows using AI Generate Text fail silently on sites where no API key is set | Either exclude AI actions from the baseline template library or document the key setup step in your onboarding checklist |
| Run-once enforcement not set | Retry logic fires a workflow multiple times for the same event on high-traffic sites | Enable run-once per entity on any workflow that should fire exactly once per user or order |
| Execution logs filling on large sites | The 9 custom database tables grow without pruning on busy sites | Review the execution history settings and set a log retention period appropriate to the client’s database size |
| Merge tags referencing fields that do not exist | Emails send with empty fields because a client’s setup omits a field the template expects | Use the workflow simulator to test every template on the target site before activating |
The failure notification system catches most of these automatically. When a workflow step fails, Krom Automation sends an email alert and queues an automatic retry with configurable backoff.
You do not need to monitor every client site manually for automation failures. The failures come to you.
When to Use External Tools Alongside Krom Automation
Krom Automation is WordPress-native. The trigger or the action needs to touch the WordPress site. If a client needs automation between two external services with no WordPress involvement, such as syncing a CRM to an accounting platform, a dedicated external tool handles that better.
The practical agency stack for most client portfolios looks like this:
- Krom Automation for all WordPress-native triggers and actions: user events, post events, WooCommerce, forms, and client-facing email sequences.
- A managed WordPress host with built-in backup, uptime monitoring, and security scanning so you are not building those from scratch in a workflow.
- A single external automation tool (Make.com or similar) for the rare workflows that genuinely involve only external services, with the Krom Automation incoming webhook receiver as the bridge when WordPress needs to be the trigger.
That last point is worth noting. Krom Automation Pro includes an incoming webhook receiver with HMAC-SHA256 signature verification and nine security layers. An external service can fire a webhook to your client’s WordPress site and trigger any workflow you have built, bridging the gap between the WordPress-native world and the external automation world without abandoning either.
The incoming webhook receiver turns the client’s WordPress site into a participant in external automation chains, not just a recipient of them.
The Agency Cost Calculation: Build vs. Buy vs. Automate
Before committing to any automation setup, run the honest numbers on what the manual version actually costs.
| Task | Manual Time per Client per Month | 20-Client Portfolio Cost (at $100/hr) | Automation Setup Time (One-Off) |
|---|---|---|---|
| Monthly maintenance report | 30 min | $1,000/month | 2 hours |
| Client onboarding sequence | 45 min per new client | Varies, typically $450/month at 10 new clients | 3 hours (reusable template) |
| Form submission routing | 10 min/week | $800/month across portfolio | 1 hour per site type |
| New user welcome email | 5 min per new user | Scales with client growth | 30 minutes (reusable template) |
The maintenance report row alone justifies the Enterprise licence cost inside a single month for most agencies. At $100 per hour and 20 clients, manual reporting costs $1,000 monthly.
The Enterprise annual licence is $369 per year. The payback period is measured in days, not months.
If you want a broader view of what WordPress automation costs across different tools and pricing models, our WordPress automation pricing comparison covers the full landscape.
Getting Started: The Agency Setup Sequence
Work through these steps in order. Skipping to the client deployment before building and testing your template library on your own site first will cost you more time than following the sequence.
- Install the free plugin on your internal staging or agency site. The free version’s 16 triggers and 21 actions cover everything needed to build and test your baseline templates.
- Build the eight baseline workflows described earlier in this guide. Test each one with the workflow simulator before exporting.
- Export each workflow as JSON and store the files in your shared agency drive, labelled clearly by use case and client type.
- Upgrade to Enterprise Pro on your agency’s internal site if you need the Schedule trigger, incoming webhook receiver, or visual email builder. Deploy Pro on client sites as needed using your licence activations.
- Import your template library on the first client site, configure client-specific variables, and run the simulator again on the live site before activating.
- Document the import checklist so any team member can deploy a new client site’s automation stack in under 30 minutes.
The step-by-step workflow builder guide covers the canvas mechanics if anyone on your team is building their first workflow.
Who Should and Should Not Use This Setup
This setup makes the most sense for agencies managing 5 or more WordPress client sites, billing on retainer, and looking to systematise rather than manually execute recurring tasks. The Enterprise licence economics do not make sense below about 4 sites, where Standard pricing is cheaper. Agencies that primarily build and hand off sites rather than managing them on retainer get less value from the scheduling and reporting automation layer, though the baseline template library still saves time on every build.
If your agency is already deeply invested in an external automation platform with hundreds of existing flows, migration carries a real cost in rebuild time. We wrote an honest assessment of moving WordPress automations off Zapier if you are evaluating that transition.
The free version is available on the WordPress.org plugin directory with no trial period, no run caps, and no features locked away. Start there, build your template library, and upgrade when the Pro triggers earn their cost.
See the full Krom Automation pricing and compare all three plans before your next client build.
Frequently Asked Questions
Can one Krom Automation licence cover all my client sites?
The Enterprise plan covers unlimited sites under a single licence, available as an annual subscription or a one-time lifetime purchase. Every Pro feature is included at every plan tier. The only difference between plans is the number of sites covered.
Do workflows transfer between client sites automatically?
No transfer is automatic, but the JSON export and import system makes it fast. Export a workflow from one site, import the JSON file on another, adjust any site-specific settings, and activate. The entire workflow including triggers, actions, branches, and delays imports intact.
What happens if a client’s site has very low traffic?
Krom Automation runs on Action Scheduler, which depends on WP-Cron. On very low-traffic sites, WP-Cron may fire late unless a real server cron job is configured.
This affects delayed workflows more than immediate ones. Most managed WordPress hosts support server-level cron configuration.
Can clients manage their own automations, or does that require agency involvement?
The visual canvas is designed to be usable without code. A client with WordPress admin access could view, pause, or edit workflows. Most agencies restrict this by role, giving clients visibility into execution history without edit access to the workflow logic.
Does Krom Automation work with the form plugins our clients already use?
Pro integrations include Gravity Forms, WPForms, Fluent Forms, Contact Form 7, Elementor Forms, and Ninja Forms. Each integration supports form submission as a trigger, so any form on a client site can kick off a workflow.
Is there a run limit or task cap on any plan?
No. Krom Automation does not charge per execution, per task, or per workflow run on any plan, free or Pro. The only variable between plans is the number of licensed sites.