Webhook Actions – build automations and integrations with AI help

No API key needed to start

• 55 free credits, no key and no signup — claimed automatically on your first prompt. There is no button to press, no account to create and no card; the plugin sends nothing but your site address. That is about five agent turns, or roughly two complete automations built end to end
• Try it without installing anything — Live Preview (also the button at the top of this page) boots a throwaway WordPress in your browser and runs the real agent on those credits
• WordPress connectors — if your site already has an AI provider connected (Settings → Connectors), the builder uses it directly and the plugin stores no keys
• My own keys — connect Anthropic, OpenAI or Google in the builder; keys are encrypted in the Credentials Vault and never returned over the API. A free Google AI Studio key gives you Gemini at no cost: step-by-step tutorial
• Your own key always wins — once a provider of yours is connected, the free credits are never spent
• Automatic fallback — if a provider is rate-limited mid-build, the agent switches to another connected provider and keeps going

What the AI works from

The agent doesn’t guess — it works from real payloads. It maps fields against actually captured payloads, edits existing webhooks by name or id instead of duplicating them, validates endpoints with a guarded probe (SSRF-protected, secrets always redacted), and verifies the result with a real test delivery. Every operation is also published as a WordPress Ability, so external AI tools (Claude Code, Cursor) can drive the same toolset over the Model Context Protocol (MCP) with scoped API tokens.

The Payload Library

Mapping fields needs an example payload, and until a trigger fires on your site there is nothing to map against — which is worst on the events that are hardest to produce on demand: a refunded order, a cancelled subscription, a deleted user.

The Payload Library closes that gap with hundreds of hook payloads captured on our own test sites — WordPress core, WooCommerce, ACF and the major form plugins — so the agent can work from the real shape of an event your site has never fired. Your own capture always wins the moment the event really fires, and a reference payload is always labelled as one: the trigger panel shows a “WP Webhooks Payload Library” badge naming the plugin build it came off, and every build made from one ends with a test delivery before the webhook can go live.

What a reference payload cannot know is your own keys. Fields inside containers your site defines — a form’s fields, post or order meta, ACF — are never mapped from it; the agent pauses, names the paths, and asks you to fire the event once. Lookups run while Build with AI is on WP Webhooks AI (the free trial or Pro credits) and cost no credits.

The API Docs Library

A language model remembers an API the way it was documented when the model was trained: an old version path, a body envelope that has since changed, a required field it never saw. Build with AI does not build from that memory. When a prompt names a service the library knows — HubSpot, Airtable, Slack, Notion, Stripe, Shopify, OpenAI, Anthropic, Gemini and 300+ more — WP Webhooks AI reads that service’s current reference card on our server and puts it in front of the model before it plans: the exact endpoint and method, how the auth token enters the plan (as a credential step, not a question in chat), the body envelope, request-level flags, and the 4xx responses that come up in practice.

A service nobody has a card for yet is researched on the spot from the vendor’s own documentation — the chat says “Reading …’s API reference for the first time” while it waits, usually under a minute, and the wait costs no credits — and the card is kept for everyone. Every reply built from a card carries a “WP Webhooks API Docs Library” pill naming the service, the operation and the date the reference was verified, linking to the vendor’s page. Available while Build with AI runs on WP Webhooks AI (the free trial or Pro credits); about one credit on the turn that uses a card.

Notifications

Retries handle the flaky minute; Notifications handle the endpoint that stays down at 3 a.m. Get told when a delivery fails, retries, gives up, is skipped, succeeds or recovers — by email, Slack, Discord, Telegram, Microsoft Teams, Google Chat, Mattermost, Pushover, ntfy, SMS and WhatsApp through Twilio, PagerDuty (an incident that opens on failure and resolves on recovery), or any URL as JSON. Rules decide when and where: which attempt, which HTTP codes, which triggers; a quiet time per webhook so a bad hour is one message, not a hundred; hourly or daily digests. Every webhook inherits the site-wide rules, can mute single ones, keep only its own, or switch notifications off. Every message is a template with {{ payload.order.id }} -style placeholders, a field picker, a live preview against your captured payload, a linter — and a Draft with AI button. Channel secrets are encrypted and never shown again. Entirely free. Five-minute setup guide · Feature overview

The engine underneath (free)

• Turn any WordPress do_action into a first-class automation trigger your CRMs, n8n flows, AI agents, and internal services can consume — every dispatch is an outgoing webhook you fully control
• Persistent delivery queue with smart retry and exponential backoff — powered by WP-Cron, auto-upgrades to Action Scheduler or System Cron when available, (Pro) External Cron for guaranteed reliability
• Per-event UUID and ISO 8601 timestamp — enable downstream deduplication
• Delivery logs with full attempt history, request/response inspection, replay, and bulk retry
• Code Glue — attach PHP snippets to any webhook+trigger to reshape the payload before dispatch or run side effects after the response, with a preview that runs your code against a real captured payload first. Build with AI can draft, test-run and assign them for you
• Per-webhook retry limit and backoff strategy (exponential, linear or fixed), each falling back to a site-wide default
• Synchronous execution mode — fire inline without queue delay
• Payload mapping — rename, restructure, exclude, and type-cast fields with dot-notation paths
• Conditional dispatch — filter events by payload field values before dispatch, so a Slack notification or a CRM sync only fires when it should. Build as many rules as you need and group them with AND/OR matching, by hand or by describing them to Build with AI
• HTTP method, custom headers, and URL query parameters per webhook
• Dynamic endpoint URLs — {{ field.path }} placeholders resolved against the payload at dispatch time, or the fswa_webhook_url filter if you would rather do it in PHP
• Webhook Chains — wire 2xx completions to downstream webhooks with full observability
• Import & Export — move webhooks and chains between sites as portable JSON (triggers, field mapping, conditions and Code Glue snippets included), with strict validation and a per-item result summary on import
• Markdown descriptions — document what each webhook and chain does inline, with a Write/Preview toggle while editing
• Notifications — email, Slack, Discord, Telegram, Teams, SMS, PagerDuty and more when a delivery fails, gives u