Social Pulse vs Webhook Actions – build automations and integrations with AI help

Describe the integration you want. The AI builds it. Webhook Actions ships with Build with AI — an in-admin agent that turns a plain-language request like “When a Contact Form 7 form is submitted, send it as JSON to my n8n webhook” into a working, tested automation. The agent proposes a plan you can review and edit, then creates the webhook, works from a real example payload — your site’s own capture, or the Payload Library for an event your site has never fired — maps the fields, sets dispatch conditions, probes your endpoint, and sends a test delivery. Nothing goes live without your confirmation — new webhooks are always created disabled, and you can undo the last change with one click. 📖 Full documentation at wpwebhooks.org/docs/ ▶️ Try it in your browser — no install, no signup, no API key What you can connect Sources — anything in WordPress that fires an action. Webhook Actions turns any do_action into a trigger, so form submissions, WooCommerce orders, user registrations, post publishes and your own custom plugin events can all start an automation. That covers Elementor Forms, WPForms, Forminator, Fluent Forms, Gravity Forms, WooCommerce and your own code — there is no per-plugin add-on to hunt down. Contact Form 7 and IvyForms go one step further with built-in support: their submissions are normalized into clean JSON payloads automatically. Destinations — any HTTP endpoint. The plugin sends outgoing webhooks to anything that accepts a request: an n8n, Make (formerly Integromat), Zapier or Pabbly webhook node, a Slack or Discord incoming-webhook URL for order and form notifications, Airtable, Google Sheets, Mailchimp, HubSpot, Salesforce, Notion, your CRM, an internal microservice, or an AI agent API. There are no bundled per-service connectors and none are needed — point a webhook at a URL, map the fields, and send. Every delivery is queued, retried on failure and logged with full request and response history. That makes it a no-code way to sync WordPress data outward: describe what you want in chat and let the AI build it, or wire it up by hand in the admin UI. No PHP required either way. 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 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 Credentials Vault — store reusable auth secrets (Bearer, Basic, API key, custom) encrypted at rest; reference them from webhooks instead of pasting raw Authorization headers. Secrets are write-only over the API — never returned, only a masked hint Activity History — persistent audit log of every admin and API-token action Built-in CF7 and IvyForms integrations — structured payloads, no extra plugins Action Scheduler auto-detection — more reliable delivery on high-traffic sites Fully translatable — the entire admin interface and all server-side strings are internationalized; ships with Polish, Simplified Chinese, and Dutch, and is compatible with WPML and Polylang String Translation Full REST API with scoped API token authentication (read / operational / full / agent) — the agent scope grants full write access for AI assistants while never exposing stored secrets Developer extensibility — 16 filters and 7 action hooks (reference) Pro features AI credits included — Build with AI runs through the hosted WP Webhooks AI service on every Pro plan: no API keys to create, no provider accounts, a monthly credit allowance that renews automatically, and a live credits counter in the builder. Your own keys and WordPress connectors stay available any time External Cron — replace unreliable visitor-triggered WP-Cron with a managed external pinger, provisioned automatically on license activation. Two modes: plugin queue endpoint (down to 20 s interval, configurable batch size) or WP-Cron endpoint (60 s, covers all WordPress background work). No server crontab or external dashboard — controlled entirely from wp-admin, with a live heartbeat chart and inline error alerts See pricing and upgrade → Examples Send Contact Form 7 submissions to a webhook (n8n demo) Send Gravity Forms Submissions to n8n Send IvyForms submissions to a webhook (n8n demo) WooCommerce orders to n8n on completion — wired up with a Claude Code agent WooCommerce to HubSpot integration — sync orders, contacts, and deals with no custom code

Social Pulse … is a WP plugin showing follower counts from YouTube, Facebook, X, and Steam. It uses Leader/Follower modes to reduce API requests. General Idea Social Pulse retrieves follower numbers from multiple platforms and displays them via WordPress shortcodes. In Leader mode, the plugin directly makes API requests to obtain the latest values, which are then cached and exposed at a dedicated URL. In Follower mode, the plugin skips direct API calls and instead retrieves the pre-fetched data from the Leader instance. * Screenshot Leader-Mode * Screenshot Follower-Mode Try it out! Download the ZIP Navigate to the WordPress Playground Go to the “Plugins” page Click “Add New Plugin” Click “Upload Plugin” Select the ZIP and click “Install Now” Click “Activate Plugin” The plugin should now be visible at the bottom of the WordPress menu. Leader and Follower Mode Leader Mode: In this mode, Social Pulse performs the actual API calls to get the latest follower counts and caches these values. The current values are also exposed at a special URL (e.g. /social-counters/values), which can be used by Follower instances. Follower Mode: Follower mode is designed to minimize API calls on installations that do not need to fetch data directly. Instead of making API requests, the plugin retrieves the cached values from the Leader URL. This is particularly useful when dealing with strict API rate limits. How to Use Social Pulse in Leader Mode Activate Leader Mode: In the plugin settings, select Leader as the mode. Configure API Credentials: Enter your API keys, tokens, and IDs for YouTube, Facebook, X, and Steam in the respective fields. Save Changes: Make sure to save your settings. Retrieve Values: The plugin will automatically fetch and cache the current follower counts. The exposed values URL (displayed on the settings page) can be used by Follower installations. How to Use Social Pulse in Follower Mode Activate Follower Mode: In the plugin settings, select Follower as the mode. Enter Leader URL: Provide the URL from a Leader installation (the URL where the leader exposes its cached values). Save Changes: Save your settings to store the Leader URL. Automatic Data Fetch: The plugin will now retrieve the follower values from the Leader URL every 5 minutes or whenever manually tested. Direct API requests are disabled in this mode. Where to Find the Necessary Information For each platform, you will need to obtain API keys, tokens, or IDs. Here are some helpful links to get you started: YouTube: YouTube Data API v3 – Getting Started (Find your API key and channel ID here.) Facebook: Facebook for Developers, Long Lasting Tokens for Clients (Learn how to create an app, get an access token, and locate your Page ID.) X (formerly Twitter): X Developer Platform, Generating and Using an App-Only Bearer-Token (Obtain a Bearer Token and set up your developer credentials.) Steam: Steam Web API Documentation (Find information on obtaining your Steam App ID and using the API.) External services WordPress guidelines require that the use of external services is clearly statet. Although this is the sole purpose of this plugin I hereby state the following external service usage: * Youtube API (https://www.googleapis.com/youtube/v3/channels) The Youtube API is used to receive the youtube followers of the account the “Youtube API Key” belongs to. * Steam API (https://api.steampowered.com/ISteamUserStats/GetNumberOfCurrentPlayers/v1/) The Steam API is used to receive the current players of the Steam app with the “Steam App ID” you enter. * Facebook API (https://graph.facebook.com/v22.0/) The Facebook API is used to gather fan or follower count of the facbook page with the “Facebook Page ID” you enter. * X API (https://api.twitter.com/2/users/by/username/) The X API is used to gather the follower count of the account with the “X Username” you enter.