IvyForms is a WordPress form builder for turning submissions into structured workflows. Create contact forms, applications, registrations, surveys, feedback forms, and multi-step flows with a clean drag-and-drop builder. Then manage entries, analyze responses, apply conditional logic, and connect data to tools like wpDataTables, Amelia, Mailchimp, and webhooks so every response can move work forward.
How does the conditional logic actually behave across multi-step flows, does each step have its own rules or is it all evaluated globally when someone hits submit?
IvyForms
@yaar89286282857 Great question!
In multi-step forms, validation is performed on each step, not only when the user reaches the final submit.
Conditional logic that controls whether a field is displayed or hidden also works within the specific step where the field exists. For example, if you want a conditional field to appear immediately on the first page based on the user's answer, that is fully supported.
If that conditional field is required, the user will see a validation error before moving to the next step if they haven't completed it. The error message will guide them to complete the required fields on the current step before continuing.
So the logic and validation are handled dynamically throughout the form flow, not only at submission.
Congrats on the launch! WordPress definitely has plenty of form builders, but focusing heavily on real workflows and complex backend actions rather than just basic data collection sounds like a massive timesaver. How deep do the native integrations go for handling multi-step logic right after a form submission?
IvyForms
@adamkamaneh Thanks, glad that resonates! Honestly, right now the native integrations are still single-action (Mailchimp, webhooks), with Zapier support coming very soon. So true multi-step chaining right now happens either through webhooks, Zapier, or directly in code via our after_submission hook. A native visual builder for chaining/branching multiple actions post-submission is exactly the kind of thing on our radar as the "workflow" side matures. Curious to know, are you picturing something like "update CRM, then conditionally alert a channel, then create a task," or a different chain? Would help us think through what to prioritize first.
the deep integration with wpDataTables and Amelia is clearly the selling point, but it makes me wonder about the flip side: if a site outgrows WordPress entirely down the line, how portable is the structured data and workflow logic? like can you export the conditional logic rules and calculated fields in some reusable format, or is that value basically locked into staying on WP once you've built it out
Trafft
@galdayan thank you for your support! And it's a great question - so far we didn't build the out-of-wp version - but the way we strore the data would allow it to be "portable" if necessary.
@alexander_gilmanov fair enough, appreciate the honesty that it's not built yet rather than pretending it's solved. "the way we store the data" being portable in theory is different from an actual export button though, that gap is usually where lock-in quietly lives. would be a good thing to firm up before teams build heavy conditional logic on top of it
Trafft
@galdayan valid feedback - and thank you for your input. Out of curiosity/for future reference, do you have a preference, which CMS or technology you use if you need to migrate a website away from WP?
Trafft
@galdayan valid feedback - and thank you for your input. Out of curiosity/for future reference, do you have a preference, which CMS or technology you use if you need to migrate a website away from WP?
Looks promising.
Are there any plans for payment integrations (Stripe, PayPal, etc.)? If so, is there a timeframe for release?
Are there plans for fron-end post submission integration?
IvyForms
@aguilar1181 Thanks for asking! Yes, we're actively working on payment integrations. Square is currently in development, while Stripe and PayPal are next. Which one comes first will depend on customer demand.
Front-end post and user submission forms are also planned, and we'll prioritize them based on the workflows our users tell us they need most.
Most form builders stop at the submission. You're explicitly building past that point, into what happens with the data next. That's a bigger scope than a form builder usually takes on. Where's the line for you between what IvyForms handles natively and what gets handed off to Zapier or a webhook? That boundary probably says more about the product's direction than the feature list does.
Congrats on the launch!
IvyForms
@jared_salois Thank you! That's exactly how we see it. 😊
Our goal is to make everything that's core to building forms and working with your data a native part of IvyForms.
For integrations, our approach is to build native connections with the services our users rely on most, while webhooks and platforms like Zapier remain the bridge to virtually any other tool or custom workflow. That way, you get the best native experience where it matters most, without limiting what's possible.
the "submissions into workflows" framing is what separates this from a basic form builder. most wordpress form plugins stop at collecting data and then you're manually moving entries into whatever system actually needs them. curious how deep the workflow side goes, can it trigger external actions like sending to a CRM or slack on submission, or is the workflow management mostly within the plugin itself?
IvyForms
@shubham4real Great question! Our goal is to go beyond simply collecting submissions. IvyForms already supports webhooks, so you can send data to thousands of apps and CRMs that support them.
We also have a direct Mailchimp integration, with Zapier and Google Sheets integrations rolling out by the end of this week.
It will be available and REST API for developers who want to build custom workflows. And yes, Slack is already in progress and will be available very soon as a native integration.
If you have a specific workflow in mind, we'd genuinely love to hear it. Real customer use cases help shape what we build next.
IvyForms
@ridhwikvinod Thank you so much! We're excited to be here!
Great question. IvyForms currently supports Google reCAPTCHA, hCaptcha, and Cloudflare Turnstile, so you can choose the spam protection solution that best fits your website. We also provide a GDPR consent field for collecting user consent when needed.
Conditional logic serves a different purpose, it helps create dynamic forms and workflows, rather than filtering spam before submissions reach your entries.
Thanks for bringing this up, and thanks for your support!