Zaplane now exposes its automations as abilities through the WordPress Abilities API; the previous Zaplane-operated MCP server has been removed. The Custom PHP Code step is no longer bundled. Minimum WordPress is 6.8.<\/p>","1.3.3":"
Workflows started by a webhook or an outside service can no longer run actions that administer the site.<\/p>","1.3.2":"
MCP clients can no longer use actions that administer the site, and PHP 7.4 compatibility is fixed.<\/p>","1.3.1":"
Security hardening throughout, and two actions removed: Switch Theme and Authenticate User.<\/p>","1.3.0":"
Adds multiple triggers per workflow, group recipes, WordPress AI Client support and OAuth sign-in for AI clients, and fixes security issues. Requires WordPress 6.8 or later. MCP tokens issued to users without administrator rights stop working.<\/p>","1.2.0":"
Adds aBlocks and FluentCart integrations, an optional MCP server and a rebuilt dark theme. Optional modules are off on new sites. The Dokan "Withdraw Request Pending" and FluentCart "Order Paid Done" triggers were removed; re-select the trigger in any workflow using them.<\/p>","1.1.0":"
Major feature release: StoreEngine, AI Agent (with MCP), AI Chat Model, Memory, Business Knowledge, Custom Apps, a bidirectional Webhook app, and many new tools and flow-control nodes.<\/p>","1.0.2":"
Recommended update with stability improvements and bug fixes.<\/p>"},"ratings":[],"assets_icons":{"icon-256x256.png":{"filename":"icon-256x256.png","revision":3748638,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3748638,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3748638,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.4.0","1.5.0"],"block_files":[],"assets_screenshots":[],"screenshots":{"1":"The visual workflow builder canvas.","2":"Choosing a trigger for a new automation.","3":"Configuring an action step.","4":"Browsing ready-made recipe templates.","5":"Workflow run history and logs."}},"plugin_section":[],"plugin_tags":[232494,569,597,15439,8197],"plugin_category":[],"plugin_contributors":[223170,177102],"plugin_business_model":[],"class_list":["post-369289","plugin","type-plugin","status-publish","hentry","plugin_tags-ai-agent","plugin_tags-automation","plugin_tags-integration","plugin_tags-webhook","plugin_tags-workflow","plugin_contributors-kodezen","plugin_contributors-tusharimran","plugin_committers-kodezen"],"banners":{"banner":"https:\/\/ps.w.org\/zaplane\/assets\/banner-772x250.png?rev=3748638","banner_2x":"https:\/\/ps.w.org\/zaplane\/assets\/banner-1544x500.png?rev=3748638","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/zaplane\/assets\/icon-256x256.png?rev=3748638","icon_2x":"https:\/\/ps.w.org\/zaplane\/assets\/icon-256x256.png?rev=3748638","generated":false},"screenshots":[],"raw_content":"\n
Zaplane<\/strong> is a no-code WordPress automation<\/strong> plugin and workflow builder that runs entirely inside your WordPress site. Connect a trigger<\/strong> (a WooCommerce order placed, a form submitted, a user registered, a subscription renewed, a webhook received) to one or more actions<\/strong> (send an email, add a contact to your CRM, post a Slack message, create a Trello card, call an API) with delays, conditions, filters, loops and AI steps in between.<\/p>\n\n Build automation workflows<\/strong> visually on a drag-and-drop canvas \u2014 no code required \u2014 and let them run reliably in the background on Action Scheduler, the same queue WooCommerce uses.<\/p>\n\n Delay (minutes, hours, days or until a date) \u00b7 Condition (if\/else) \u00b7 Filter (stop if criteria don't match) \u00b7 Router (branch into many paths) \u00b7 Iterator \/ Repeater (loop over a list) \u00b7 Set Variable \u00b7 Schedule \u00b7 Manual trigger \u00b7 Human Approval (pause for a Slack approval) \u00b7 HTTP Request \u00b7 Catch Webhook \u00b7 Send Webhook \u00b7 Formatter \u00b7 Date \/ Time \u00b7 CSV \u00b7 XML \u00b7 JSON Parser \u00b7 Image Helper \u00b7 Conversation Memory \u00b7 Business Knowledge \u00b7 MCP Client \u00b7 Sticky Note.<\/p>\n\n aBlocks, ActiveCampaign, Advanced Custom Fields (ACF), AI Agent (tool-calling), AI Chat Model, Anthropic (Claude), AR Form, Avada Form, Beaver Builder, Bit Form, Booking Calendar Contact Form, Brevo, BuddyBoss, Business Knowledge, Catch Webhook, Contact Form 7, CoBlocks, Custom Apps, Discord, Divi Builder, Dokan, Easy Digital Downloads, Elementor, Essential Blocks, Facebook Messenger, Fillout, FluentCart, FluentCRM, FluentSMTP, Fluent Forms, Formidable Forms, FunnelKit, GameEngine, GamiPress, GemBoards, GemBooking, GemCRM, Gmail, Google Docs, Google Gemini, Google Meet, Google Sheets, Gravity Forms, Groundhogg, HTTP Request, JetEngine, Jotform, Kadence Blocks, LearnDash, LifterLMS, Mailchimp, MasterStudy LMS, MemberPress, Meta Box, Metform, MCP Client, Ninja Forms, OpenAI, OpenAI-compatible endpoints (Azure OpenAI, Ollama, OpenRouter, self-hosted), Paid Memberships Pro, Paymattic, Profile Builder, QuizPress, Send Webhook, Slack, Spectra, StoreEngine, SureCart, SureForms, SureMail, SureMembers, Telegram, The Events Calendar, Trello, TruePlayer, Tutor LMS, Typeform, Ultimate Member, weForms, WhatsApp, WooCommerce, WooCommerce Bookings, WordPress core (post type, taxonomy, user, option, role, custom hook), WordPress AI Client, WP Map Block, WPFunnels, WPForms, WP User Frontend, ZenAppBuilder, ZenCommunity, Zoom.<\/p>\n\n Each service needs your own account with that provider. See External services<\/strong> below for exactly what Zaplane sends to each one, and when.<\/p>\n\n Zaplane contacts no external service when you install, activate or browse it, and sends nothing to its authors. It talks to a third-party only after you add a connection for it, and then only when you test that connection, when the editor loads options from it, or when a step that uses it runs. Each service needs your own account; review its terms and privacy before connecting. Requests carry your site's address in the User-Agent header.<\/p>\n\n The AI entries (Anthropic, Google Gemini, OpenAI, OpenAI-compatible, WordPress AI Client) apply only when a connection uses that provider.<\/p>\n\n HTTP Request, Send Webhook, Custom Apps, the MCP Client, the AI Agent's HTTP tool, and the steps that read a file from a URL (CSV, Image Helper, Upload Media From URL, AI image and audio) send data to, or fetch data from, the address you enter or that your workflow supplies. What is sent is what you configure in that step; the MCP Client also sends your site's address so a server can recognise calls from it. Requests go only where you point them, and addresses on private networks are refused unless a developer allows them.<\/p>\n\n Only one part of Zaplane is compiled: the admin interface, which is a React app. Everything else, including all of the plugin's PHP in Every generated You need Node.js 18.12 or newer and npm 8.19 or newer. In the plugin's folder, The build writes minified files to The PHP library in No. Zaplane needs no account with us and does not send your site's data to us. You only need an account with a third-party service (for example Slack or Mailchimp) if you build a workflow that uses that service.<\/p><\/dd>\n No. WooCommerce is optional. Zaplane works with WordPress core events and with whichever supported plugins you have installed; the available triggers and actions depend on the plugins active on your site.<\/p><\/dd>\n Zaplane uses Action Scheduler (the same background-processing library used by WooCommerce) to run delays, scheduled steps and long-running workflows reliably.<\/p><\/dd>\n Workflows, run logs and connection credentials are stored in your WordPress database. Data leaves your site only when something you set up needs it to: a workflow step that calls a service, testing a connection, a builder field that loads options from a connected account (such as your Slack channels), or an AI step. Every service, with what is sent and when, is listed under External services.<\/p><\/dd>\n Not by default. HTTP Request, Send Webhook, Custom Apps and every other step that fetches a URL refuse loopback, private, link-local and reserved addresses, including after a redirect. A developer can allow a specific internal host with the Zaplane registers its capabilities as abilities, and an MCP adapter you install exposes them to an AI client. Zaplane runs no server of its own, so authentication and transport are WordPress core's. Every ability requires an administrator, and the client can read your workflows, runs and recipes, draft and test workflows, and run them. It cannot administer your site: actions that activate or deactivate plugins, create, change or delete users, change roles or capabilities, or change site options are kept out of its reach, and it cannot create, read, edit, activate, test or run a workflow that uses one, including one you built yourself. You can still use those actions in workflows you build in the Zaplane dashboard.<\/p><\/dd>\n Only functions that code on your site has allowed with the Yes. You can chain multiple actions and insert delay, condition, filter, iterator and variable steps to control exactly how and when each step runs.<\/p><\/dd>\n In the plugin itself. Added<\/strong>\n* Inbox module: website live chat, Facebook Messenger and WhatsApp channels, selling in chat with product cards, saved replies and quick-answers, automatic answers from Business Knowledge, agent presence and business hours, email-capture gating, typing indicator and realtime delivery. New triggers and actions so workflows can read, reply to and route conversations.\n* Third-party integration API: other plugins can register their own triggers and actions with Changed<\/strong>\n* Minimum WordPress is 7.0.\n* Many editor polish passes: top-bar logo and spacing, Create Workflow modal rhythm, Add Trigger drawer, email-template editor layout.<\/p>\n\n Fixed<\/strong>\n* Why Zaplane?<\/h4>\n\n
\n
What you can automate<\/h4>\n\n
\n
Flow-control & utility steps<\/h4>\n\n
Full integrations list<\/h4>\n\n
External services<\/h3>\n\n
ActiveCampaign<\/h4>\n\n
\n
*.api-us1.com<\/code>) with your key, when you test the connection or an ActiveCampaign step runs.<\/li>\nAnthropic<\/h4>\n\n
\n
api.anthropic.com<\/code> with your key, when you test the connection or an AI \/ AI Agent step runs.<\/li>\nBrevo<\/h4>\n\n
\n
api.brevo.com<\/code> with your key, when you test the connection or a Brevo step runs.<\/li>\nDiscord<\/h4>\n\n
\n
Fillout<\/h4>\n\n
\n
api.fillout.com<\/code> with your key, when you test the connection or the editor loads forms.<\/li>\nGoogle Gemini<\/h4>\n\n
\n
generativelanguage.googleapis.com<\/code> with your key, when an AI step runs or (with semantic search on) knowledge is embedded or searched.<\/li>\nGoogle (Gmail, Calendar, Meet)<\/h4>\n\n
\n
gmail.googleapis.com<\/code>, www.googleapis.com<\/code>, meet.googleapis.com<\/code>, with sign-in at accounts.google.com<\/code> \/ oauth2.googleapis.com<\/code>) using the OAuth client you configure, when you connect, when the editor loads labels or calendars, or when a Gmail \/ Google Meet step runs.<\/li>\nJotform<\/h4>\n\n
\n
api.jotform.com<\/code> with your key, when you test the connection, when the editor loads forms, or when a Jotform step runs.<\/li>\nMailchimp<\/h4>\n\n
\n
api.mailchimp.com<\/code> data centre named in your key, when you test the connection or a Mailchimp step runs.<\/li>\nMeta (Messenger, WhatsApp)<\/h4>\n\n
\n
graph.facebook.com<\/code>) with your page or WhatsApp Business token, when you test the connection or a Messenger \/ WhatsApp step runs.<\/li>\nOpenAI<\/h4>\n\n
\n
api.openai.com<\/code> with your key, when you test the connection, when an AI step runs, or (with semantic search on) when knowledge is embedded or searched.<\/li>\nOpenAI-compatible providers<\/h4>\n\n
\n
openrouter.ai<\/code>, Azure OpenAI, or a self-hosted endpoint such as Ollama), when you test the connection, when the editor loads models, or when an AI \/ AI Agent step runs.<\/li>\nSlack<\/h4>\n\n
\n
Telegram<\/h4>\n\n
\n
api.telegram.org<\/code> with your bot token, when you test the connection or a Telegram step runs.<\/li>\nTrello<\/h4>\n\n
\n
api.trello.com<\/code>, when you test the connection, when the editor loads boards and lists, or when a Trello step runs.<\/li>\nTypeform<\/h4>\n\n
\n
api.typeform.com<\/code> with your access token, when you test the connection, when the editor loads forms, or when a Typeform step runs.<\/li>\nWordPress AI Client<\/h4>\n\n
\n
YouTube thumbnails (email editor)<\/h4>\n\n
\n
img.youtube.com<\/code>, when you add a YouTube link to a Video block on the Email Templates screen.<\/li>\nZoom<\/h4>\n\n
\n
api.zoom.us<\/code> (sign-in at zoom.us<\/code>) through your Zoom app, when you connect or a Zoom step runs.<\/li>\nAddresses you configure<\/h4>\n\n
Source Code and Build Process<\/h3>\n\n
includes\/<\/code> and integrations\/<\/code>, runs exactly as it ships. The complete, uncompiled source of the admin interface is included in this plugin, together with everything needed to build it.<\/p>\n\nWhere the development files are<\/h4>\n\n
\n
dev_zaplane\/<\/code> \u2014 the React source: app.js<\/code> is the entry point, app.scss<\/code> its base stylesheet, with components\/<\/code> (shared UI), containers\/BackendDashboard\/<\/code> (the admin screens and workflow canvas), redux\/<\/code> (store and slices), hooks\/<\/code>, utils\/<\/code> and webpack\/<\/code> (a loader that points the email editor's placeholder images at assets\/images\/<\/code>).<\/li>\nassets\/scss\/<\/code> \u2014 the Sass for the admin interface; backend.scss<\/code> is its entry.<\/li>\npackage.json<\/code>, webpack.config.js<\/code>, tailwind.config.js<\/code>, postcss.config.js<\/code> and jsconfig.json<\/code> \u2014 the dependencies, build scripts and configuration. The build runs on @wordpress\/scripts<\/code>, with Tailwind CSS and Autoprefixer through PostCSS.<\/li>\n<\/ul>\n\nGenerated files<\/h4>\n\n
\n
assets\/build\/app.js<\/code> \u2014 built from dev_zaplane\/app.js<\/code> and every module it imports.<\/li>\nassets\/build\/app.css<\/code> and assets\/build\/app-rtl.css<\/code> \u2014 built from the Sass above; the right-to-left file comes from the same source.<\/li>\nassets\/build\/app.asset.php<\/code> \u2014 written by the build: the script's WordPress dependencies and its version.<\/li>\n<\/ul>\n\n.js<\/code> and .css<\/code> file starts with a comment naming its source and the commands that rebuild it.<\/p>\n\nBuilding the admin interface<\/h4>\n\n
wp-content\/plugins\/zaplane<\/code>:<\/p>\n\n\n
npm install --legacy-peer-deps<\/code><\/li>\nnpm run build<\/code><\/li>\n<\/ol>\n\nassets\/build\/<\/code>. While working on the source, npm run start<\/code> rebuilds on every save, unminified and with source maps; run npm run build<\/code> again before using the plugin on a live site. --legacy-peer-deps<\/code> is needed because one dependency, react-json-view, declares support only for older React versions, although it works with the version Zaplane uses.<\/p>\n\nvendor\/<\/code> (Action Scheduler) is managed with Composer; composer install --no-dev<\/code> reinstalls it.<\/p>\n\n\n\n
zaplane<\/code> folder to the \/wp-content\/plugins\/<\/code> directory, or install the plugin through the Plugins > Add New<\/strong> screen in WordPress.<\/li>\nRequirements<\/h4>\n\n
\n
\n
Do I need a Zaplane account or any external service to use this?<\/h3><\/dt>\n
Does Zaplane require WooCommerce?<\/h3><\/dt>\n
How are scheduled and background steps processed?<\/h3><\/dt>\n
Where does my data go?<\/h3><\/dt>\n
Can workflows reach private or internal addresses?<\/h3><\/dt>\n
zaplane_http_allowed_private_hosts<\/code> filter.<\/p><\/dd>\nWhat can an AI client connected through the Abilities API do?<\/h3><\/dt>\n
Can a Custom App call PHP functions?<\/h3><\/dt>\n
zaplane_custom_app_callables<\/code> filter. A Custom App can also fire a WordPress action or filter hook of your choosing.<\/p><\/dd>\nCan I build multi-step workflows with conditions and delays?<\/h3><\/dt>\n
Where is the source code for the admin interface?<\/h3><\/dt>\n
dev_zaplane\/<\/code> holds the React source of the admin interface and assets\/scss\/<\/code> its Sass; the files in assets\/build\/<\/code> are compiled from them. See Source Code and Build Process for where each file is and how to build it.<\/p><\/dd>\n\n<\/dl>\n\n\n1.5.0<\/h4>\n\n
zaplane_register_integration()<\/code> on the zaplane_register_integrations<\/code> action. See docs\/integrations\/third-party\/README.md<\/code>.\n* wp zaplane make:addon <slug><\/code> scaffolds a ready-to-edit plugin with a sample third-party integration (or adds one to an existing plugin with --plugin=<folder><\/code>).\n* New built-in integrations: Shopify, Google Sheets, Google Docs, JetFormBuilder, Forminator, Everest Forms, HappyForms, Gutena Forms, Tally Form, QuizPress, Easy Content Manager, TruePlayer, WP Map Block, GemBoard, ZenAppBuilder.\n* AI Agent: Chat Model, Memory and Tool slots with a slot-aware picker and a zaplane_agent_slots<\/code> filter; a Chat Model's own connection decides the provider; Memory can read Inbox conversations.\n* Workflows list: filter by status and folder, search, \"Clear filters\" affordance; Connections list: status tabs, app filter and search.\n* Editor: tidier step connection picker opening the shared \"Add connection\" modal; missing-connection notice as a card over the canvas; workflows the editor flags when a step has no connection.\n* Settings: a gear button per module opens its settings; multi-WordPress support for the WordPress integration.<\/p>\n\n