mateuszflowsystems

<p>Flow Systems Webhook Actions is a developer-focused WordPress webhook delivery layer designed for reliable automation workflows.</p>
<p>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.</p>
<p>Works great with WooCommerce, n8n, Zapier alternatives, and custom APIs.</p>
<p>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.</p>
<p>Unlike basic “fire-and-forget” webhook implementations, this plugin ensures:</p>
<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>
<p>Built for production environments where losing events is not acceptable.</p>
<p>👉 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><br />
👉 Step-by-step example: <a href="https://wpwebhooks.org/examples/gravity-forms-webhooks/" rel="nofollow ugc">Send Gravity Forms Submissions to n8n</a><br />
👉 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></p>
<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>
<p>Every dispatched webhook includes:</p>
<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>
<p>This enables downstream deduplication, idempotent workflow design, and reliable debugging across systems.</p>
<h4>Reliable Queue & Smart Retry</h4>
<p>Webhooks are never sent directly from request execution. Instead:</p>
<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>
<p>Smart retry routing:</p>
<ul>
<li>5xx and 429 responses <span aria-hidden="true" class="wp-exclude-emoji">→</span> automatic exponential backoff retry</li>
<li>4xx and 3xx responses <span aria-hidden="true" class="wp-exclude-emoji">→</span> immediately marked as <code>permanently_failed</code></li>
<li>Configurable maximum retry attempts</li>
<li>Full attempt history stored per event</li>
</ul>
<p>No silent failures.</p>
<h4>Replay Webhook Events</h4>
<p>Webhook debugging is difficult when events cannot be reproduced.</p>
<p>Flow Systems Webhook Actions allows you to replay any webhook event directly from the delivery logs — including successful deliveries.</p>
<p>This makes it easy to:</p>
<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>
<p>Each replay uses the original payload and event metadata, ensuring consistent behavior across retries and debugging sessions.</p>
<h4>Delivery Observability</h4>
<p>Operational visibility built into the admin panel:</p>
<p>Status states: <code>pending</code>, <code>processing</code>, <code>success</code>, <code>failed</code> (retrying), <code>permanently_failed</code></p>
<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>
<p>Filter by: event UUID, target URL, date range, status</p>
<p>Queue health metrics:</p>
<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>
<p>Designed as an operations console — not just a webhook sender.</p>
<h4>Payload Mapping</h4>
<p>Adapt outgoing JSON payloads to match any external API:</p>
<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>
<p>Payloads always include stable event metadata for consistency.</p>
<h4>REST API Access with Token Authentication</h4>
<p>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.</p>
<p>Every endpoint supports dual authentication:</p>
<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>
<p><strong>API Tokens</strong></p>
<p>Create tokens directly from the API Tokens screen in the admin panel. Each token is assigned one of three scopes:</p>
<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>
<p>Token authentication is accepted via:</p>
<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>
<p>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.</p>
<p>Full REST API documentation: <a href="https://wpwebhooks.org/webhook-wordpress-plugin-api/" rel="nofollow ugc">REST API Reference</a></p>
<h4>AI Agents and Programmatic Automation</h4>
<p>The REST API makes Flow Systems Webhook Actions accessible to AI-powered tools and coding agents.</p>
<p>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.</p>
<p>Typical AI-driven workflows include:</p>
<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>
<p>Because the API exposes operational endpoints for logs, queue jobs, webhooks, and triggers, external agents can treat WordPress as a programmable event infrastructure.</p>
<p>Example scenarios:</p>
<p>• A Claude Code agent analyzes webhook delivery logs and automatically retries failed integrations.<br />
• A CI/CD pipeline disables webhook triggers during deployments and re-enables them afterward.<br />
• Automation systems query webhook health metrics and alert when the queue becomes stuck.<br />
• External dashboards display real-time webhook delivery metrics using API tokens.</p>
<p>This allows WordPress automation pipelines to be controlled entirely through HTTP APIs, enabling advanced integration with AI-driven development workflows.</p>
<h4>Contact Form 7 Webhooks (NEW in 1.5.0)</h4>
<p>Flow Systems Webhook Actions includes built-in integration with Contact Form 7.</p>
<p>When Contact Form 7 is active, form submissions are automatically converted into structured webhook payloads — no custom code required.</p>
<p>Included in each payload:</p>
<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>
<p>Benefits:</p>
<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>
<p>This allows you to build reliable form-to-automation pipelines directly from WordPress.</p>
<h4>Action Scheduler Support (NEW in 1.4.0)</h4>
<p>Flow Systems Webhook Actions now supports Action Scheduler — the same background job system used by WooCommerce.</p>
<p>When available, webhook queue processing automatically switches from WP-Cron to Action Scheduler for improved reliability and scalability.</p>
<p>Benefits:</p>
<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>
<p>This makes the plugin suitable for production WooCommerce stores and high-throughput automation pipelines.</p>
<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>
<p>Most WordPress webhook setups fire once, don’t retry intelligently, don’t provide delivery visibility, and don’t expose event identity.</p>
<p>Flow Systems Webhook Actions provides:</p>
<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>
<p>Built for developers who need production-grade automation reliability.</p>
<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.

mifupa

<p>BreznFlow turns n8n workflow JSON exports into interactive, zoomable SVG diagrams inside WordPress. Paste your workflow, and the plugin renders every node with brand-accurate colors, connection lines, and clickable detail panels — directly in your posts and pages.</p>
<p>The plugin was built for mifupa.com, a personal blog where n8n automations are documented regularly. Screenshots get outdated. Embedding the n8n editor is impractical. BreznFlow solves this: one shortcode, one interactive diagram, zero external dependencies.</p>
<h4>At a glance</h4>
<ul>
<li>Renders n8n workflow JSON as interactive SVG diagrams with zoom, pan, and click</li>
<li>86 node types with brand-accurate colors and icons (OpenAI, Slack, GitHub, Telegram, and more)</li>
<li>Click any node to inspect its parameters in a detail panel below the diagram</li>
<li>Automatically masks API keys, tokens, and secrets before storage — the raw JSON is never saved</li>
<li>3-step import wizard: paste JSON, configure display, preview and publish</li>
<li>5 built-in themes (Dark, Light, Minimal, Tech, Brezn) plus custom theme import</li>
<li>Shortcode <code>[breznflow id="X"]</code> with 13 attributes for per-instance configuration</li>
<li>Action bar with share, embed, get JSON, and download actions</li>
<li>Standalone embed page for iframe integration</li>
<li>Related workflows by shared node types</li>
<li>View counter and AI detection badges</li>
<li>Zero dependencies — vanilla JavaScript, no external CDN, no tracking</li>
</ul>
<h4>What makes BreznFlow different</h4>
<ul>
<li><strong>No external services.</strong> Everything runs locally inside WordPress. No CDN, no SaaS, no API calls during page loads.</li>
<li><strong>Security first.</strong> Sensitive data (API keys, tokens, secrets) is automatically detected and replaced with <code>[REDACTED]</code> before storage. The raw workflow JSON is never saved.</li>
<li><strong>Real interactivity.</strong> Not a static image — visitors can zoom, pan, and click nodes to see their configuration.</li>
<li><strong>Vanilla JavaScript.</strong> No React, no jQuery, no build step. The renderer is a single JS file that generates SVG elements directly.</li>
<li><strong>Built for real sites.</strong> Running on the developer’s own production sites since version 1.0.</li>
</ul>
<h4>Display modes</h4>
<ul>
<li><strong>Visual</strong> — full diagram with toolbar, detail panel, and action bar</li>
<li><strong>Info</strong> — node counts only (InfoBox summary like “3× HTTP Request, 2× Code”) — no diagram</li>
<li><strong>Compact</strong> — diagram without toolbar or action bar</li>
</ul>
<h4>Theme system</h4>
<p>5 built-in themes: Dark (default), Light, Minimal, Tech, and Brezn. Custom themes can be imported as <code>.breznflow.json</code> files containing 41 CSS color tokens. Themes are selectable globally, per workflow, or per shortcode.</p>
<h4>Node type registry</h4>
<p>86 predefined node types across 10 categories: Triggers, Core Logic, Data Transformation, Databases, Communication, Google, Dev Tools, AI, Storage, and CRM/Marketing. Unknown node types get a deterministic fallback with auto-generated colors — the same unknown type always looks the same.</p>
<h4>Sensitive data masking</h4>
<p>Before saving, BreznFlow runs a two-pass sanitization:</p>
<ol>
<li>All strings pass through WordPress sanitization</li>
<li>Secret detection scans for API keys in URL parameters, sensitive header values (Authorization, Bearer, X-API-Key), and high-entropy condition values</li>
</ol>
<p>A masking log records every redaction with reason and context — visible in the wizard preview.</p>
<h4>Action bar</h4>
<p>Below the diagram, the action bar provides four configurable actions:</p>
<ul>
<li><strong>Share</strong> — article link and anchor link for hash navigation</li>
<li><strong>Embed</strong> — iframe embed code for standalone embedding</li>
<li><strong>Get JSON</strong> — formatted JSON display with file size</li>
<li><strong>Download</strong> — sanitized JSON file download</li>
</ul>
<p>Each action can be enabled/disabled globally, per workflow, or per shortcode. Embed and Download use dual-gate security (global setting AND per-post permission).</p>
<h3>External Services</h3>
<p>This plugin optionally connects to external services only when you explicitly use the “Import from URL” feature in the workflow import wizard.</p>
<h4>Import from URL</h4>
<p>If you choose to import a workflow by pasting a URL instead of uploading or pasting JSON directly, the plugin makes an HTTP request to that URL using WordPress’s built-in <code>wp_remote_get()</code> function.</p>
<ul>
<li><strong>When:</strong> Only when you click the “Fetch” button in the Add Workflow wizard</li>
<li><strong>What is sent:</strong> Only the URL you provide — no WordPress data, no user data, no cookies</li>
<li><strong>To whom:</strong> Whatever server hosts the URL you provide</li>
<li><strong>Privacy policy:</strong> Depends on the server you connect to</li>
</ul>
<p>No data is transmitted automatically. No data is sent during normal page loads or to visitors browsing your site.</p>
<p>For security, requests to private and internal network addresses are blocked: localhost, <code>127.0.0.0/8</code>, <code>10.0.0.0/8</code>, <code>172.16.0.0/12</code>, <code>192.168.0.0/16</code>, and cloud metadata endpoints (e.g. <code>169.254.169.254</code>).</p>


BreznFlow

Display n8n workflows as interactive SVG diagrams with zoom, pan, node details, and automatic secret masking.

Flow Systems Webhook Actions vs BreznFlow