Let’s build something.
Describe the integration in plain words. The agent plans it, then builds and tests it for you in your WordPress admin panel.
It has already seen the payload and read the API.
A real example of the event — yours, or one of ours for an event your site has never fired — and the destination's current API reference, read before a single field is mapped.
- Payload Library 574 hook payloads from WordPress core, WooCommerce and the major form plugins
- API Docs Library 312 APIs — HubSpot, OpenAI, Slack, Stripe — read on our server, not remembered
- Free credits 55 on every install. No key, no signup, no card.
From install to your first working automation in about two minutes — free AI credits included, no key to set up.
One sentence in. A shipped pipeline out.
Not demos of what could work — documented builds you can replay on your own site, prompt included.
Contact form → n8n
“When a Contact Form 7 form is submitted, send it as JSON to my n8n webhook.”
Queued before the reply renders, delivered with automatic retry on failure.
WooCommerce → HubSpot deal lifecycle
“Create a HubSpot deal when an order is placed — and move it to Closed Won when it completes.”
Two webhooks, zero SDK, deal stages that follow the order on their own.
Built by Claude Code over REST
“Create a webhook for completed orders and send them to n8n. — typed into Claude Code, not the admin.”
The assistant provisions everything over the REST API, catches its own field-path mistake, and fixes it live.
Gravity Forms → n8n
“Send Gravity Forms entries to n8n with just the fields I need.”
Field mapping, automatic retries, and a full log of every attempt.
You just became the integrations department.
Two-week projects become a sentence.
The wiring job that used to mean quotes, tickets, and a specialist is now something you type. Review the plan, flip the switch, take the credit.
Your builds come out engineered, not glued.
Queued, retried, logged, replayable — every automation ships on infrastructure a ten-year integrations engineer would sign off on. Nobody has to know it took you a minute.
Describe once. Adjust in one line.
"Actually, only orders over $50." "Rename that field before it sends." The agent edits what it built — or open the manual editor and fine-tune by hand when you feel like it.
Claude Code and Cursor can run it for you.
The same toolset is exposed over MCP and a token-scoped REST API, so your coding agent can build, inspect logs, and retry deliveries — without ever touching admin credentials.
The senior engineer is included. You bring the sentence.
The toolkit a senior engineer would insist on. The AI already uses it.
Queue, retry, logs, replay, credentials vault, conditions — the agent builds on these instead of generating fragile glue code. And every one of them is still there when you want manual control.
Nothing blocks the request
Your event is enqueued in under 5ms and drained by background workers — checkout never waits on a slow endpoint. WP-Cron → Action Scheduler → System Cron → External Cron (Pro).
Failures fix themselves
A flaky endpoint retries on its own — 1m → 2m → 4m → 8m, capped at 1h, 5 attempts by default. Tune the limit and the curve per webhook.
You can always see what happened
Every attempt is recorded: payload, response, status, latency, attempt count. Filter by hook, endpoint, status, or time window.
Recover with one click
Failed delivery? Replay it. Re-run a window. Re-evaluate a skipped event after fixing its conditions — from the admin or the REST API.
Downstream dedup is free
Every event carries a v4 UUID plus X-Event-Id and X-Webhook-Id headers, so receivers deduplicate and stay idempotent without inspecting the payload.
Only the events that matter
Fire only when order.total > $50, only when a product is in the cart, only when it's real traffic. Build as many rules as you need and group them with AND/OR matching — all free.
Every move it makes, written down.
Click any row to see the exact request body, response body, headers, and full attempt history. Failed? Replay it. And it's not just deliveries — every change the AI agent makes lands in the Activity History, so you always know who did what, human or machine.
Nothing to lose: new webhooks start disabled, and every change can be undone.
WordPress already broadcasts everything. That surface is your integration layer.
WordPress already broadcasts everything important as an action — orders placed, forms submitted, posts published, users registered, subscriptions renewed. This plugin turns that action surface into your integration surface. Any do_action on your site — including ones a plugin update ships next month — becomes a trigger you can map and send anywhere.
No vendor SDK. No custom integration plugin per service. No glue code rotting in functions.php. The hook itself is the API — and the toolkit around it (queue, retries, idempotent headers, scoped REST tokens, a full delivery log, replay) makes the WordPress side of your stack finally look like the rest of it.
The AI is optional. Everything the agent does you can click together by hand, script over the token-scoped REST API, or drive from an external agent via MCP — same engine either way. Full plugin spec · API reference · AI cost calculator
Own the whole pipeline for free. Pay only to go further.
Build with AI ships in the free plugin and starts with 55 credits on the house — no key, no signup. After that, a free Google AI Studio key keeps it running, or a Pro plan includes hosted credits so you never manage a key at all. The free plugin runs production webhooks on unlimited sites — async queue, retries, the full delivery log, replay, the REST API, payload mapping, unlimited conditions with AND/OR groups, per-webhook retry and backoff, Code Glue PHP snippets and {{ field.path }} dynamic URL templates. Pro adds the two things that run on our servers: hosted AI credits, and a built-in External Cron that replaces WP-Cron entirely.
Prices exclude VAT. Any applicable tax is calculated and shown at checkout.
Things engineers always ask.
Don't see yours? Open an issue on GitHub or check the full reference in the API docs.