Build with AI
An in-admin AI agent that turns plain-language requests into working, tested webhook integrations — plan-first, with confirmation before anything goes live.
Build with AI is the plugin's in-admin agent. Describe the outcome — "When a Contact Form 7 form is submitted, send it as JSON to my n8n webhook" — and the agent proposes a step-by-step plan, then executes it: creates the webhook (always disabled at first), works from a real example payload — your site's own capture where one exists, otherwise a reference payload from the Payload Library — and, when the destination is a named third-party service, from that service's current API reference in the API Docs Library, maps fields against the actual payload shape, sets dispatch conditions, probes the endpoint with an SSRF-guarded test call, and sends a real test delivery. Steps that go live or change data pause for your confirmation, and the last change can be undone with one click. On a fresh install there is nothing to connect first — a free trial covers your first builds the moment you send a prompt.
Free credits, nothing to connect
A brand-new install can build straight away. Sending your first prompt claims a free trial — 55 credits, issued to your site by our API with no key, no account and no card. That is roughly five agent turns, or two complete automations. Before you spend anything the model bar reads "Free trial — starts with your first prompt" alongside the credit count; once claimed it switches to "N credits left" and counts down as you build, and the same figures appear on the Free trial card in Settings → AI Builder. One trial per site, and it is never refilled. It is also the last source Auto reaches for, so a site that has connected WordPress connectors or its own API key keeps using those and never spends trial credits. When the trial is used up, Build with AI carries on as soon as you connect your own provider key — a free Google AI Studio key is enough — or activate Pro for a monthly pool of hosted credits.
Model sources
Four ways to connect a model, none of them required to get started. With a Pro license the simplest is WP Webhooks AI (included) — hosted credits that run on our servers with no keys to configure (see the WP Webhooks AI doc). The others are WordPress connectors (the WordPress 7.0 AI Client, using your site's configured providers, with no keys stored by the plugin), My own keys (Anthropic, OpenAI, or Google — encrypted in the Credentials Vault), or Auto, which prefers WordPress connectors, falls back to your own keys, and only then to the free trial. Activating a Pro license switches to the hosted service without overriding an explicit own-key or connector choice, and if a provider is rate-limited mid-build the agent automatically retries on another connected provider.
Grounded in real site data
The agent works from real payloads, not guesses: field paths in mappings and conditions come from example payloads (args.0.form_id, never invented names) — this site's own capture first, and for a trigger that has never fired here, a reference payload from the Payload Library, always labelled as one. The request going out is grounded the same way: when the destination is HubSpot, Airtable, Notion or another service in the API Docs Library, the agent works from that service's current reference card — endpoint, auth, envelope, known errors — instead of what the model remembers, and the reply says so with a pill. Existing webhooks are edited by id instead of duplicated, and test deliveries verify the integration end to end. Before building an internal automation that calls your own site, it reads the target REST route's real argument contract (via get_rest_route_schema), so required fields like a user's password are handled with a Code Glue snippet — or called out honestly — instead of guessed. Payload field values with sensitive-looking names (passwords, tokens, keys) are redacted before any prompt is built, and stored credentials are never sent to the model.
You approve what goes live
Plans run in order and pause for confirmation before anything real happens: a test delivery that would create or modify actual data (e.g. really create a WordPress user) shows a clear warning first, and a plan review shows the exact PHP a Code Glue snippet step will install — you approve the code, not just a summary. After a build finishes you can flip the webhook between background and synchronous delivery right in the chat, with a recommended mode based on real evidence that your queue is draining.
The same tools, everywhere
Every operation the agent uses is registered through the WordPress Abilities API as flowsystems-webhook-actions/*, so external AI tools like Claude Code and Cursor can drive the identical toolset over MCP or REST with a scoped API token. See the AI Abilities reference in these docs for every tool.
Nothing the agent builds is gated
Every ability the agent has works on the free plugin — including agent-driven Code Glue, where it writes a PHP snippet, test-runs it against your payload with preview_snippet, and assigns it after your confirmation, and multi-rule AND/OR condition groups. Since 3.0.0 there is no licence check anywhere in the abilities layer. What Pro adds is the fuel and the timing: a renewing pool of hosted AI credits so you are not bringing your own key, and External Cron so the queue drains without WP-Cron.
/ Related