Webhook Actions – build automations and integrations with AI help vs Challonge

Do you use Challonge for your gaming or sport events? The Challonge plugin integrates your Challonge tournaments into your WordPress website so your users may easily see recent tournaments, their progress, and even sign up and participate. Features Adaptive caching and background refresh allows your pages to load a lot faster than before! – New in 1.1.6! Only registered users may sign up to your tournaments. Likewise, your users may forfeit a tournament after signing up, but only before it begins. Participating users may report their own scores. Includes role capabilities. You will need a role management plugin to change who has these capabilities. Custom participant name templating. Languages English Spanish (68%) – Thanks to Andrew Kurtis from WebHostingHub for translating! Requirements In order to use the API, you will need cURL. Most PHP installations include cURL. Latest Information Keep up to date with upcoming release information on my website: https://zavaboy.org/challonge-wordpress-plugin/ Getting Started Before you start using this plugin, here’s what you’ll need: A Challonge.com account. Registration is free. A valid Developer API Key so the Challonge plugin can talk with your Challonge.com account. Once you have the Challonge plugin installed and activated on your website, you will need to enter your Challonge.com API key in ‘Settings’ > ‘Challonge’. Once you have done that, you have unlocked the full power of this nice plugin. Shortcode You may use a shortcode in posts and pages to display a tournament or list out tournaments. [challonge] – This will list out all tournament brackets in your account, excluding all organizations. [challonge url="w4la9fs6"] – This will embed a tournament bracket. This may be any Challonge bracket, not just your own. [challonge subdomain="my_sub"] – This will list out all tournament brackets in the ‘my_sub’ organization. (eg: my_sub.challonge.com) [challonge url="w4la9fs6" theme="2" show_final_results="1" width="90%" height="600px"] – This is just a more customized version of the first shortcode. If you have a tournament bracket within an organization, you will have to use the subdomain attribute along with the url attribute, like so: [challonge url="w4la9fs6" subdomain="my_sub"] Here’s all the shortcode attributes available to you: url – The URL to a tournament. subdomain – The subdomain of the tournament URL or if no tournament URL is provided, the listing will be tournaments within the specified subdomain. theme – The theme ID you would like to use. multiplier – Scales the entire bracket. match_width_multiplier – Scales the width allotted for names. show_final_results – Display the final results above your bracket. show_standings – For round robin and Swiss tournaments, you can opt to show a table of the standings below your bracket. width – The width of the embedded tournament bracket. height – The height of the embedded tournament bracket. limit – Limit the number of returned results for tournament listings. allowusers / denyusers / allowroles / denyroles – A comma separated list of users or roles you would like to specifically allow or deny from viewing the tournament bracket or tournament listings. statuses / excludestatuses – A comma separated list of tournament statuses you would like to specifically show or hide from the tournament listings. All statuses: “Pending,Checking In,Checked In,Underway,Awaiting Review,Complete” listparticipants – List participants currently in the tournament. (Must be used with url) – New in 1.1.6! Widget To allow your users to signup and report their own scores, just add the plugin widget. The widget has the following options: Title – The title of the widget, nothing special here. Defaults to ‘Challonge’. Subdomain – The subdomain to list your tournaments from. (Optional) Tournament Filter – Only tournament names that match this filter will be listed. (Optional) This may be a simple wildcard filter, for example My * Tournament will match ‘My Big Tournament’ but not ‘Your Big Tournament’. If you need a more robust filter, you may use Regular Expressions (PCRE) like so: /My \d+(st|nd|rd|th) Tournament/i will match ‘My 3rd tournament’ but not ‘My Third Tournament’ Status Filter – Only list tournaments with the selected statuses, unless none are selected. Max tournaments listed – The maximum number of tournaments that the widget will list. Defaults to 10. Integrating Challonge.com Tournaments Challonge.com tournaments may be easily setup to allow your WordPress users to signup and report scores. Here are a few things you should know when setting up your Challonge.com tournaments: Turning ‘Host a sign-up page’ on will allow your users to signup through the widget. In ‘Advanced Options’ > ‘Permissions’: Turning ‘Allow participants with Challonge accounts to report their own scores.’ on will allow your users to report their own scores through the widget. In ‘Advanced Options’ > ‘Permissions’: Turning ‘Exclude this event from search engines and the public browsable index.’ on will hide the tournament from the shortcode and widget tournament listings. Did You Know? If you run the same tournaments on multiple WordPress websites, your WordPress users will be tracked in your Challonge.com tournaments by their email address and login name, even if their display name differs. With this in mind, users may signup and report their score using either website. Also note, users who change their email address will lose access to any of their preexisting tournament signups. Good luck!

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, captures a real example payload from your site, 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/ 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, 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. Bring your own AI — free options included WordPress 7.0 AI Client — if your site already has an AI provider connected (Settings → Connectors), the builder uses it directly; the plugin stores no keys Your own API key — connect Anthropic, OpenAI, or Google in the builder; keys are encrypted in the Credentials Vault and never returned over the API Free to run — a free Google AI Studio key gives you Gemini at no cost: step-by-step tutorial 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 your site’s real data. 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 MCP with scoped API tokens. 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 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 HTTP method, custom headers, and URL query parameters per webhook Dynamic endpoint URLs — {{ field.path }} placeholders resolved at dispatch time (free via fswa_webhook_url filter) 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, and conditions included; Code Glue with Pro), 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 AI writes Code Glue for you — the agent drafts PHP snippets, test-runs them against your real captured payloads, and assigns them to webhooks (with your confirmation) for pre-dispatch payload enrichment or post-dispatch side effects AI sets advanced conditions — with Pro the agent can propose multi-rule AND/OR condition groups instead of a single rule Code Glue — attach PHP snippets to any webhook+trigger (pre-dispatch payload enrichment, post-dispatch side effects) 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 Unlimited conditions per trigger with AND/OR groups Per-webhook retry limit and backoff strategy overrides Dynamic URL templates — {{ }} syntax with no custom PHP required 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