內容簡介
Zaplane 是一款無需編碼的 WordPress 自動化外掛及工作流程建構工具，能在您的 WordPress 網站內部運行。使用者可以將觸發事件（如 WooCommerce 訂單、表單提交等）與多個動作（如發送電子郵件、添加聯絡人等）連結，並在背景中可靠執行。
【主要功能】
• 無需編碼的視覺化工作流程建構器
• 自我託管，無每次任務費用
• 超過 100 種整合選項
• 流程控制步驟：延遲、條件、過濾器
• 可靠的背景處理
• 可選的 AI 自動化功能
外掛標籤
開發者團隊
② 後台搜尋「Zaplane – AI Agent Automation & Workflow Builder」→ 直接安裝（推薦）
原文外掛簡介
Zaplane is a no-code WordPress automation plugin and workflow builder that runs entirely inside your WordPress site. Connect a trigger (a WooCommerce order placed, a form submitted, a user registered, a subscription renewed, a webhook received) to one or more actions (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.
Build automation workflows visually on a drag-and-drop canvas — no code required — and let them run reliably in the background on Action Scheduler, the same queue WooCommerce uses.
Why Zaplane?
No-code visual workflow builder — design automations by connecting trigger and action nodes on a flow canvas.
Self-hosted — no per-task fees — workflows, run history and credentials stay in your own WordPress database. No external automation service to pay per task or per workflow. Data reaches a third-party only when a workflow or connection you set up uses it (see External services).
100+ integrations — WooCommerce, Easy Digital Downloads, FluentCRM, Mailchimp, Slack, Discord, Telegram, WhatsApp, Gmail, Google Sheets, Zoom, LearnDash, Tutor LMS, Elementor, Fluent Forms, Gravity Forms, WPForms, Contact Form 7 and many more (full list below).
Flow control steps — Delay, Condition, Filter, Router (multi-branch), Iterator (loop), Set Variable, HTTP Request, Send/Catch Webhook, Human Approval, Schedule, Manual trigger, Sticky Note.
Reliable background processing — long-running and scheduled steps run on Action Scheduler.
Ready-made recipes — templates for abandoned carts, birthday messages, win-backs, upsells, review requests, order confirmations, lead nurturing and more.
Optional AI automation — write replies, run a tool-calling AI Agent, generate images, or search your own knowledge base, through the WordPress AI Client (when available in core) or your own OpenAI, Anthropic or Gemini key.
AI access through the WordPress Abilities API — Zaplane registers its workflow capabilities as abilities. Install an MCP adapter and an AI client you approve can discover, build and run workflows. Zaplane runs no server of its own, and every ability requires an administrator.
Build your own integrations — Custom Apps let you add any REST API or WordPress hook as a trigger or action without writing a plugin.
GPL-3.0, 100% free, no premium upsell — every integration, trigger, action and recipe is in this plugin.
What you can automate
WooCommerce automation — welcome new customers, recover abandoned carts, follow up on orders, tag high-value buyers in your CRM, notify Slack when a product goes out of stock, send a review request after delivery, trigger subscription renewal reminders.
CRM & marketing automation — add form submissions to FluentCRM / Mailchimp / Brevo / ActiveCampaign / Groundhogg / GemCRM, apply or remove tags, enrol contacts in sequences, sync between CRMs, send birthday emails.
Form automation — route Fluent Forms, Gravity Forms, WPForms, Contact Form 7, Formidable, Ninja Forms, Fillout, Typeform or Jotform submissions to any destination; create tickets, cards, deals, posts, users or orders from a form.
LMS automation — enrol learners on LearnDash, Tutor LMS, LifterLMS, MasterStudy or Academy courses, grant membership on purchase, email instructors on course completion, award points, print certificates.
Membership automation — provision access on MemberPress, Paid Memberships Pro, SureMembers, BuddyBoss or Ultimate Member when a payment succeeds; downgrade on cancellation; sync membership status to a CRM.
Messaging automation — post to Slack, Discord, Telegram or Microsoft Teams-style channels, send Gmail / SureMail replies, auto-reply on WhatsApp or Facebook Messenger, create Zoom or Google Meet meetings.
Content & publishing automation — publish posts across sites, update ACF / Meta Box / JetEngine fields, add Events Calendar events, generate PDFs, send Google Docs / Google Sheets.
AI automation — route a form submission through an AI Agent, summarise support emails, auto-reply to webhooks with your knowledge base, translate content, extract structured data.
Scheduled & recurring automation — hourly, daily, weekly or cron-based jobs; birthdays and anniversaries; polling triggers for Google Sheets / Google Docs; delayed follow-ups.
Flow-control & utility steps
Delay (minutes, hours, days or until a date) · Condition (if/else) · Filter (stop if criteria don’t match) · Router (branch into many paths) · Iterator / Repeater (loop over a list) · Set Variable · Schedule · Manual trigger · Human Approval (pause for a Slack approval) · HTTP Request · Catch Webhook · Send Webhook · Formatter · Date / Time · CSV · XML · JSON Parser · Image Helper · Conversation Memory · Business Knowledge · MCP Client · Sticky Note.
Full integrations list
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.
Each service needs your own account with that provider. See External services below for exactly what Zaplane sends to each one, and when.
External services
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.
The AI entries (Anthropic, Google Gemini, OpenAI, OpenAI-compatible, WordPress AI Client) apply only when a connection uses that provider.
ActiveCampaign
Sends: contact emails, names and phone numbers, and list / tag / automation IDs — to your account’s API URL (e.g. *.api-us1.com) with your key, when you test the connection or an ActiveCampaign step runs.
Terms: https://www.activecampaign.com/legal/terms-of-service · Privacy: https://www.activecampaign.com/legal/privacy-policy
Anthropic
Sends: instructions, messages, conversation history, knowledge context, tool definitions and results, and image URLs — to api.anthropic.com with your key, when you test the connection or an AI / AI Agent step runs.
Terms: https://www.anthropic.com/legal/commercial-terms · Privacy: https://www.anthropic.com/legal/privacy
Brevo
Sends: contact emails, names, attributes and list IDs — to api.brevo.com with your key, when you test the connection or a Brevo step runs.
Terms: https://www.brevo.com/legal/termsofuse/ · Privacy: https://www.brevo.com/legal/privacypolicy/
Discord
Sends: server, channel and user IDs and the message content you configure — to Discord’s API with your bot token, when you test the connection, when the editor loads channels, or when a Discord step runs.
Terms: https://discord.com/terms · Privacy: https://discord.com/privacy
Fillout
Sends: form IDs — to api.fillout.com with your key, when you test the connection or the editor loads forms.
Terms: https://www.fillout.com/terms · Privacy: https://www.fillout.com/privacy
Google Gemini
Sends: prompts, conversation history, knowledge context and images; for semantic search, knowledge titles / content and queries — to generativelanguage.googleapis.com with your key, when an AI step runs or (with semantic search on) knowledge is embedded or searched.
Terms: https://ai.google.dev/gemini-api/terms · Privacy: https://policies.google.com/privacy
Google (Gmail, Calendar, Meet)
Sends: recipients, subjects and bodies; event titles, times, descriptions and attendee emails; OAuth codes and tokens — to Google’s APIs (gmail.googleapis.com, www.googleapis.com, meet.googleapis.com, with sign-in at accounts.google.com / oauth2.googleapis.com) using the OAuth client you configure, when you connect, when the editor loads labels or calendars, or when a Gmail / Google Meet step runs.
Terms: https://policies.google.com/terms (and https://developers.google.com/terms) · Privacy: https://policies.google.com/privacy
Jotform
Sends: form IDs and the form definitions you create — to api.jotform.com with your key, when you test the connection, when the editor loads forms, or when a Jotform step runs.
Terms: https://www.jotform.com/terms/ · Privacy: https://www.jotform.com/privacy/
Mailchimp
Sends: subscriber emails, merge fields, tags and audience IDs — to the api.mailchimp.com data centre named in your key, when you test the connection or a Mailchimp step runs.
Terms: https://mailchimp.com/legal/terms/ · Privacy: https://www.intuit.com/privacy/statement/
Meta (Messenger, WhatsApp)
Sends: recipient ID or phone number, message text, templates, media URLs and locations — to the Meta Graph API (graph.facebook.com) with your page or WhatsApp Business token, when you test the connection or a Messenger / WhatsApp step runs.
Terms: https://developers.facebook.com/terms/ and https://www.whatsapp.com/legal/business-terms · Privacy: https://www.facebook.com/privacy/policy/
OpenAI
Sends: instructions, messages, conversation history, knowledge context, tool definitions and results, image URLs and prompts, audio files you point to; for semantic search, knowledge text and queries — to api.openai.com with your key, when you test the connection, when an AI step runs, or (with semantic search on) when knowledge is embedded or searched.
Terms: https://openai.com/policies/services-agreement/ · Privacy: https://openai.com/policies/privacy-policy/
OpenAI-compatible providers
Sends: the same data as the OpenAI entry — to the base URL you enter (e.g. OpenRouter at openrouter.ai, 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.
Terms and privacy: those of the provider you choose. OpenRouter: https://openrouter.ai/terms · https://openrouter.ai/privacy. Azure OpenAI: https://www.microsoft.com/licensing/terms/ · https://www.microsoft.com/privacy/privacystatement
Slack
Sends: the channels, users, message text and names you configure; your OAuth code or bot token; for Human Approval, the message and its approve / reject links to the incoming webhook URL you enter — to Slack’s API, when you connect or test a connection, when the editor loads channels, or when a Slack / Human Approval step runs.
Terms: https://slack.com/terms-of-service/api · Privacy: https://slack.com/trust/privacy/privacy-policy
Telegram
Sends: chat ID, message text and media URLs — to api.telegram.org with your bot token, when you test the connection or a Telegram step runs.
Terms: https://telegram.org/tos/bot-developers · Privacy: https://telegram.org/privacy
Trello
Sends: the card, list, board, member and label details you configure, with your key and token — to api.trello.com, when you test the connection, when the editor loads boards and lists, or when a Trello step runs.
Terms: https://www.atlassian.com/legal/atlassian-customer-agreement · Privacy: https://www.atlassian.com/legal/privacy-policy
Typeform
Sends: form titles, fields and workspace, and your site’s webhook URL (the Create Form step registers it so responses reach your workflows) — to api.typeform.com with your access token, when you test the connection, when the editor loads forms, or when a Typeform step runs.
Terms: https://www.typeform.com/legal/service-terms-and-conditions · Privacy: https://www.typeform.com/legal/privacy-policy
WordPress AI Client
Sends: prompt, conversation history, knowledge context, tool definitions and results, and any image you reference — to WordPress core’s AI Client, which forwards them to the provider the site owner configured. Zaplane stores no key for it and contacts no AI service itself.
Terms and privacy: those of the provider configured in WordPress (see the Anthropic / Google Gemini / OpenAI entries above).
YouTube thumbnails (email editor)
Sends: the video ID, as part of the image address — to img.youtube.com, when you add a YouTube link to a Video block on the Email Templates screen.
Terms: https://www.youtube.com/t/terms · Privacy: https://policies.google.com/privacy
Zoom
Sends: meeting topics, times and settings; registrant names and emails; OAuth codes and tokens — to api.zoom.us (sign-in at zoom.us) through your Zoom app, when you connect or a Zoom step runs.
Terms: https://www.zoom.com/en/trust/terms/ · Privacy: https://www.zoom.com/en/trust/privacy/privacy-statement/
Addresses you configure
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.
Source Code and Build Process
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 includes/ and integrations/, 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.
Where the development files are
dev_zaplane/ — the React source: app.js is the entry point, app.scss its base stylesheet, with components/ (shared UI), containers/BackendDashboard/ (the admin screens and workflow canvas), redux/ (store and slices), hooks/, utils/ and webpack/ (a loader that points the email editor’s placeholder images at assets/images/).
assets/scss/ — the Sass for the admin interface; backend.scss is its entry.
package.json, webpack.config.js, tailwind.config.js, postcss.config.js and jsconfig.json — the dependencies, build scripts and configuration. The build runs on @wordpress/scripts, with Tailwind CSS and Autoprefixer through PostCSS.
Generated files
assets/build/app.js — built from dev_zaplane/app.js and every module it imports.
assets/build/app.css and assets/build/app-rtl.css — built from the Sass above; the right-to-left file comes from the same source.
assets/build/app.asset.php — written by the build: the script’s WordPress dependencies and its version.
Every generated .js and .css file starts with a comment naming its source and the commands that rebuild it.
Building the admin interface
You need Node.js 18.12 or newer and npm 8.19 or newer. In the plugin’s folder, wp-content/plugins/zaplane:
Install the dependencies: npm install --legacy-peer-deps
Build the production files: npm run build
The build writes minified files to assets/build/. While working on the source, npm run start rebuilds on every save, unminified and with source maps; run npm run build again before using the plugin on a live site. --legacy-peer-deps is needed because one dependency, react-json-view, declares support only for older React versions, although it works with the version Zaplane uses.
The PHP library in vendor/ (Action Scheduler) is managed with Composer; composer install --no-dev reinstalls it.
