mateuszflowsystems

Flow Systems Webhook Actions is a developer-focused WordPress webhook delivery layer designed for reliable automation workflows.
It adds a persistent queue, automatic retries, and Action Scheduler support for production-grade background processing — so your webhooks don’t get lost when external APIs fail.
Works great with WooCommerce, n8n, Zapier alternatives, and custom APIs.
Includes built-in Contact Form 7 integration — send CF7 form submissions to webhooks instantly with clean, structured payloads. Replace fragile CF7 email workflows with reliable webhook-based automation.
Unlike basic “fire-and-forget” webhook implementations, this plugin ensures:
<ul>
<li>Delivery attempts are tracked</li>
<li>Failures are visible</li>
<li>Retries are automatic and intelligent</li>
<li>Events include stable identity metadata for idempotency</li>
</ul>
Built for production environments where losing events is not acceptable.
👉 Step-by-step example: <a href="https://wpwebhooks.org/examples/cf7-to-webhook/" rel="nofollow ugc">Send Contact Form 7 submissions to a webhook (n8n demo)</a> 
👉 Step-by-step example: <a href="https://wpwebhooks.org/examples/gravity-forms-webhooks/" rel="nofollow ugc">Send Gravity Forms Submissions to n8n</a> 
👉 Step-by-step example: <a href="https://wpwebhooks.org/examples/ivyforms-to-webhook/" rel="nofollow ugc">Send IvyForms submissions to a webhook (n8n demo)</a>
<h4>Typical Use Cases</h4>
<ul>
<li>CF7 to Webhook: Send Contact Form 7 Data to n8n or external APIs</li>
<li>Gravity Forms webhooks for sending submission to CRM</li>
<li>Send IvyForms submissions to n8n or external APIs</li>
<li>Build reliable form-to-CRM integrations with retry protection</li>
<li>Process high-volume WooCommerce webhooks using Action Scheduler</li>
<li>Send WooCommerce orders to n8n with retry protection</li>
<li>Sync WordPress users to external CRMs safely</li>
<li>Trigger backend microservices from WP hooks</li>
<li>Send event-driven data to internal APIs</li>
<li>Replace fragile custom <code>wp_remote_post()</code> integrations</li>
<li>Build idempotent WordPress automation pipelines</li>
<li>Query delivery logs, trigger retries, or manage webhooks programmatically from CI/CD pipelines or external dashboards using API tokens</li>
<li>Allow AI coding assistants (e.g. Claude Code) to inspect webhook logs and retry failed events automatically</li>
<li>Use AI agents to monitor webhook delivery health and operate the queue through the REST API</li>
</ul>
<h4>Event Identity & Idempotency</h4>
Every dispatched webhook includes:
<ul>
<li>Unique UUID (v4) per event</li>
<li>ISO 8601 UTC timestamp</li>
<li>Embedded <code>event.id</code>, <code>event.timestamp</code>, <code>event.version</code> in the payload</li>
<li>HTTP headers: <code>X-Event-Id</code>, <code>X-Event-Timestamp</code></li>
</ul>
This enables downstream deduplication, idempotent workflow design, and reliable debugging across systems.
<h4>Reliable Queue & Smart Retry</h4>
Webhooks are never sent directly from request execution. Instead:
<ul>
<li>Events are stored in a persistent database queue</li>
<li>Processed asynchronously via background jobs</li>
<li>Dispatched in batches to avoid performance impact</li>
</ul>
Smart retry routing:
<ul>
<li>5xx and 429 responses → automatic exponential backoff retry</li>
<li>4xx and 3xx responses → immediately marked as <code>permanently_failed</code></li>
<li>Configurable maximum retry attempts</li>
<li>Full attempt history stored per event</li>
</ul>
No silent failures.
<h4>Replay Webhook Events</h4>
Webhook debugging is difficult when events cannot be reproduced.
Flow Systems Webhook Actions allows you to replay any webhook event directly from the delivery logs — including successful deliveries.
This makes it easy to:
<ul>
<li>Re-run automation workflows</li>
<li>Debug external integrations</li>
<li>Recover from temporary endpoint failures</li>
<li>Test webhook consumers without recreating WordPress events</li>
</ul>
Each replay uses the original payload and event metadata, ensuring consistent behavior across retries and debugging sessions.
<h4>Delivery Observability</h4>
Operational visibility built into the admin panel:
Status states: <code>pending</code>, <code>processing</code>, <code>success</code>, <code>failed</code> (retrying), <code>permanently_failed</code>
<ul>
<li>Attempt timeline per event</li>
<li>HTTP status codes and response bodies</li>
<li>Inspect full request payloads</li>
<li>Manual retry (single or bulk)</li>
<li>Replay webhook events for debugging and testing integrations</li>
</ul>
Filter by: event UUID, target URL, date range, status
Queue health metrics:
<ul>
<li>Average attempts per event</li>
<li>Oldest pending job age</li>
<li>Queue stuck detection</li>
<li>WP-Cron-only warning</li>
</ul>
Designed as an operations console — not just a webhook sender.
<h4>Payload Mapping</h4>
Adapt outgoing JSON payloads to match any external API:
<ul>
<li>Rename fields using dot notation</li>
<li>Restructure nested objects</li>
<li>Exclude sensitive or unnecessary data</li>
<li>Store example payloads for configuration</li>
<li>Modify via <code>fswa_payload</code> filter</li>
</ul>
Payloads always include stable event metadata for consistency.
<h4>REST API Access with Token Authentication</h4>
The plugin exposes a full operational REST API (<code>/wp-json/fswa/v1/</code>) that powers the admin interface and can also be used directly by external tools, automation systems, AI agents, and CI/CD pipelines.
Every endpoint supports dual authentication:
<ul>
<li>WordPress admin session (cookie-based, used by the admin panel)</li>
<li>API token — for programmatic access without a browser session</li>
</ul>
API Tokens
Create tokens directly from the API Tokens screen in the admin panel. Each token is assigned one of three scopes:
<ul>
<li><code>read</code> — GET access to webhooks, logs, queue, health, triggers, and schemas</li>
<li><code>operational</code> — Read + toggle webhooks on/off, retry and replay log entries, execute queue jobs</li>
<li><code>full</code> — Operational + create, update, and delete webhooks, schemas, and queue jobs</li>
</ul>
Token authentication is accepted via:
<ul>
<li><code>X-FSWA-Token: <token></code> header (recommended)</li>
<li><code>Authorization: Bearer <token></code> header</li>
<li><code>?api_token=<token></code> query parameter</li>
</ul>
Tokens can be set to expire and rotated at any time. Rotation issues a new secret immediately while preserving the token’s name, scope, and settings. Token management always requires a WordPress admin login — tokens cannot be used to create or manage other tokens.
Full REST API documentation: <a href="https://wpwebhooks.org/webhook-wordpress-plugin-api/" rel="nofollow ugc">REST API Reference</a>
<h4>AI Agents and Programmatic Automation</h4>
The REST API makes Flow Systems Webhook Actions accessible to AI-powered tools and coding agents.
Automation systems, CI pipelines, and AI coding assistants (such as Claude Code or Cursor) can safely interact with webhook infrastructure using API tokens without requiring WordPress admin sessions.
Typical AI-driven workflows include:
<ul>
<li>AI agents monitoring webhook delivery health</li>
<li>Automatically retrying failed webhook events</li>
<li>Inspecting delivery logs to debug integrations</li>
<li>Enabling or disabling webhooks dynamically during deployments</li>
<li>Managing automation pipelines across environments</li>
</ul>
Because the API exposes operational endpoints for logs, queue jobs, webhooks, and triggers, external agents can treat WordPress as a programmable event infrastructure.
Example scenarios:
• A Claude Code agent analyzes webhook delivery logs and automatically retries failed integrations. 
• A CI/CD pipeline disables webhook triggers during deployments and re-enables them afterward. 
• Automation systems query webhook health metrics and alert when the queue becomes stuck. 
• External dashboards display real-time webhook delivery metrics using API tokens.
This allows WordPress automation pipelines to be controlled entirely through HTTP APIs, enabling advanced integration with AI-driven development workflows.
<h4>Contact Form 7 Webhooks (NEW in 1.5.0)</h4>
Flow Systems Webhook Actions includes built-in integration with Contact Form 7.
When Contact Form 7 is active, form submissions are automatically converted into structured webhook payloads — no custom code required.
Included in each payload:
<ul>
<li>Form ID and title</li>
<li>Submission data (all fields)</li>
<li>Normalized field structure (no raw CF7 format)</li>
<li>Request metadata</li>
<li>Uploaded files (where applicable)</li>
</ul>
Benefits:
<ul>
<li>Send CF7 submissions to n8n, APIs, CRMs, or automation tools</li>
<li>No need for custom hooks or additional plugins</li>
<li>Clean JSON payloads ready for external processing</li>
<li>Works with existing webhook retry, queue, and replay system</li>
</ul>
This allows you to build reliable form-to-automation pipelines directly from WordPress.
<h4>Action Scheduler Support (NEW in 1.4.0)</h4>
Flow Systems Webhook Actions now supports Action Scheduler — the same background job system used by WooCommerce.
When available, webhook queue processing automatically switches from WP-Cron to Action Scheduler for improved reliability and scalability.
Benefits:
<ul>
<li>More reliable background execution than WP-Cron</li>
<li>Better handling of high-volume webhook traffic</li>
<li>Persistent job tracking and recovery</li>
<li>No configuration required — automatic detection and migration</li>
</ul>
This makes the plugin suitable for production WooCommerce stores and high-throughput automation pipelines.
<h4>Developer Friendly</h4>
<ul>
<li>Works with any WordPress or WooCommerce action</li>
<li>Full REST API (<code>/wp-json/fswa/v1/</code>) usable from any HTTP client — not just the admin panel</li>
<li>API token authentication with scoped access (<code>read</code>, <code>operational</code>, <code>full</code>)</li>
<li>Fully extensible via filters and actions</li>
<li>Clean namespace and unique prefixes</li>
<li>Built according to WordPress.org standards</li>
<li>Supports system cron, WP-Cron, and Action Scheduler (auto-detected)</li>
</ul>
<h4>Why Choose Flow Systems Webhook Actions?</h4>
Most WordPress webhook setups fire once, don’t retry intelligently, don’t provide delivery visibility, and don’t expose event identity.
Flow Systems Webhook Actions provides:
<ul>
<li>Persistent queue</li>
<li>Smart retry logic</li>
<li>Webhook replay for debugging integrations</li>
<li>Permanent failure state handling</li>
<li>Event UUIDs and timestamps</li>
<li>Full delivery logging and metrics</li>
<li>REST API with token authentication for programmatic access</li>
<li>Action Scheduler support for reliable background processing (when available)</li>
<li>Built-in CF7 to webhook support (no extra plugins needed)</li>
</ul>
Built for developers who need production-grade automation reliability.
<h4>Available Filters</h4>
<ul>
<li><code>fswa_should_dispatch</code> – Decide if a trigger should dispatch</li>
<li><code>fswa_payload</code> – Customize webhook payload</li>
<li><code>fswa_headers</code> – Add custom HTTP headers</li>
<li><code>fswa_require_https</code> – Toggle HTTPS requirement</li>
<li><code>fswa_max_attempts</code> – Configure maximum retry attempts</li>
<li><code>fswa_queue_batch_size</code> – Configure batch processing size</li>
<li><code>fswa_http_timeout</code> – Configure HTTP request timeout</li>
<li><code>fswa_http_connect_timeout</code> – Configure HTTP connect timeout</li>
<li><code>fswa_http_args</code> – Customize HTTP request arguments</li>
<li><code>fswa_available_triggers</code> – Customize available trigger list</li>
</ul>
<h4>Available Actions</h4>
<ul>
<li><code>fswa_success</code> – Fired after successful webhook delivery</li>
<li><code>fswa_error</code> – Fired after webhook delivery failure</li>
</ul>
<h4>Admin UX Improvements</h4>
<ul>
<li>Option to move the plugin menu under “Tools” for a cleaner admin sidebar</li>
<li>Instant UI refresh when changing menu location</li>
</ul>

Flow Systems Webhook Actions

Reliable WordPress webhooks with retries, queue, Action Scheduler support, delivery logs, and replayable events for n8n, APIs, and integrations.

DVYZR

Tired of logging into countless WordPress sites for routine checks? Synapse transforms your website into a powerful “WordPress Data Bridge”, giving you programmatic access to the data you need. Connect your site to automation platforms like n8n, Zapier, Make, or your own custom applications.
Synapse is the essential tool for developers, agencies, and security-conscious site owners who want to build efficient workflows, monitor sites remotely, and manage WordPress like a pro.
A POWERFUL LOCAL DASHBOARD & ROBUST API IN ONE
Even as a standalone tool, Synapse provides a valuable local dashboard in your WordPress admin area. Get an instant overview of:
<ul>
<li>Available Updates: All pending updates for core, plugins, and themes at a glance.</li>
<li>Website Health Status: Proactively monitor your site’s health and security.</li>
<li>Moderation Queue: See how many comments or posts are awaiting your approval.</li>
</ul>
But the true power lies in its API. See the full <a href="https://dvyzr.com/synapse-documentation/" rel="nofollow ugc">User Documentation</a> to get started.
KEY API FEATURES (FREE VERSION)
The free version provides the endpoints you need for essential monitoring and maintenance:
<ul>
<li>Monitor Available Updates (<code>/updates</code>): Get a detailed JSON list of all pending WordPress core, plugin, and theme updates.</li>
<li>Check Site Health (<code>/site-health</code>): Receive a comprehensive, machine-readable status report on your site’s performance and security.</li>
<li>View Moderation Queue (<code>/moderation</code>): Check the number of pending comments and posts.</li>
<li>Execute Remote Updates (<code>/updates/...</code>): Trigger plugin, theme, or core updates securely and remotely—perfect for automated maintenance scripts.</li>
</ul>
Explore the full <a href="https://wp-api.dvyzr.com/documentation.html" rel="nofollow ugc">Synapse REST API Documentation</a> to see all possibilities.
WHAT CAN YOU BUILD WITH SYNAPSE? (AUTOMATION USE CASES)
Synapse is designed to be the central hub for your WordPress automation workflows. Here are just a few examples:
<ul>
<li>Proactive Security Monitoring: Build a daily workflow in n8n that checks for security updates and sends a notification to your Slack or Discord channel.</li>
<li>Instant Issue Alerts: Set up an automation that sends a push notification to your phone the moment your site’s health status becomes “critical”.</li>
<li>Efficient Content Management: Automatically create a new task in Trello or Asana whenever a new post is submitted for moderation.</li>
<li>Automated Maintenance Workflows: Create a script that automatically creates a backup of your site and then triggers all pending plugin and theme updates via the Synapse API.</li>
</ul>
FROM A SINGLE SITE TO AN ENTIRE NETWORK
This free plugin is the perfect “Connector” to monitor and manage a single WordPress site.
Looking to manage multiple client sites from a single, central dashboard? The Synapse PRO version allows you to connect all your websites and manage them from one central location, run selective updates without logging in, and much more. The upcoming Synapse ULTIMATE will provide advanced API endpoints for user and content management, making it the ultimate tool for agencies and power users.

Synapse – Data Bridge for Automation

The data bridge for WordPress. A powerful REST API to monitor sites and automate workflows with n8n, Zapier, Make, and your own scripts.

Flow Systems Webhook Actions vs Synapse – Data Bridge for Automation