An agent can list the workflows the site owner has exposed and trigger any one of them by name, with the workflow running locally using the site's own AI provider keys.
View AI Workflow Automation on WordPress.org
Requires WordPress 6.2 or newer with AI Workflow Automation active and its agent-exposure setting turned on. Every ability's permission_callback checks the manage_options capability by default, filterable via the wp_ai_workflows_abilities_capability filter.
wp-ai-workflows/list-workflows is a fixed, literal id. Beyond it, one ability registers per exposed workflow as 'wp-ai-workflows/run-' plus a slug of that workflow's own id, so the full set cannot be enumerated from source alone.
Grouped by what each one can change. Every one starts off until you enable it.
Lists the active workflows currently exposed to agents, each with its runnable ability name and trigger type.
Runs one exposed workflow locally with the caller's input and returns its output; one such ability is registered per exposed workflow, named from that workflow's own id.
Four steps from two active plugins to a governed connection.
Both plugins need to be active on the same WordPress site. AI Workflow Automation registers its own abilities; this plugin discovers and governs them.
In Agent Abilities for MCP, open the Bridge tab (labeled "Other plugins" in the admin). Abilities from every registered plugin appear there, grouped by the plugin that registered them.
Every ability from AI Workflow Automation starts off. Turn on only the ones you want an agent to reach, or enable the whole set in one click.
Approve the connection as a WordPress account scoped to what you actually want the agent to do. Each call still re-checks that account’s capability before it runs.
Read more in how bridging works or the full documentation.
Conditionally. A fixed discovery ability registers once the site owner opts in, and one more ability registers per active workflow that has a manual or webhook trigger and is exposed, up to 100, so the exact set of runnable abilities depends on the site's own workflow library.
The plugin's opt-in setting (wp_ai_workflows_settings.expose_to_agents) must be on; nothing registers otherwise.. Per-workflow run abilities register only for workflows with status 'active' and a manual or webhook trigger, capped at the first 100 that qualify..
Requires WordPress 6.2 or newer with AI Workflow Automation active and its agent-exposure setting turned on. Every ability's permission_callback checks the manage_options capability by default, filterable via the wp_ai_workflows_abilities_capability filter.
An agent can read OttoKit's SaaS connection status, access-control settings, system health (cron jobs, database table, webhook log counts), configured automation triggers, which supported integrations are active, and paginated webhook execution logs.
Once an operator turns on the relevant feature toggles, an agent can read a site's exposed settings, users, and post content and terms, and can ask the plugin's AI experiments to draft or suggest excerpts, titles, slugs, meta descriptions, editorial notes and updates, summaries, translations, classifications, type-ahead text, image alt text, generated images, and comment moderation or reply suggestions, though running the content-generation ones also needs an AI connector configured.
An AI agent can create a new AutomatorWP automation, add triggers or actions to an existing one, and run or execute an automation's actions immediately, using AutomatorWP's own no-code automation builder.
Verified from AI Workflow Automation's own free wordpress.org code on 28 September 2026, not from its marketing claims. Not every ability listed here has been run end to end against a live site. Plugin authors change their code, so a name, a capability, or a condition can be different in a later release. This site is not affiliated with, or endorsed by, massiveshift or AI Workflow Automation. Back to the full directory.
Every ability starts off, is scoped to the user you connect, and is written to the same audit log as core. Turn on only what you need.
Off by default. Capability checked on every call.