WordPress Automation Glossary: Every Term Explained

This glossary covers every WordPress automation term you are likely to encounter, from the basics like triggers and actions to the technical layer underneath, including webhooks, cron jobs, REST API calls, and conditional branching. Each definition stands alone, so you can jump to any term without reading the rest. If you are building your first workflow or evaluating an automation plugin, these are the words you need to know before you start.

The vocabulary around WordPress automation borrows from general programming, from SaaS tools like Zapier and Make, and from WordPress’s own hook system. That mix creates genuine confusion because the same word sometimes means different things depending on the context. This glossary untangles those overlaps explicitly.

We built Krom Automation, a visual workflow automation plugin for WordPress, so we live inside this vocabulary every day. The definitions below reflect how these terms work in practice, not just in theory. Browse the full feature list to see how they apply inside a real plugin.

Core Concepts: The Vocabulary Every Automation Starts With

Trigger

A trigger is the event that starts a workflow. It is the “if this” in the “if this, then that” model. In WordPress, triggers map to real site events: a user registers, a post publishes, a WooCommerce order completes.

No trigger means no automation runs. The number of distinct triggers a plugin offers determines how much of your site’s activity it can actually respond to. Krom Automation’s free version includes 16 built-in triggers across users, posts, comments, media, and WooCommerce.

Action

An action is what happens after the trigger fires. It is the “then that” half. Examples include sending an email, creating a post, changing a user role, or making an HTTP request to an external service.

A single trigger can chain multiple actions in sequence. The distinction between a WordPress “action hook” (a developer concept) and an automation “action” (a workflow step) confuses beginners, but the two are unrelated in daily use. See the full free actions reference for a complete list of what each action does.

Workflow

A workflow is the complete automation: one trigger connected to one or more actions, with optional conditions and delays between them. Some tools call this a “recipe” (Uncanny Automator), a “flow” (FlowMattic), or a “scenario” (Make). The word differs by product but the structure is the same.

A workflow sits dormant until its trigger fires, then executes top to bottom. How Krom Automation works walks through the trigger-action-workflow relationship in detail.

Recipe

Recipe is Uncanny Automator’s term for a workflow. A recipe contains one trigger and any number of actions. Outside Uncanny Automator, most WordPress automation tools use “workflow” instead.

The concepts are identical. If you see documentation that refers to recipes and you are using a different plugin, read “recipe” as “workflow” throughout.

The word “recipe” means exactly the same thing as “workflow.” The terminology differs by product, but the confusion it causes is real and completely avoidable.

Canvas

A canvas is the visual interface where you build a workflow by placing and connecting nodes. It replaces the older list-based rule editor pattern, where triggers and actions lived in dropdowns stacked vertically. A canvas makes branching logic, delays, and parallel paths readable at a glance.

Not every automation plugin uses a canvas. List-based editors are still common in simpler tools. Krom Automation uses a drag-and-drop canvas built on ReactFlow with auto layout, which means nodes reposition automatically as you add steps.

Logic and Control Flow

Conditional Logic / Conditional Branching

Conditional logic adds a decision point to a workflow. Instead of every trigger firing the same actions every time, a condition checks a value and routes execution down a Yes path or a No path.

For example: “if the new user’s role is ‘subscriber’, send welcome email A; if their role is ‘editor’, send welcome email B.” Without conditions, you need a separate workflow for every variation. Conditions and branching in Krom Automation covers how to add Yes/No logic to any workflow step.

Delay / Delay Scheduling

A delay pauses execution between steps for a set amount of time. Delays are used to space out a welcome email sequence (send immediately, then again after 3 days, then again after 7 days), to wait for a payment to clear before granting access, or to schedule a reminder before an event. Delay units in Krom Automation include minutes, hours, days, weeks, or a custom number of seconds.

Delays depend on WordPress Cron to fire on time, so very low-traffic sites may see delays fire late unless a real server cron is configured. See delays and scheduling documentation for configuration details.

Run Once

Run once is a setting that prevents a workflow from executing more than one time for the same entity, usually a user or a post. Without it, a workflow triggered by “user login” would run every time that user logs in, which is usually not what you want for a one-time onboarding sequence.

Run once enforcement is stored per entity in the workflow’s execution log. Krom Automation includes this in the free version.

Loop

A loop repeats an action across a list of items. For example: for every subscriber on a list, send a personalised email. Loops are common in more advanced automation platforms and in developer-level WordPress automation.

In no-code WordPress plugins, looping is less common and is usually handled by Pro tiers when it exists. It is worth checking whether a plugin’s free tier supports loops before building a workflow that requires them.

Data and Dynamic Values

Merge Tags / Dynamic Variables

Merge tags are placeholders that inject live data from the trigger event into any action field. If your trigger is “User Registered” and your action is “Send Email”, a merge tag like {{user_email}} inserts the actual email address of the user who just registered. Without merge tags, every automated email would be identical.

With them, every execution is personalised to the specific event that fired. Merge tags in Krom Automation lists every available variable and how to use them inside action fields.

Token

Token is another word for merge tag, used primarily in Uncanny Automator. A token pulls data from the trigger and makes it available to downstream actions.

If you see “token” in automation documentation, treat it as a synonym for merge tag. The underlying mechanism is the same: a variable that resolves to a real value at execution time.

Execution Log

An execution log records every time a workflow runs, including which trigger fired, which actions executed, whether each step succeeded or failed, and the exact data passed between steps. Execution logs are essential for debugging.

A workflow that runs silently and produces no output is impossible to diagnose without a log. Krom Automation stores a full per-step audit trail for every execution, which means you can see exactly where a workflow broke and why.

A workflow that fails silently looks identical to a working one until you check the execution log. Per-step logging is not a premium feature you can skip.

Payload

A payload is the data package sent with an event or request. When a webhook fires, it sends a payload, typically formatted as JSON, containing all the details of what happened.

When you make an HTTP request action, the payload is the body of the request you send to the external service. Understanding payloads matters when connecting WordPress to external APIs, because the structure of the payload determines what the receiving service can do with the data.

Connections to External Services

Webhook

A webhook is an HTTP request sent automatically when a specific event occurs. Instead of your site checking an external service every few minutes to see if anything changed (polling), the external service pushes data to your site the moment it happens (webhook). Webhooks require a receiver URL that accepts the incoming request.

Krom Automation Pro includes an incoming webhook receiver with HMAC-SHA256 signature verification and 9 security layers. For a deeper explanation of how webhooks work in WordPress specifically, see Webhooks Explained Without the Jargon.

HTTP Request / API Call

An HTTP request is how WordPress communicates with external services. When your workflow needs to send data to Slack, update a record in Airtable, or trigger an action in any tool that has an API but no native integration, you send an HTTP request.

Krom Automation’s free HTTP Request action supports GET, POST, PUT, PATCH, and DELETE methods with JSON response parsing, which means you can connect to any external service with an API without writing code. See how to connect any external service to WordPress for a practical walkthrough.

REST API

The WordPress REST API is a built-in interface that lets external applications read and write WordPress data over HTTP. It is the mechanism behind mobile apps, headless WordPress setups, and many automation integrations.

When a tool says it “uses the WordPress REST API”, it means it sends requests to endpoints like /wp-json/wp/v2/posts rather than loading WordPress pages directly. Krom Automation exposes its own REST API under the krom-automation/v1 namespace, which lets developers trigger workflows, query execution logs, and manage workflows programmatically.

Integration

In automation contexts, an integration is a pre-built connection between your WordPress site and a specific external service. Integrations package the authentication, the trigger definitions, and the action definitions for a third-party tool so you do not have to configure raw HTTP requests.

Krom Automation Pro includes 24 integrations covering forms, e-commerce, CRM, email marketing, LMS, membership, messaging, social media, data storage, productivity, and affiliate tools. Examples include the Mailchimp integration for subscriber sync and the Google Sheets integration for data storage.

Native vs. SaaS Automation

Native automation runs on your WordPress server. SaaS automation (Zapier, Make, n8n cloud) runs on a third-party platform and connects to your site via API or webhook. Native automation keeps all data, credentials, and execution logs inside your own database.

SaaS automation adds a dependency on an external platform and routes your site’s data through it. For sites handling personal data, order information, or customer records, the distinction matters.

See self-hosted vs. SaaS automation and data privacy for a comparison of the two approaches.

WordPress-Specific Technical Terms

Hook (WordPress Core)

A hook is a WordPress developer concept that lets code interrupt WordPress at a specific point to run custom functions. There are two types: action hooks (which run code at a point in execution) and filter hooks (which modify data passing through). Hooks are what automation plugins use under the hood to detect that a trigger event happened.

When a user registers, WordPress fires the user_register action hook, and an automation plugin listens for that hook to start a workflow. As a non-developer using an automation plugin, you interact with hooks indirectly through the trigger interface, not directly in code.

Action Hook vs. Filter Hook

An action hook lets you run code at a specific moment during WordPress execution. A filter hook lets you modify a value before WordPress uses it. Action hooks are what most automation triggers are built on, because they fire when something happens.

Filter hooks are used more in theme and plugin development to transform data. If you are configuring an automation plugin and not writing PHP, you will almost never need to distinguish between them. The distinction matters only when you are writing custom trigger or action extensions.

WP-Cron

WP-Cron is WordPress’s built-in task scheduler. Instead of a real operating system cron job, WP-Cron runs scheduled tasks the next time any visitor loads a page after the scheduled time. This means that on low-traffic sites, a task scheduled for 9:00 AM might not run until 11:00 AM when the first visitor arrives.

Automation delays and scheduled workflows rely on WP-Cron by default. For reliable timing, replace WP-Cron with a real server cron that calls wp-cron.php at a fixed interval. Krom Automation uses Action Scheduler on top of WP-Cron, which adds a persistent job queue and retry logic, but the underlying dependency on site traffic still applies.

Action Scheduler

Action Scheduler is an open-source job queue library originally built for WooCommerce. It stores scheduled tasks in the database and processes them in the background, separate from page loads.

This is more reliable than raw WP-Cron for high-volume tasks because it does not lose jobs on a slow page load and supports automatic retry on failure. Krom Automation runs all workflow executions through Action Scheduler, which means nothing blocks while a workflow runs and failed jobs retry automatically with configurable backoff.

Cron Job (Server Level)

A cron job is a scheduled task configured at the server operating system level, independent of WordPress. It runs at a precise time regardless of site traffic. A server cron job is the correct fix when WP-Cron timing is unreliable.

It is configured in the server’s crontab file and typically calls wp-cron.php every minute or every five minutes. If your host does not give you crontab access, most managed WordPress hosts offer a scheduled task feature as an alternative.

Background Processing

Background processing means running tasks outside the normal request-response cycle that serves a page to a visitor. Without background processing, every automation action would slow down the page load of whatever triggered it. With background processing, the trigger fires, WordPress queues the job, the page load completes at normal speed, and the workflow executes separately a few seconds later.

This is why plugins that run automation correctly have no measurable effect on frontend performance. See do automation plugins slow down WordPress for the full answer.

Workflow Builder Features

Visual Builder / Drag-and-Drop Canvas

A visual builder is a graphical interface for constructing workflows by placing and connecting blocks on a canvas, rather than filling in form fields or writing code. Drag-and-drop means you move nodes by clicking and dragging them. Not all automation plugins use a visual builder.

Many use a vertical list of configured rules, which works for simple linear flows but becomes hard to read when branching logic is involved. Using the visual workflow builder in Krom Automation covers canvas navigation, node placement, and auto layout.

Node

A node is a single step on a workflow canvas. Each node represents either the trigger, an action, a condition, or a delay. Nodes connect to each other with lines showing the direction of execution.

On a branching workflow, a condition node splits into two output lines: one for Yes, one for No. The node-based model makes complex workflows readable because the structure is visible rather than implied by a list order.

Simulator / Dry Run

A simulator lets you test a workflow without actually executing its actions. It walks through the workflow logic using test data and shows you what would have happened at each step: which path a condition would have taken, what value a merge tag would have resolved to, which action would have fired.

Dry run testing prevents the classic problem of discovering a workflow error by watching it send 500 emails to real users. Testing workflows with the simulator explains how to set up and read a dry run result.

Import / Export

Workflow import and export lets you save a complete workflow as a portable file, typically JSON, and restore it on another site. This is useful for agencies deploying the same automations across client sites, for backing up workflows before making changes, and for sharing workflow templates with other users. Krom Automation supports import and export as JSON in the free version, with no licence restriction on the number of workflows you can export.

A workflow you cannot export is a workflow you cannot back up. Import/export is not a nice-to-have feature once you have more than three active workflows.

Execution Analytics

Execution analytics summarise how your workflows are performing over time. Useful metrics include total executions, success rate, failed execution count, and execution trend over a date range. Per-workflow breakdowns show which automations run most often and which fail most often.

Without analytics, a workflow failing 15 percent of the time looks identical to a healthy one. Krom Automation’s analytics dashboard is included free and covers all of those metrics. The reports page adds date range filtering and CSV export.

Plan and Licensing Terms

Free vs. Pro

Most WordPress automation plugins offer a free version on WordPress.org and a paid Pro version with additional triggers, actions, and integrations. The division matters because the free version determines what you can build without paying anything. Krom Automation’s free version includes 16 triggers, 21 actions, 20 workflow templates, and AI actions with no paywall.

Pro adds 80+ additional triggers, 60+ additional actions, 24 integrations, and 101 additional templates. See the free vs. Pro feature comparison for the exact breakdown.

Per-Task Billing

Per-task billing charges you a fee for each automation execution, rather than a flat annual or lifetime licence. Zapier and Make both use this model: you buy a number of “tasks” or “operations” per month, and every action in every workflow consumes one.

A busy site can exhaust a monthly allowance quickly. Native WordPress automation plugins, including Krom Automation, charge a flat licence fee with no per-execution billing at any tier.

Annual vs. Lifetime Licence

An annual licence grants access to the plugin and updates for one year and requires renewal to continue receiving updates. A lifetime licence grants permanent access and updates for a one-time payment.

Lifetime licences carry more upfront cost but lower long-term cost. Krom Automation offers both, with annual plans starting at $119 for one site and lifetime plans starting at $299 for one site.

Site Activation / Site Licence

A site activation is a single installation of a Pro plugin on one WordPress site. A licence covers a specific number of activations. A 5-site licence lets you install the Pro version on up to 5 different WordPress installs.

Krom Automation’s Standard plan covers 5 sites for $199 per year or $499 lifetime. The Enterprise plan covers unlimited sites for $369 per year or $799 lifetime.

Also from wpRigel

Pollify is wpRigel’s Gutenberg-native poll, survey, and quiz plugin. Polls are built as real blocks inside the editor, so there are no shortcodes to paste and no separate admin interface to learn. If you run a site that collects audience feedback, it fits directly into the writing workflow you already use.

Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl plus K to jump to any page, search any content, and run admin actions without clicking through menus. It is the only command palette plugin with genuine WooCommerce depth: orders, products, and customers are all first-class commands, not an afterthought.

What to Build First

If this glossary is your starting point, the most useful next step is building one workflow before exploring every feature. The classic starting workflow is a welcome email triggered by user registration: one trigger, one action, one merge tag.

Your first workflow: send a welcome email when a user registers walks through every step. After that, the what to automate first on a WordPress site guide covers which automations make the biggest practical difference, in the order that makes sense to tackle them.

The free version of Krom Automation is available on the WordPress.org plugin directory with no trial period, no run caps, and no features held back from non-paying users. Download it free and build your first workflow today.

When you are ready to add integrations like FluentCRM, LearnDash, or Slack and Telegram messaging, Pro plans start at $119 per year. See full pricing details and compare the three plans side by side.

Frequently Asked Questions

What is the difference between a hook and a trigger in WordPress automation?

A hook is a WordPress developer concept used in PHP code to listen for events inside WordPress core. A trigger is the user-facing term in automation plugins for the same underlying event.

When you select “User Registered” as a trigger in Krom Automation, the plugin is listening to the user_register hook under the hood. You interact with triggers, not hooks, unless you are writing custom extensions in PHP.

Is a recipe the same as a workflow?

Yes. Recipe is the term Uncanny Automator uses for what most other automation plugins call a workflow.

Both describe the same structure: one trigger connected to one or more actions, with optional conditions and delays. The word is product-specific, not a technical distinction.

What is the difference between an action hook and a filter hook in WordPress?

An action hook runs code at a specific moment during WordPress execution without changing any output. A filter hook modifies a piece of data before WordPress uses it.

In the context of automation plugins, action hooks are the mechanism most triggers are built on, because they fire when something happens. As a non-developer using a plugin’s interface, you will almost never need to distinguish between them.

Does WP-Cron affect automation delays and scheduled triggers?

Yes. WP-Cron only fires when a page is loaded on your site, so on low-traffic sites a delay or scheduled trigger may run later than intended.

The fix is to disable WP-Cron in wp-config.php and add a real server cron job that calls wp-cron.php every minute. Most managed WordPress hosts offer a scheduled tasks interface as an alternative to direct crontab access.

What is the difference between per-task billing and a flat licence?

Per-task billing charges a fee for every automation execution, so a site that runs 10,000 workflow actions per month pays proportionally more than one running 100. A flat licence charges a fixed annual or lifetime price regardless of how many workflows run. Native WordPress automation plugins like Krom Automation use flat licensing, while SaaS platforms like Zapier and Make use per-task billing.

What is a merge tag and where do I use one?

A merge tag is a placeholder you insert into an action field that resolves to live data from the trigger event at execution time. For example, placing {{user_first_name}} in an email subject line inserts the actual first name of whoever triggered the workflow. Merge tags work in any text field inside an action, including email subjects, email bodies, post titles, and HTTP request payloads.