Drip
Two-month digests that keep circling the same theme: get your data out of Drip and into your own stack.
A side-by-side editorial comparison of Formidable Forms and Pushwoosh — release velocity, themes, recent moves, and the top alternatives to consider.
The forms plugin just opened its data to AI agents through an MCP adapter.
Formidable Forms ships as a core plugin plus a fleet of separately versioned add-ons — PDFs, Visual Views, Digital Signature, Export View, Forms API — each getting its own small release. Most of that stream is bug fixes and hardening, including two security passes in the last month credited in part to Wordfence. The exception is Forms API v2.0, which adds support for the WordPress Abilities API and an MCP adapter alongside tighter API key validation.
Pushwoosh journeys can now read what a webhook says back and act on it mid-run.
The current release batch is broad but coherent. Journeys gained the ability to consume webhook response data and use returned values to personalize later steps in the same run. Messaging coverage evened out across channels, with PW_SMSSent and PW_WhatsAppSent events matching what email already emitted, and one-time WhatsApp sends no longer requiring a journey. On the web side, subscription forms can be dropped into any popup as lead capture, form field labels are editable without code, and the popup editor and targeting both got more room to work.
Formidable Forms ships as a core plugin plus a fleet of separately versioned add-ons — PDFs, Visual Views, Digital Signature, Export View, Forms API — each getting its own small release. Most of that stream is bug fixes and hardening, including two security passes in the last month credited in part to Wordfence. The exception is Forms API v2.0, which adds support for the WordPress Abilities API and an MCP adapter alongside tighter API key validation.
Two threads are running at once. The first is a security tightening pass across the add-ons: constant-time API key comparison, restrictions on where a key can be used, and validation that signature deletion only touches signature files on the active entry. The second, newer thread is making form data reachable by software rather than only by humans — the gated-content actions added to PDFs and Visual Views, and now an MCP adapter on the API. The add-ons are converging on a shared access-control model rather than each solving it locally.
Expect the MCP surface to widen from the API add-on into the entry and view add-ons, since those already gained gated-content actions and hold the data an agent would want to read.
The current release batch is broad but coherent. Journeys gained the ability to consume webhook response data and use returned values to personalize later steps in the same run. Messaging coverage evened out across channels, with PW_SMSSent and PW_WhatsAppSent events matching what email already emitted, and one-time WhatsApp sends no longer requiring a journey. On the web side, subscription forms can be dropped into any popup as lead capture, form field labels are editable without code, and the popup editor and targeting both got more room to work.
Two things are being closed at once. The channel gap is narrowing — SMS and WhatsApp are being given the same event surface and standalone send path email has had, which makes them first-class for segmentation and triggering rather than journey-only endpoints. The bigger change is that journeys are becoming stateful against the outside world: a webhook step that can return a value into the run turns the journey builder from a sequencer into something closer to orchestration.
Now that webhook responses can feed a running journey, the natural extension is branching on those values and handling failure paths when the external call does not answer as expected. Expect the remaining email-only capabilities to keep arriving for SMS and WhatsApp until channel parity is complete.
Other Mkt Auto products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Formidable Forms or Pushwoosh.
Two-month digests that keep circling the same theme: get your data out of Drip and into your own stack.
A security-hardening train: nine advisories across six patch releases, no feature work in sight.
Three release lines running in parallel, all of them shipping nothing but fixes this week
OpnForm is turning its V2 platform into an automation surface, one integration at a time.
Zoho Social opens its management surface to AI assistants via MCP.
AWeber is moving the console out of the browser and into the chat window
See all Formidable Forms alternatives → · See all Pushwoosh alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Formidable Forms and Pushwoosh are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Formidable Forms and Pushwoosh are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Mkt Auto products to evaluate alongside.
Top Formidable Forms alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Formidable Forms alternatives" section above for the current picks, or visit /alternatives/formidable-forms for the full list with editorial commentary on each.
Top Pushwoosh alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Pushwoosh alternatives" section above for the current picks, or visit /alternatives/pushwoosh for the full list with editorial commentary on each.