Description

Zaplane is a no-code WordPress automation plugin and workflow builder — a self-hosted Zapier alternative 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

eCommerce: WooCommerce, WooCommerce Bookings, Easy Digital Downloads, SureCart, FluentCart, StoreEngine, Dokan.

Funnels & subscriptions: FunnelKit, WPFunnels, Paymattic.

CRM & marketing: FluentCRM, Groundhogg, GemCRM, Mailchimp, Brevo, ActiveCampaign.

Forms: Fluent Forms, Gravity Forms, WPForms, Contact Form 7, Formidable Forms, Ninja Forms, SureForms, Metform, weForms, WP User Frontend, Bit Form, Avada Form, AR Form, Booking Calendar Contact Form, Fillout, Typeform, Jotform.

LMS: LearnDash, Tutor LMS, LifterLMS, MasterStudy LMS, Academy LMS, QuizPress.

Membership & community: MemberPress, Paid Memberships Pro, SureMembers, BuddyBoss, Ultimate Member, Profile Builder, ZenCommunity.

Messaging & calling: Slack, Discord, Telegram, WhatsApp, Facebook Messenger, Zoom, Google Meet.

Email: Gmail, SureMail, FluentSMTP.

Google workspace: Google Sheets, Google Docs, Google Meet, Gmail.

Page builders & blocks: Elementor, Divi Builder, Beaver Builder, Kadence Blocks, Essential Blocks, Spectra, aBlocks, CoBlocks.

Content, custom fields & events: Advanced Custom Fields (ACF), JetEngine, Meta Box, The Events Calendar.

Gamification: GameEngine, GamiPress.

Project & productivity: Trello.

Mapping & media: WP Map Block, TruePlayer.

App builder & boards: ZenAppBuilder, GemBoards, GemBooking.

Developer: Webhook (incoming + outgoing), HTTP Request, Custom Apps (bring your own REST API or WordPress hook), MCP Client, Business Knowledge, WordPress core (any post type, taxonomy, user, option, role, custom hook).

AI: AI (Chat Model), AI Agent (tool-calling), OpenAI, Anthropic (Claude), Google Gemini, OpenAI-compatible endpoints (OpenRouter, Azure OpenAI, Ollama, self-hosted), WordPress AI Client.

Each service needs your own account with that provider. See External services below for exactly what Zaplane sends to each one, and when.

Keywords this plugin covers

WordPress automation, workflow builder, no-code automation, Zapier alternative, Make.com alternative, n8n alternative, Pabbly Connect alternative, Integromat alternative, WooCommerce automation, CRM automation, email automation, marketing automation, form automation, abandoned cart automation, drip campaign, autoresponder, webhook, HTTP request, API connector, trigger action, scheduled job, cron, Action Scheduler, AI automation, AI agent, MCP, Model Context Protocol, Abilities API, LearnDash automation, FluentCRM automation, Slack notifications, Mailchimp sync, Gmail sender.

External services

Zaplane contacts no external service when you install, activate or browse it, and it sends nothing to its authors. It connects to a third-party service only after you add a connection for that service, and then only when you test the connection, when the workflow builder loads options from it (for example your Slack channels or Trello boards), or when a workflow step that uses it runs. Each service needs your own account with its provider, so please review their terms and privacy policies before connecting. Like every request WordPress makes, these carry your site’s address in the User-Agent header.

Slack

Used for: the Slack app (send messages, manage channels, add reactions, receive Slack events) and the Human Approval step’s optional Slack notification.
Sends: the channels, users, message text and names you configure; the OAuth code or bot token you connect with; for Human Approval, the message and its approve and reject links, to the incoming webhook URL you enter.
When: when you connect or test a Slack connection, when the builder loads your channels, and when a Slack or Human Approval step runs.
Terms of service: https://slack.com/terms-of-service/api
Privacy policy: https://slack.com/trust/privacy/privacy-policy

Discord

Used for: the Discord app (send messages, create invites, add reactions) through a bot token you provide.
Sends: server, channel and user IDs and the message content you configure.
When: when you test the connection, when the builder loads channels, and when a Discord step runs.
Terms of service: https://discord.com/terms
Privacy policy: https://discord.com/privacy

Used for: the Telegram app (send messages, media, locations and polls) through a bot token you provide (api.telegram.org).
Sends: the chat ID, message text and media URLs you configure.
When: when you test the connection and when a Telegram step runs.
Terms of service: https://telegram.org/tos/bot-developers
Privacy policy: https://telegram.org/privacy

Meta (Messenger and WhatsApp)

Used for: the Messenger and WhatsApp apps, through the Meta Graph API (graph.facebook.com) with the page or WhatsApp Business token you provide.
Sends: the recipient ID or phone number, message text, templates, media URLs and locations you configure.
When: when you test the connection and when a Messenger or WhatsApp step runs.
Terms of service: https://developers.facebook.com/terms/ and https://www.whatsapp.com/legal/business-terms
Privacy policy: https://www.facebook.com/privacy/policy/

Google (Gmail, Google Calendar and Google Meet)

Used for: the Gmail app (send email, load labels) and the Google Meet app (create calendar events with Meet links and meeting spaces), through Google’s APIs (gmail.googleapis.com, www.googleapis.com, meet.googleapis.com) after you authorize your own Google Cloud OAuth client (accounts.google.com, oauth2.googleapis.com).
Sends: recipients, subjects and message bodies; event titles, times, descriptions and attendee emails; OAuth codes and tokens.
When: when you connect, when the builder loads labels or calendars, and when a Gmail or Google Meet step runs.
Terms of service: https://policies.google.com/terms and https://developers.google.com/terms
Privacy policy: https://policies.google.com/privacy (see also https://developers.google.com/terms/api-services-user-data-policy)

AI provider configured in WordPress

Used for: AI and AI Agent steps, and Generate Image, when their connection uses the WordPress AI provider (the default).
Sends: Zaplane hands the prompt, conversation history, knowledge context, tool definitions and results, and any image you reference to the AI Client in WordPress core, which sends them to the provider the site owner configured in WordPress. Zaplane stores no key for it and contacts no AI service itself.
When: when one of those steps runs.
Terms of service and privacy policy: those of the provider configured in WordPress, for example the Anthropic, OpenAI or Google Gemini terms listed below.

The Anthropic, OpenAI, Google Gemini and OpenAI-compatible entries below apply only when you choose that provider on a connection and enter your own key.

Google Gemini API

Used for: AI steps with the Gemini provider and, if you turn it on, Business Knowledge semantic search, using your Gemini API key (generativelanguage.googleapis.com).
Sends: prompts, conversation history, knowledge context and images you reference; for semantic search, knowledge entry titles and content and search queries.
When: when an AI step runs, and with semantic search on, when knowledge entries are embedded or searched.
Terms of service: https://ai.google.dev/gemini-api/terms
Privacy policy: https://policies.google.com/privacy

Anthropic

Used for: AI and AI Agent steps with the Anthropic provider, using your API key (api.anthropic.com).
Sends: instructions, messages, conversation history, knowledge context, tool definitions and results, and image URLs you reference.
When: when you test the connection (which lists models) and when an AI or AI Agent step runs.
Terms of service: https://www.anthropic.com/legal/commercial-terms
Privacy policy: https://www.anthropic.com/legal/privacy

OpenAI

Used for: AI and AI Agent steps with the OpenAI provider (chat, image generation, audio transcription) and, if you turn it on, Business Knowledge semantic search, using your API key (api.openai.com).
Sends: the same kinds of data as for Anthropic, plus image prompts, the audio files you point to for transcription, and knowledge entry text and search queries for semantic search.
When: when you test the connection, when an AI step runs, and with semantic search on, when knowledge entries are embedded or searched.
Terms of service: https://openai.com/policies/services-agreement/
Privacy policy: https://openai.com/policies/privacy-policy/

OpenAI-compatible providers

Used for: AI and AI Agent steps when you choose the OpenAI-compatible provider and enter a base URL (for example Azure OpenAI, OpenRouter at openrouter.ai, or a model you host yourself with Ollama, which stays on your own server).
Sends: the same data as the OpenAI provider, to the base URL you entered.
When: when you test the connection, when the builder loads the models the endpoint lists, and when an AI or AI Agent step runs.
Terms of service and privacy policy: those of the provider you choose. For OpenRouter: https://openrouter.ai/terms and https://openrouter.ai/privacy. For Azure OpenAI: https://www.microsoft.com/licensing/terms/ and https://www.microsoft.com/privacy/privacystatement

Zoom

Used for: the Zoom app (create meetings and webinars, add registrants) through your own Zoom app (api.zoom.us, with OAuth at zoom.us).
Sends: meeting topics, times and settings; registrant names and emails; OAuth codes and tokens.
When: when you connect and when a Zoom step runs.
Terms of service: https://www.zoom.com/en/trust/terms/
Privacy policy: https://www.zoom.com/en/trust/privacy/privacy-statement/

Trello

Used for: the Trello app (create and update cards, lists and boards) with your API key and token (api.trello.com).
Sends: the card, list, board, member and label details you configure, with your key and token.
When: when you test the connection, when the builder loads boards and lists, and when a Trello step runs.
Terms of service: https://www.atlassian.com/legal/atlassian-customer-agreement
Privacy policy: https://www.atlassian.com/legal/privacy-policy

Mailchimp

Used for: the Mailchimp app (add or update subscribers and tags) with your API key (the api.mailchimp.com data centre named in your key).
Sends: subscriber email addresses, merge fields, tags and audience IDs.
When: when you test the connection and when a Mailchimp step runs.
Terms of service: https://mailchimp.com/legal/terms/
Privacy policy: https://www.intuit.com/privacy/statement/

Brevo

Used for: the Brevo app (create and update contacts, manage lists) with your API key (api.brevo.com).
Sends: contact email addresses, names, attributes and list IDs.
When: when you test the connection and when a Brevo step runs.
Terms of service: https://www.brevo.com/legal/termsofuse/
Privacy policy: https://www.brevo.com/legal/privacypolicy/

ActiveCampaign

Used for: the ActiveCampaign app (contacts, lists, tags, automations) at the account API URL and key you enter (your account’s own address, such as youraccount.api-us1.com or youraccount.activehosted.com).
Sends: contact email addresses, names and phone numbers, and list, tag and automation IDs.
When: when you test the connection and when an ActiveCampaign step runs.
Terms of service: https://www.activecampaign.com/legal/terms-of-service
Privacy policy: https://www.activecampaign.com/legal/privacy-policy

Typeform

Used for: the Typeform app (list and create forms) with your access token (api.typeform.com). After the Create Form step runs, it registers your site’s webhook URL with that form so its responses reach your workflows.
Sends: form titles, fields and workspace, and your site’s webhook URL.
When: when you test the connection, when the builder loads forms, and when a Typeform step runs.
Terms of service: https://www.typeform.com/legal/service-terms-and-conditions
Privacy policy: https://www.typeform.com/legal/privacy-policy

Jotform

Used for: the Jotform app (list and create forms) with your API key (api.jotform.com).
Sends: form IDs and the form definitions you create.
When: when you test the connection, when the builder loads forms, and when a Jotform step runs.
Terms of service: https://www.jotform.com/terms/
Privacy …

Installation

Upload the zaplane folder to the /wp-content/plugins/ directory, or install the plugin through the Plugins > Add New screen in WordPress.
Activate the plugin through the Plugins screen.
Open the Zaplane menu in your WordPress admin.
Create a new automation, pick a trigger, add your actions, and turn it on.

Requirements

WordPress 6.8 or higher
PHP 7.4 or higher

FAQ

Do I need a Zaplane account or any external service to use this?: 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.
Does Zaplane require WooCommerce?: 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.
How are scheduled and background steps processed?: Zaplane uses Action Scheduler (the same background-processing library used by WooCommerce) to run delays, scheduled steps and long-running workflows reliably.
Where does my data go?: 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.
Can workflows reach private or internal addresses?: 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_http_allowed_private_hosts filter.
What can an AI client connected through the Abilities API do?: 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.
Can a Custom App call PHP functions?: Only functions that code on your site has allowed with the zaplane_custom_app_callables filter. A Custom App can also fire a WordPress action or filter hook of your choosing.
Can I build multi-step workflows with conditions and delays?: Yes. You can chain multiple actions and insert delay, condition, filter, iterator and variable steps to control exactly how and when each step runs.
Where is the source code for the admin interface?: In the plugin itself. dev_zaplane/ holds the React source of the admin interface and assets/scss/ its Sass; the files in assets/build/ are compiled from them. See Source Code and Build Process for where each file is and how to build it.

Reviews

There are no reviews for this plugin.

Contributors & Developers

“Zaplane – AI Agent Automation Workflow Builder & Integrations for LMS, CRM, eCommerce, Google Sheets, Forms and More” is open source software. The following people have contributed to this plugin.

Translate “Zaplane – AI Agent Automation Workflow Builder & Integrations for LMS, CRM, eCommerce, Google Sheets, Forms and More” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

1.4.0

Changed
* AI access now uses the WordPress Abilities API instead of Zaplane’s own MCP server. Zaplane registers its workflow capabilities as abilities; install an MCP adapter and an AI client you approve can discover, build and run workflows through WordPress core. Every ability requires an administrator, and site-administration actions stay out of an AI client’s reach.
* Removed the built-in MCP server, its OAuth sign-in, access tokens, and the “AI access” settings and log screens.
* Raised the minimum WordPress version to 6.8. Abilities and the core AI Client are consumed through the Abilities API when the hosting WordPress version provides them.
* The MCP Client workflow step (calling other services’ MCP servers) is unchanged.

1.3.3

Security
* A workflow that another service starts — a Catch Webhook URL, a provider webhook, or a trigger from a connected outside account — can no longer run actions that administer the site: activating or deactivating plugins, creating, changing or deleting users, changing roles and capabilities, and changing site options. Such a workflow cannot be activated, the editor explains why, and the step is refused if one runs anyway. The same actions still work in workflows started by something that happens on the site.
* An AI Agent is never given those actions as tools.
* The Academy and ZenCommunity steps no longer switch the signed-in user while they run; they act for the user they name.
* MCP access tokens now sign in through WordPress’s own authentication filter, the one application passwords use, instead of switching the user inside the endpoint.

1.3.2

Security
* An AI client connected through the MCP server can no longer reach actions that administer the site: activating or deactivating plugins, creating, changing or deleting users, changing roles and capabilities, and changing site options. It cannot add them to a workflow, or read, edit, activate, test or run a workflow that uses them.

Fixed
* Conditions, filters and a few triggers no longer call string functions that need PHP 8, so Zaplane runs on PHP 7.4 as declared.
* Workflow steps now run when Action Scheduler is processed from WP-CLI, as many hosts do from a system cron. Before, every queued step failed there.

1.3.1

Security and privacy
* Removed the Switch Theme and Authenticate User actions. Which theme a site runs, and signing in, are the site owner’s own decisions.
* Create, Update and Delete User now accept only the fields their form offers and a role the site defines, and refuse to delete the last administrator or the account the run is using.
* Incoming webhook and Catch Webhook URLs check the provider’s signature, or the trigger’s shared secret, before the request reaches the workflow.
* The workflow query builder now refuses any table, column, operator or sort direction that is not a plain name, and every value it sends is a placeholder filled in by WordPress.
* The admin palette, the integrations catalogue and the MCP consent screen are escaped on the way out.
* Documented the Telegram API address and the links to claude.ai and ChatGPT under External services.

Fixed
* Lists of courses, quizzes, ranks and achievements are read through WordPress instead of the posts table directly.
* Fixed selecting a specific set of columns — a “get this field for every row” query returned nothing.

1.3.0

Workflows
* A workflow can start from more than one trigger. Whichever fires starts the run, and {{trigger.*}} reads its data.
* Connecting steps is easier: drop a line anywhere on a step’s card, and letting go on empty canvas opens the step picker.

Recipes
* Group recipes set up several workflows at once in a new folder, starting with WooCommerce Customer Lifecycle and StoreEngine Store Emails.
* Every recipe opens a setup for its optional steps, settings and connections. Plugins can register recipes as simple arrays.

AI
* The AI, AI Agent and Generate Image steps use the WordPress AI Client when it is available in core, including the agent’s tool calling. Your own provider key is still an option.

AI access (MCP server)
* claude.ai and ChatGPT can connect through OAuth, with administrator approval. WordPress application passwords also work.
* Tool calls are logged, tokens can expire, and run tokens can be limited to chosen workflows.

Security and compatibility
* Merge tags are no longer evaluated as PHP, and outbound requests are checked on every redirect.
* MCP tokens now act as their own user and require administrator rights.
* Updates come only from WordPress.org. WordPress 6.8 or later is required.

Fixes
* GemCRM Send Email now reaches only the chosen contact or list.
* Fixed shipped recipes’ Send Email steps, duplicate recipes after a rename, fields with hyphens, forms watched by two triggers, and Logs Re-Try.

1.2.0

New integrations
* aBlocks — a Form Submitted trigger for aBlocks form-builder forms.
* FluentCart — 21 new triggers and 52 new actions across carts, coupons, licences, customers, orders, products and subscriptions.

AI access (MCP server)
* Let Claude, Cursor or any Model Context Protocol client read your automations and build new ones from a plain-language description. Off by default, behind scoped and revocable tokens.

Modules
* Optional features are now opt-in and switched off on a fresh install. Existing sites keep whatever they had.
* A card on the Workflows, Dashboard and Connections screens lists what you have not turned on, with a one-click switch. Picking a step whose module is off now says so in the builder and offers to enable it there.

Workflow canvas
* Nodes are colour-typed as trigger, action, tool or AI, on the card and on the connector leaving it, so a glance shows what feeds what.
* Node cards now sit on a canvas of their own colour instead of sharing it, connectors draw a single stroke instead of three, and the delete control is a real, keyboard-reachable button.

Appearance
* The dark theme was rebuilt for legibility — secondary text and button labels previously fell below the accessible contrast minimum.
* The dashboard chart now follows your palette instead of fixed light-mode colours.

Performance
* The admin bundle drops from 23.8 MB to 1.6 MB.

Removed
* The Dokan “Withdraw Request Pending” and FluentCart “Order Paid Done” triggers. A workflow still using either will need its trigger re-selected.

1.1.0

New integrations
* StoreEngine — order, subscription and product triggers plus actions.
* AI (Chat Model) — generate replies with Anthropic, OpenAI, or WordPress Core AI.
* AI Agent — autonomous tool-calling agent with Chat Model, Memory and Tools sub-nodes, plus MCP server support.
* Conversation Memory — durable, keyed chat history for AI conversations.
* Business Knowledge — a searchable knowledge base the AI Agent can query; sync from StoreEngine products.
* Custom Apps — build your own integrations (REST or same-site WordPress hooks) without code changes.
* Webhook — a dedicated app for both directions: Catch Webhook (incoming) and Send Webhook (outgoing) with optional HMAC-SHA256 signing.
* Messenger and WhatsApp — AI auto-reply flows.
* Academy — course enrolment triggers, actions and access-group membership.

New tools & flow control
* Manual Trigger, Schedule trigger, and Human-in-the-Loop approval.
* Router (multi-branch), Repeater/Iterator, Condition and Filter.
* Utility tools: CSV, XML, JSON Parser, Formatter, Date/Time, Image Helper, Set Variable, and Sticky Note.

New recipe
* “AI Reply to Incoming Webhook” — receive a question by webhook, answer it with the AI Agent using your Business Knowledge, then post the reply back out.

Improvements
* Dynamic-data “@” token picker across expression fields, with sample outputs so tokens are available before a test run.
* Redesigned Business Knowledge, field, checkbox and connection-icon UI, with icon fallbacks.
* Clearer node port / branch handles and AI Agent sub-node handles on the canvas.

Fixes
* AI and AI Agent no longer appear as trigger options where only actions apply.
* Custom Apps: trigger firing, label handling, and the stale generic “Custom App” entry in the app picker.
* Webhook: structured Body fields so multi-line/quoted values (e.g. an AI reply) can’t produce malformed JSON.
* Node port, multiple-output, route-indicator, CSV parser, and dynamic-data resolution fixes.

1.0.2

Improvements and bug fixes.

1.0.0

Initial release.