Cascade Forge – No-Code Workflow Automation & Webhooks
by avakodeforge 0 (0 reviews)

Cascade Forge – No-Code Workflow Automation & Webhooks

No-code workflow automation for WordPress and WooCommerce: visual flow builder, triggers, outbound webhooks, retries and a failed-run queue.

Cascade Forge ranks #54,294 among WordPress.org plugins with 0+ active installations, is #10,113 of 14,124 in the E-commerce category, and was last updated Oct 30, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1.4
v1.8.10 Current Version v1.8.10
Updated 3 days ago Last Update on 30 Oct, 2026
Refreshed 2 days ago Last Refreshed on
#10,113 of 14,124 in E-commerce Downloads -20% this week Actively maintained
View on WordPress.org
Rank
#54,294
— No change
Active Installs
0+
— No change
KW Avg Position
N/A
— No change
Downloads
196
+11 today
Support Resolved
0%
— No change
Rating
0%
Review 0 out of 5
0 (0 reviews)

Next Milestone 10

Total Progress 40%
0+ 10+
26,726
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

  • Exact install estimates within tiers
  • Track install growth over time
  • Milestone progress predictions
Upgrade to Pro
Need 6 more installs to reach 10+

Rank Changes

54,153 58,443 62,732 67,021 71,311 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026 02-11-2026
53,791 58,865 63,940 69,014 74,088 18-10-2026 19-10-2026 20-10-2026 21-10-2026 22-10-2026 23-10-2026 24-10-2026 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026 02-11-2026
Current #54,294
Change
Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Active Installs 0,000,000+
Growth +0.0%
Peak 0,000,000

Downloads Growth

0 10 20 30 40 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026 02-11-2026
0 10 20 30 40 18-10-2026 19-10-2026 20-10-2026 21-10-2026 22-10-2026 23-10-2026 24-10-2026 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026 02-11-2026
Downloads
Growth
Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

0.0
0 reviews
Overall 0%
5
0 (0%)
4
0 (0%)
3
0 (0%)
2
0 (0%)
1
0 (0%)

Frequently Asked Questions

Common questions about Cascade Forge – No-Code Workflow Automation & Webhooks

No. The free plugin runs entirely on your own server. See "External services" above for exactly what this download does and does not contact.
Pro features ship in a separate "Cascade Forge Pro" add-on. Install this free plugin first, then add Pro from https://avakode.com.
As many as you like. There is no cap on flows, active or draft, and none on runs. How long run history is kept is a setting (Settings → Log retention), not a limit.
Every WordPress and WooCommerce trigger, the sibling events those plugins publish from their own free cores, the "a run was dead-lettered" trigger, and the nine actions listed above — including the outbound webhook. Nothing in the free plugin is switched off waiting for a licence; the Pro catalogue is a separate download and simply is not there until you install it.
Yes. Cascade Forge declares itself compatible with High-Performance Order Storage, and it reads and writes orders only through WooCommerce's own order functions, so it does not depend on whether orders are kept in posts or in WooCommerce's order tables. Two things are worth knowing when a flow works on orders. The "Update post meta" step sets the meta on the order itself when the ID you give it is an order's. The "Post meta updated" trigger listens to WordPress post meta, and under High-Performance Order Storage an order's meta is not post meta, so it is not a reliable trigger for orders (with compatibility mode on, WooCommerce may still copy order meta to posts); for orders, use the WooCommerce triggers: order created, order status changed, payment complete and refund created.
No. Every trigger and every step renders a form built from the parameters it declares, and conditions are rows: field, operator, value. The JSON textareas survive under an "Advanced" toggle for anyone who wants them. If a flow contains something the form cannot draw without risking your data — a nested condition group, a parameter no schema knows about, an OR group on a site without the Pro add-on — that panel opens as JSON with a note saying why, rather than being redrawn and silently truncated. Without JavaScript the screen falls back to the plain editor.
They ship with the plugin as data, not as model output: 20 flows whose every trigger and action is a real id in Cascade Forge's catalogue, checked by the test suite against the live registries. Some of them lean on ids that belong to the Pro add-on or to a sibling plugin, so a recipe this site cannot run yet says which plugin it needs instead of offering a button that would fail. Importing one creates a draft — it cannot switch itself on — and any credential a step needs is left blank on purpose so you fill it in and read the flow before turning it on. Recipes cost nothing.
The run is kept. The Failed view on the Runs screen shows the step it stopped on, the error, and a preview of the payload it was carrying with anything token-shaped blanked out. Retry writes a new run that starts at that step with the original payload, so the steps that already succeeded do not run twice. It is refused if you have edited the flow since the failure, because the step it stopped on is then no longer that step; if the step's own connection is already known to be access-revoked, the button reads "Fix access, then resume" instead, because retrying now would only fail the same way again; and if the run stopped not knowing whether its last step reached its target, retrying could repeat that exact request, so the free screen explains that instead of offering a retry — start a new run of the flow, or resolve it from the Pro add-on's Inbox once you know what actually happened. An incident already resolved that way is not retried either. If you would rather be told than go looking, the "a run was dead-lettered" trigger lets one flow react to another giving up.
With the Pro add-on. The "Wait for approval" step pauses the run and e-mails one approver an Approve link and a Reject link; the decision is recorded and the run continues from exactly where it paused, with the decision, who made it and when available to every later step. Only a hash of the link's token is stored, a second click cannot change the answer, and you decide in advance what happens if nobody replies before the timeout — rejection is the default.
No. The only thing in Cascade Forge that spends Forge credits is the Pro add-on's AI recipe generator, at 3 credits per draft, and the button says so before you press it.

Sign In / Register

You need to sign in or register to use this feature.