Farhan Srambiyan

<p>This plugin adds a customizable n8n chat widget to your website frontend. It allows visitors to interact with n8n chat workflows directly from your website through a popup interface.</p>
<h4>Features</h4>
<ul>
<li>Easily integrate n8n chat workflows into your website</li>
<li>Customizable chat widget appearance:
<ul>
<li>Choose the widget position (left or right)</li>
<li>Set custom widget title</li>
<li>Change the primary color</li>
<li>Select custom emoji icon or upload SVG icon</li>
<li>Adjust content zoom level (50% – 150%)</li>
</ul>
</li>
<li>Mobile-responsive design</li>
<li>Smooth animations</li>
<li>Lightweight implementation</li>
</ul>
<h4>Requirements</h4>
<ul>
<li>WordPress 5.0 or higher</li>
<li>n8n with an existing chat workflow</li>
</ul>
<h3>Configuration</h3>
<ol>
<li><strong>n8n Chat URL</strong>: Enter the full URL of your n8n chat webhook (e.g., <code>https://n8n.example.com/webhook/your-chat-id/chat</code>)</li>
<li><strong>Enable Chat Widget</strong>: Toggle to enable or disable the chat widget on your website</li>
<li><strong>Widget Position</strong>: Choose between right or left side positioning</li>
<li><strong>Chat Widget Title</strong>: Set the title that appears in the chat header</li>
<li><strong>Widget Color</strong>: Select a custom color for the widget button and header</li>
<li><strong>Chat Icon</strong>: Choose an emoji or upload an SVG icon for the chat button</li>
<li><strong>Chat Content Zoom</strong>: Adjust the zoom level of the chat content</li>
</ol>
<h3>External Services</h3>
<p>This plugin connects to an external service (n8n) to provide chat functionality:</p>
<h4>n8n Chat Service</h4>
<ul>
<li><strong>What is it?</strong>: n8n is a workflow automation platform that can be configured to provide AI-powered chat functionality.</li>
<li><strong>What data is sent</strong>: When a user interacts with the chat widget, their messages are sent to your n8n instance via the webhook URL you provide in the settings.</li>
<li><strong>When data is sent</strong>: Data is only sent when a user actively engages with the chat widget by opening it and sending messages.</li>
<li><strong>Terms and Privacy</strong>: This plugin requires you to have your own n8n instance or use n8n Cloud. For more information about n8n’s terms and privacy policy, please visit:
<ul>
<li><a href="https://n8n.io/legal/terms/" rel="nofollow ugc">n8n Terms of Service</a></li>
<li><a href="https://n8n.io/legal/privacy/" rel="nofollow ugc">n8n Privacy Policy</a></li>
</ul>
</li>
</ul>
<p>Note: You are responsible for ensuring that your use of n8n complies with all applicable laws and regulations regarding user data and privacy.</p>


n8n Chat Widget

Adds a customizable n8n chat widget to your website frontend. It allows visitors to interact with n8n chat workflows directly from your website throug …

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.

n8n Chat Widget vs Flow Systems Webhook Actions