Description
What Happens After Someone Fills Out Your Brizy Form?
For most WordPress site owners, the answer is: not much. A submission lands in an inbox or a database table, and then it just sits there. That’s a missed opportunity, especially if you’ve built your site with Brizy and put real effort into designing forms that visitors actually want to complete. AutomatorWP – Brizy exists to close that gap. It connects the forms built with the Brizy website builder to WordPress automation workflows, so every submission can trigger something meaningful instead of disappearing into a database.
Think about what a form submission actually represents. Someone typed their name, answered a question, maybe selected an option from a dropdown. That’s a signal. It tells you something about intent, interest, or need. Without automation, that signal goes nowhere. With AutomatorWP – Brizy, it becomes the starting point for a workflow: award points, send data into a CRM step, trigger a badge, kick off an email sequence, or feed the submitted values into another action entirely. The plugin turns passive form data into an active part of your site’s logic.
How AutomatorWP – Brizy Solves the Disconnect
AutomatorWP – Brizy works as an add-on to the AutomatorWP automation framework, and its entire job is translating Brizy form activity into triggers that the rest of your automation stack can react to. Instead of writing custom code to hook into form submissions, you set conditions visually. A user submits a form, and something happens. A guest submits a specific field value, and something else happens. The logic lives in the AutomatorWP interface, not in a functions.php file.
What makes this particularly useful is the distinction between logged-in users and anonymous visitors. Plenty of forms on a typical Brizy site get filled out by people who haven’t created an account yet: contact forms, lead magnets, quiz entries, waitlists. AutomatorWP – Brizy treats these as first-class citizens with their own dedicated triggers, so you’re not forced to require registration just to capture automation-worthy data. That’s a meaningful distinction most generic form-to-automation setups gloss over.
The other piece of the puzzle is field-level granularity. Rather than only reacting to “a form was submitted,” you can build logic around a specific field value. Someone selects “Enterprise” from a dropdown instead of “Starter”? That’s a different trigger path. Someone types a particular keyword into a text field? Same idea. This lets you branch your automations based on what people actually said, not just the fact that they said something.
Core Features
- User submits a form — fires an automation trigger whenever a logged-in user completes any Brizy-built form on your site, giving you a general-purpose hook for post-submission logic.
- User submits a specific field value on a form — narrows the trigger to a particular answer, selection, or entry within a form, so you can build conditional paths based on what the user actually submitted.
- Guest submits a form — extends the same triggering logic to anonymous visitors, useful for lead capture, contact forms, and any front-facing form that doesn’t require login.
- Guest submits a specific field value on a form — combines the anonymous trigger with field-level precision, letting you react to specific guest responses without requiring account creation.
- Field value tag — pulls any submitted form field value into your automation actions, so you can pass real submission data (names, choices, comments) directly into emails, notifications, points systems, or other connected plugins.
Taken together, these five capabilities cover the two questions that matter most in form automation: did someone submit something, and what exactly did they submit? The plugin doesn’t try to reinvent form building — Brizy already handles that side well. Instead, it focuses entirely on what happens the moment after a submission lands, which is where most WordPress sites leave value on the table.
Practical Applications
A membership site built with Brizy might use the user-submission trigger to award points or badges the moment a member completes a profile-update form, reinforcing engagement without manual review. Combine that with the field value tag, and you can personalize a follow-up notification with the member’s actual answers instead of a generic confirmation message.
A lead-generation site aimed at guests can use the anonymous triggers to build a nurture sequence. A visitor submits a contact form, the guest trigger fires, and the submitted field values — name, company size, area of interest — get passed into an email or CRM step so the follow-up feels tailored rather than templated. Because this works for non-logged-in visitors, you don’t lose the ability to automate simply because someone hasn’t registered an account.
Course creators and coaching businesses often use field-specific triggers to route people based on their answers. If a student selects “Beginner” versus “Advanced” on an intake form, AutomatorWP – Brizy can treat those as distinct events, feeding different onboarding paths, tags, or notifications depending on the response. Agencies managing several client installs will also appreciate that the plugin, distributed under GPL licensing, fits cleanly into workflows where multiple sites need consistent automation logic without licensing friction between installs.
Event and community sites can use the guest field-value trigger for RSVP forms — someone selects “attending” versus “not attending,” and that single answer can determine whether they get added to a reminder sequence, a waitlist, or a follow-up survey. None of this requires custom development. It’s condition-and-action logic, built through the AutomatorWP interface, powered by data Brizy’s forms are already collecting.
Compatibility and Requirements
AutomatorWP – Brizy is currently at version 1.0.0 and requires WordPress version 4.4 or higher. As an add-on, it depends on the core AutomatorWP plugin being active alongside a Brizy-built site, since it specifically extends AutomatorWP’s trigger and tag system to recognize Brizy form activity. Site owners running older WordPress installs should confirm their version meets the 4.4 minimum before activating.
Frequently Asked Questions
How do I automate something when a Brizy form is submitted?
Create an automation in AutomatorWP and select the “User submits a form” or “Guest submits a form” trigger, depending on whether the submitter is logged in. Once that trigger is attached to a Brizy form, any completed submission fires the automation, which can then run whatever actions you’ve connected to it — notifications, points, tags, or third-party plugin actions.
Can I trigger different actions based on what someone actually typed or selected?
Yes. The “specific field value” triggers, available for both logged-in users and guests, let you set a condition tied to an exact field response. This means a dropdown selection or a typed keyword can send the automation down a different path than a generic submission would.
How do I find out which fields and sub-fields are available from a form submission?
The most reliable way is to build a test automation using the “User submits a form” trigger, activate it, and then submit the form yourself to generate a log entry. Inside AutomatorWP’s Logs section, open that trigger entry and look at the “Fields Submitted” data within the Log Data box — it lists every field and sub-field that was captured, which you can then reference in your actual automation.
Do I need to require user registration to use these triggers?
No. AutomatorWP – Brizy includes dedicated anonymous triggers — “Guest submits a form” and “Guest submits a specific field value on a form” — specifically so you can automate around visitors who never create an account. This is particularly useful for contact forms, lead capture, and public-facing forms where requiring login would hurt conversions.
Can submitted form data be reused inside the automation itself?
Yes, through the field value tag. This tag lets you pull any submitted field’s value and insert it directly into an action, such as an email body, a notification message, or a value passed to another connected plugin, so your automations reflect the actual content someone submitted rather than static, generic text.
