AI Workflow Automation vs OpenStation

Website and docs: https://wpaiworkflowautomation.com What reviewers say “You can design these workflows using an intuitive drag-and-drop editor, and access multiple AI models from the same user interface.” (WPBeginner) “AI Workflow Automation stands out as a powerful solution if you want to leverage AI within the WordPress ecosystem.” (WP Mayor, rated 4.5 out of 5) Turn WordPress into an AI automation platform, visually, without code. Drag nodes onto a canvas, connect them, and build real, multi-step workflows and AI agents right inside wp-admin. Draft and optimize content, answer visitors with an AI chatbot, run form-to-AI automations, scrape and research the web, and keep a human in the loop for approvals. Powered by leading models from OpenAI, Anthropic, and OpenRouter: hundreds of models through one interface. It is genuinely free. Bring your own AI provider API key and every workflow runs locally on your own server: unlimited, with no account and nothing sent to us. When you’d rather not manage keys or worry about PHP timeouts, flip any workflow to Cloud and run it on our hosted engine with a free connected account. You choose, per workflow, whether it runs Local (your key) or Cloud (our hosted engine), and you can mix both on the same site. Why AI Workflow Automation A real free tier, not a trial. The visual builder, ~20 node types, every trigger, local execution, and the chat widget are free forever with your own key (BYOK). No account needed, no lock-in. Visual, multi-step automations and agents. Not single-shot prompts: chain trigger, AI, logic, and action into genuine automations on a drag-and-drop canvas (React Flow), then watch each run live. AI agent chatbots that do things. Deploy a chatbot that can search your posts and WooCommerce products, show rich cards, and call your workflows as tools, governed by per-tool approval gates, rate limits, and one-click human handoff to Chatwoot, Zendesk, or Intercom. Human in the loop, built in. Pause any workflow for a person to review, edit, or approve AI output. Pending approvals and hand-offs collect in a dedicated Tasks page and a real-time Operator Inbox. Your keys, or ours. Run on your own key for free, or connect a free account and use hosted AI with no key management at all. Your provider keys never leave WordPress. WordPress-native, agency-ready. Trigger from core events and the major form plugins, expose workflows as core Abilities / MCP tools on WordPress 7.0 (opt-in), and manage many client sites from one account. Who it’s for Content creators and marketers: automate drafting, summarizing, SEO optimization, and image sourcing. Agencies and freelancers: deploy AI automations and chatbots across many client sites, billed centrally. Store owners: generate product descriptions, route form leads through AI, and post results automatically. Developers: trigger workflows by webhook, call external APIs, parse JSON/XML/CSV/HTML, and expose workflows to AI agents via Abilities/MCP. What you can build (nodes) Triggers: manual, scheduled runs, webhooks, and form submissions from Gravity Forms, WPForms, Contact Form 7, Ninja Forms, and Elementor Forms, plus workflow-to-workflow chaining. AI Model node: generate and transform text with OpenAI, Anthropic (Claude), and OpenRouter; use your key, the site-default provider, or a connected account. Return named, typed multi-output fields that flow straight into later steps. Specialized AI nodes: sentiment analysis, summarization, information extraction, SEO optimization, and full article writing. Content and data actions: create or update posts and custom post types (including WooCommerce products and ACF fields), write to custom database tables, find images with Unsplash, generate images/media, generate PDFs from templates or HTML, send email, call external APIs, and post to webhooks. Connect an App: bring Google (Sheets, Drive, Docs, Gmail), Slack, Notion, GitHub, and more into a workflow as action steps, with a secure one-click account connection. Research and web: deep web research and Firecrawl-powered scraping/crawling pipelines. Knowledge Base (RAG): give your AI a private knowledge base from pasted text, your WordPress content, or uploaded PDF/DOCX/TXT documents. Chatbots: build an AI chat widget trained on your own data and deploy it anywhere with a shortcode. Logic and control: conditions and branching, a Loop node, parsers (JSON/XML/CSV/HTML), and a Human Input node for approvals and human-in-the-loop review. MCP client: connect your workflows to external MCP tools and servers. Use cases Content automation: turn a topic or brief into a drafted, SEO-optimized post, ready for review. AI chatbots: answer visitor questions 24/7 with a chatbot trained on your content, deployed via shortcode. Form to AI to action: take a form submission, process it with AI, and email, post, or store the result automatically. Research and scraping pipelines: crawl sources with Firecrawl, research a subject, then summarize and extract structured data. Human-approval flows: pause a workflow for a human to review, edit, or approve AI output before it goes live. Agentic tasks (WP 7.0): let an AI assistant call your workflows as Abilities/MCP tools, with spend limits you control. Free vs. Cloud, your choice, per workflow Local (free, BYOK). Builder, core nodes, triggers, chat widget, and local execution are free forever. AI calls go directly from your site to the provider you configured, using your key. Your key never leaves your WordPress install. No account required. Cloud. Connect a free account to run workflows on our engine with our keys: no key management, no PHP timeouts, server-side scheduling, and premium nodes. External services This plugin can connect to external services. In the free, local (BYOK) configuration it never contacts our platform. Each connection below happens only in the situation described. 1. AI Workflow Automation platform (accounts and cloud execution) Our hosted account, AI proxy, and workflow execution service. It is contacted only after you create or connect an account, and never in local/BYOK mode. Service domain: https://api.wpaiworkflowautomation.com What is sent, and when: When you create or connect an account: your email and password, or a Google sign-in token, so we can authenticate you, plus your site URL so the site can be registered and issued a site key. When an AI node runs in keyless mode: the prompt or messages, the model name, and the generation parameters for that request, so the call can run on our provider keys and return the result. Your own provider keys are never included. When a workflow runs in Cloud mode: the workflow definition and the trigger or input data for that run, so our engine can execute it and return the result. A finished run may perform a small, allow-listed WordPress action back on your site through a signed callback. While the site stays connected: your plan status and remaining allowance are fetched periodically so the plugin can display them. If you redeem a legacy license: the license key. Terms and conditions: https://wpaiworkflowautomation.com/terms-and-conditions/ Privacy policy: https://wpaiworkflowautomation.com/privacy-policy/ 2. Your AI provider (OpenAI, Anthropic, OpenRouter, or another provider you configure) Contacted when an AI node runs in local/BYOK mode, or when you use the WordPress site-default provider. What is sent, and when: the prompt or messages and the generation parameters for that request, sent directly from your server to the provider you configured, using your own key, at the moment the node runs. Nothing passes through us. Review the terms and privacy policy of the provider you choose, for example https://openai.com/policies , https://www.anthropic.com/legal/privacy , or https://openrouter.ai/privacy . 3. Template library (wpaiworkflowautomation.com) Contacted only when you open the Templates screen or import a template. Service domain: https://wpaiworkflowautomation.com What is sent, and when: a request for the template list or for one template by slug, at the moment you browse or import. If a legacy license key is still stored on the site, it is included so entitled templates can be returned. No workflow or site content is sent. 4. Paddle (payment processing) Our merchant of record, contacted only if you choose to buy a paid plan or a top-up. What is sent, and when: the plugin asks our platform for a checkout session and opens Paddle’s hosted checkout page; the billing details you enter there go to Paddle. The plugin never loads Paddle scripts on your site and never handles or stores card data. Terms: https://www.paddle.com/legal/terms Privacy policy: https://www.paddle.com/legal/privacy 5. Usage analytics (opt-in, off by default) Optional and disabled by default. Nothing is sent unless you explicitly switch on “Usage Analytics” in the plugin settings, and you can switch it off again at any time. Service domain: https://api.wpaiworkflowautomation.com What is sent, and when: only after you opt in: an anonymous installation ID, your site URL and a hash of it, the plugin, WordPress, and PHP versions, the AI models selected in settings, and aggregate counts (how many workflows exist, how many are active, and how many executions ran and succeeded in the last 30 days). It is sent when the plugin is activated or deactivated and roughly once a day while enabled. No personal data, API keys, prompts, workflow content, or execution content is sent. Terms and conditions: https://wpaiworkflowautomation.com/terms-and-conditions/ Privacy policy: https://wpaiworkflowautomation.com/privacy-policy/

wp-admin forgets. OpenStation doesn’t. You know the moment. You’re deep in a post and you need one image from the Media Library. You click over, find it, click back, and everything you had going is gone. Your scroll position, your half-typed thought, the three other things you had queued up in your head. That’s not a bug you hit. That’s the design. wp-admin shows you one screen at a time, and every navigation throws the last one away. It has worked this way since 2003, like a fridge that empties itself every time you close the door. WordPress has rebuilt almost everything else. The editor, the site editor, the patterns, the styles. The admin’s one-screen-at-a-time model is the layer nobody touched. OpenStation touches it. Install it and admin screens become draggable, resizable windows. Edit a post while the Media Library sits open next to it. Drag an image from one window straight into the other. Keep comments open in the corner. Reload the browser and your window layout — open pages, positions, sizes, and window states — comes back where you left it. OpenStation itself is free, GPL, and opt-in per user. One click in the admin bar turns it on for you. One click turns it off. Nobody else on your site sees anything change, and deactivating the plugin restores the classic admin exactly. No Core patches and no lock-in. Optional AI providers may charge for their service. Built and maintained by Automattic, the company behind WordPress.com, Jetpack, WooCommerce, and Tumblr. Work on more than one thing at once Admin pages open as windows, including pages added by most other plugins. Drag them, resize them, snap them, tile them, minimize them to a taskbar. The admin menu becomes a dock of icons. Two editors open at once is one click away. Never lose your place Moving between open windows leaves each page in place. Across reloads, OpenStation remembers your open pages, window positions, sizes and states, virtual desktops, and focus. Closing a window with unsaved changes warns you first. A desk you can actually put things on Drop posts, media, and links right onto the wallpaper. Sort them into folders. Trash them to a Trash that actually holds things. The stuff you’re working on this week can just sit out where you can see it. One desktop per job Virtual desktops, the way your operating system does them. One for writing. One for the store. One for comment triage. One for that redesign you keep poking at. Switch between them without closing anything. Find anything with Cmd+K The full WordPress command palette, plus slash commands from your plugins, all under one keystroke. Turn on the optional AI assistant and you can ask it things like “which post had the comment asking for the recipe?” and it searches your own content to answer. (Requires an AI provider configured in Settings → Connectors on WordPress 7.0+. Details under “External services” below.) See how your site fits together The Corkboard is an interactive, zoomable map of how your posts, pages, and products link to each other. Pan around it. Find the orphans. Find the hubs. Running a store? Orders, Products, Coupons, and Customers become browsable folders with stock and sale ribbons. Open a customer to see their lifetime spend and what they buy most. Follow a product to its buyers, or a coupon to who redeemed it. Make it yours Wallpapers, from color presets to animated scenes to your own photo. Live widgets pinned to the desktop: drafts, stats, recent comments, a focus timer. Uploadable desktop themes, including a built-in Legacy theme that brings the old WordPress blue back in one click. And Mio, a soft-body desk companion that drifts across your wallpaper and gets bumped around by your windows. Off by default. You’ll turn it on. For developers Extend OpenStation through documented PHP and JavaScript APIs. Register windows, icons, wallpapers, widgets, commands, and settings tabs through stable openstation_register_* PHP APIs and a typed JavaScript API; customize dock items through documented hooks; add AI tools with the WordPress Abilities API. Copy-paste examples live in the developer docs on GitHub. External services No external service is required for OpenStation’s desktop interface. The optional AI Assistant and two user-initiated enrichment features make the external requests described below. AI Assistant The optional AI Assistant sends data to the AI provider you configure in WordPress’s Settings → Connectors (for example OpenAI, Anthropic, or Google). Generation is routed through WordPress 7.0’s built-in AI Client, which supplies the credentials stored in Connectors. The plugin never handles an API key itself. With no provider configured in Connectors, no external AI requests are made. When the AI Assistant is enabled and a user invokes it (via Cmd+K or the slash-command palette): What is sent: the user’s prompt, the conversation history for the active session, and tool-call metadata. The plugin’s built-in tools (search_posts, search_pages, search_comments) run WordPress’s native keyword search and may include excerpts of the matching posts/pages/comments in tool results, which are then sent back to the provider as part of the agentic loop. When it is sent: on user-initiated AI requests, and (if an administrator enables “Score new comments with AI”) on comment-save hooks for spam analysis. Posts, pages, and taxonomy terms are not sent automatically. Why it is sent: to obtain model completions and tool-call decisions that drive the AI Assistant. Who provides the service: whichever provider you configured in Settings → Connectors. Which provider (and endpoint) receives the data depends entirely on that configuration. Review the chosen provider’s own terms and privacy policy (e.g. OpenAI, Anthropic, or Google). URL shortcut favicons When an authorized user creates a desktop shortcut to an external URL, OpenStation asks that URL for its page HTML and favicon so the shortcut can display the site’s icon. The request is made from your WordPress server and sends the requested URL, the server’s IP address, an OpenStation user-agent string, and normal HTTP request metadata to the operator of that site. This happens only when a user creates the shortcut. The destination site’s terms and privacy policy apply. WordPress.org plugin information When an authorized user opens or refreshes parts of OpenStation’s Plugins window, OpenStation may request public plugin details, update metadata, and review excerpts from WordPress.org. These requests send plugin slugs, the site’s locale, and normal HTTP request metadata to WordPress.org. This information is used only to display and manage plugins. Review the WordPress.org Privacy Policy. OpenStation’s OAuth relay does not contact a service by itself. Third-party plugins that configure the relay may contact their own providers and are responsible for disclosing those services. Credits OpenStation is brought to you by Automattic. The plugin is open source under GPLv2-or-later; contributions are welcome on GitHub. Third-party libraries The plugin bundles the following third-party JavaScript library, loaded on demand only when a feature that needs it is in use: PixiJS (MIT License) — used by the Corkboard window, built-in canvas wallpapers (e.g. the animated WordPress logo), the Mio desk companion, and the Inkfall typing game. PixiJS is loaded from the plugin’s own assets/vendor/ directory; no CDN requests are made. Data files The Inkfall game’s word list (assets/games/inkfall/words.txt) is generated from the following sources (attribution also ships in the file’s header): FrequencyWords by Hermit Dave (CC-BY-SA 4.0) — English word-frequency ranking derived from the OpenSubtitles corpus. english-words by dwyl (Unlicense) — used as a validity filter. LDNOOBW English list (CC-BY 4.0) — used as an exclusion filter.