[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f87L7HIhEiEFmdXmHyzOIKKrlIEM3SZqx9TEWLpizep4":3},{"slug":4,"display_name":4,"profile_url":5,"plugin_count":6,"total_installs":7,"avg_security_score":8,"avg_patch_time_days":9,"trust_score":10,"computed_at":11,"plugins":12},"mateuszflowsystems","https:\u002F\u002Fprofiles.wordpress.org\u002Fmateuszflowsystems\u002F",1,0,100,30,94,"2026-04-05T02:03:55.991Z",[13],{"slug":14,"name":15,"version":16,"author":4,"author_profile":5,"description":17,"short_description":18,"active_installs":7,"downloaded":19,"rating":8,"num_ratings":20,"last_updated":21,"tested_up_to":22,"requires_at_least":23,"requires_php":24,"tags":25,"homepage":31,"download_link":32,"security_score":8,"vuln_count":7,"unpatched_count":7,"last_vuln_date":33,"fetched_at":34},"flowsystems-webhook-actions","Flow Systems Webhook Actions","1.2.1","\u003Cp>Flow Systems Webhook Actions is a developer-focused WordPress webhook delivery layer designed for reliable automation workflows.\u003C\u002Fp>\n\u003Cp>Trigger HTTP webhooks from any WordPress or WooCommerce action (\u003Ccode>do_action\u003C\u002Fcode>) and dispatch them asynchronously through a persistent queue with smart retries, event identity, and full delivery visibility.\u003C\u002Fp>\n\u003Cp>Unlike basic “fire-and-forget” webhook implementations, this plugin ensures:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Delivery attempts are tracked\u003C\u002Fli>\n\u003Cli>Failures are visible\u003C\u002Fli>\n\u003Cli>Retries are automatic and intelligent\u003C\u002Fli>\n\u003Cli>Events include stable identity metadata for idempotency\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Built for production environments where losing events is not acceptable.\u003C\u002Fp>\n\u003Ch4>Typical Use Cases\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Send WooCommerce orders to n8n with retry protection\u003C\u002Fli>\n\u003Cli>Sync WordPress users to external CRMs safely\u003C\u002Fli>\n\u003Cli>Trigger backend microservices from WP hooks\u003C\u002Fli>\n\u003Cli>Send event-driven data to internal APIs\u003C\u002Fli>\n\u003Cli>Replace fragile custom \u003Ccode>wp_remote_post()\u003C\u002Fcode> integrations\u003C\u002Fli>\n\u003Cli>Build idempotent WordPress automation pipelines\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Event Identity & Idempotency\u003C\u002Fh4>\n\u003Cp>Every dispatched webhook includes:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Unique UUID (v4) per event\u003C\u002Fli>\n\u003Cli>ISO 8601 UTC timestamp\u003C\u002Fli>\n\u003Cli>Embedded \u003Ccode>event.id\u003C\u002Fcode>, \u003Ccode>event.timestamp\u003C\u002Fcode>, \u003Ccode>event.version\u003C\u002Fcode> in the payload\u003C\u002Fli>\n\u003Cli>HTTP headers: \u003Ccode>X-Event-Id\u003C\u002Fcode>, \u003Ccode>X-Event-Timestamp\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This enables downstream deduplication, idempotent workflow design, and reliable debugging across systems.\u003C\u002Fp>\n\u003Ch4>Reliable Queue & Smart Retry\u003C\u002Fh4>\n\u003Cp>Webhooks are never sent directly from request execution. Instead:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Events are stored in a persistent database queue\u003C\u002Fli>\n\u003Cli>Processed asynchronously via background jobs\u003C\u002Fli>\n\u003Cli>Dispatched in batches to avoid performance impact\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Smart retry routing:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>5xx and 429 responses \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> automatic exponential backoff retry\u003C\u002Fli>\n\u003Cli>4xx and 3xx responses \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> immediately marked as \u003Ccode>permanently_failed\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Configurable maximum retry attempts\u003C\u002Fli>\n\u003Cli>Full attempt history stored per event\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>No silent failures.\u003C\u002Fp>\n\u003Ch4>Replay Webhook Events\u003C\u002Fh4>\n\u003Cp>Webhook debugging is difficult when events cannot be reproduced.\u003C\u002Fp>\n\u003Cp>Flow Systems Webhook Actions allows you to replay any webhook event directly from the delivery logs — including successful deliveries.\u003C\u002Fp>\n\u003Cp>This makes it easy to:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Re-run automation workflows\u003C\u002Fli>\n\u003Cli>Debug external integrations\u003C\u002Fli>\n\u003Cli>Recover from temporary endpoint failures\u003C\u002Fli>\n\u003Cli>Test webhook consumers without recreating WordPress events\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Each replay uses the original payload and event metadata, ensuring consistent behavior across retries and debugging sessions.\u003C\u002Fp>\n\u003Ch4>Delivery Observability\u003C\u002Fh4>\n\u003Cp>Operational visibility built into the admin panel:\u003C\u002Fp>\n\u003Cp>Status states: \u003Ccode>pending\u003C\u002Fcode>, \u003Ccode>processing\u003C\u002Fcode>, \u003Ccode>success\u003C\u002Fcode>, \u003Ccode>failed\u003C\u002Fcode> (retrying), \u003Ccode>permanently_failed\u003C\u002Fcode>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Attempt timeline per event\u003C\u002Fli>\n\u003Cli>HTTP status codes and response bodies\u003C\u002Fli>\n\u003Cli>Inspect full request payloads\u003C\u002Fli>\n\u003Cli>Manual retry (single or bulk)\u003C\u002Fli>\n\u003Cli>Replay webhook events for debugging and testing integrations\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Filter by: event UUID, target URL, date range, status\u003C\u002Fp>\n\u003Cp>Queue health metrics:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Average attempts per event\u003C\u002Fli>\n\u003Cli>Oldest pending job age\u003C\u002Fli>\n\u003Cli>Queue stuck detection\u003C\u002Fli>\n\u003Cli>WP-Cron-only warning\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Designed as an operations console — not just a webhook sender.\u003C\u002Fp>\n\u003Ch4>Payload Mapping\u003C\u002Fh4>\n\u003Cp>Adapt outgoing JSON payloads to match any external API:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Rename fields using dot notation\u003C\u002Fli>\n\u003Cli>Restructure nested objects\u003C\u002Fli>\n\u003Cli>Exclude sensitive or unnecessary data\u003C\u002Fli>\n\u003Cli>Store example payloads for configuration\u003C\u002Fli>\n\u003Cli>Modify via \u003Ccode>fswa_payload\u003C\u002Fcode> filter\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Payloads always include stable event metadata for consistency.\u003C\u002Fp>\n\u003Ch4>Developer Friendly\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Works with any WordPress or WooCommerce action\u003C\u002Fli>\n\u003Cli>Internal REST endpoints power the admin interface\u003C\u002Fli>\n\u003Cli>Fully extensible via filters and actions\u003C\u002Fli>\n\u003Cli>Clean namespace and unique prefixes\u003C\u002Fli>\n\u003Cli>Built according to WordPress.org standards\u003C\u002Fli>\n\u003Cli>Supports system cron for improved reliability\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Why Choose Flow Systems Webhook Actions?\u003C\u002Fh4>\n\u003Cp>Most WordPress webhook setups fire once, don’t retry intelligently, don’t provide delivery visibility, and don’t expose event identity.\u003C\u002Fp>\n\u003Cp>Flow Systems Webhook Actions provides:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Persistent queue\u003C\u002Fli>\n\u003Cli>Smart retry logic\u003C\u002Fli>\n\u003Cli>Webhook replay for debugging integrations\u003C\u002Fli>\n\u003Cli>Permanent failure state handling\u003C\u002Fli>\n\u003Cli>Event UUIDs and timestamps\u003C\u002Fli>\n\u003Cli>Full delivery logging and metrics\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Built for developers who need production-grade automation reliability.\u003C\u002Fp>\n\u003Ch4>Available Filters\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Ccode>fswa_should_dispatch\u003C\u002Fcode> – Decide if a trigger should dispatch\u003C\u002Fli>\n\u003Cli>\u003Ccode>fswa_payload\u003C\u002Fcode> – Customize webhook payload\u003C\u002Fli>\n\u003Cli>\u003Ccode>fswa_headers\u003C\u002Fcode> – Add custom HTTP headers\u003C\u002Fli>\n\u003Cli>\u003Ccode>fswa_require_https\u003C\u002Fcode> – Toggle HTTPS requirement\u003C\u002Fli>\n\u003Cli>\u003Ccode>fswa_max_attempts\u003C\u002Fcode> – Configure maximum retry attempts\u003C\u002Fli>\n\u003Cli>\u003Ccode>fswa_queue_batch_size\u003C\u002Fcode> – Configure batch processing size\u003C\u002Fli>\n\u003Cli>\u003Ccode>fswa_http_timeout\u003C\u002Fcode> – Configure HTTP request timeout\u003C\u002Fli>\n\u003Cli>\u003Ccode>fswa_http_connect_timeout\u003C\u002Fcode> – Configure HTTP connect timeout\u003C\u002Fli>\n\u003Cli>\u003Ccode>fswa_http_args\u003C\u002Fcode> – Customize HTTP request arguments\u003C\u002Fli>\n\u003Cli>\u003Ccode>fswa_available_triggers\u003C\u002Fcode> – Customize available trigger list\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Available Actions\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Ccode>fswa_success\u003C\u002Fcode> – Fired after successful webhook delivery\u003C\u002Fli>\n\u003Cli>\u003Ccode>fswa_error\u003C\u002Fcode> – Fired after webhook delivery failure\u003C\u002Fli>\n\u003C\u002Ful>\n","Reliable WordPress webhooks for automation workflows with retries, delivery logs, event IDs, queue processing, and replayable webhook events.",409,2,"2026-03-07T21:21:00.000Z","6.9.4","6.0","8.0",[26,27,28,29,30],"api","automation","integration","n8n","webhook","https:\u002F\u002Fflowsystems.pl\u002Fwordpress-webhook-actions","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fflowsystems-webhook-actions.1.2.1.zip",null,"2026-03-15T15:16:48.613Z"]