Create new Brilliant Directories users from new FluentForms form entries

Each new Fluent Forms entry on your WordPress site creates a user record in your Brilliant Directories website, so people who apply or sign up through your form become directory members without manual entry.

Fluent Forms

Brilliant Directories

Download this workflow Browse more workflows

2 steps Setup ~5 min Used on 1.3k sites Free to import

The Create new Brilliant Directories users from new FluentForms form entries workflow on the FlowMattic canvas, with 2 steps across Fluent Forms, Brilliant Directories — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

Directory owners often collect applications on their main WordPress site, then rebuild each one as a member in Brilliant Directories. That copying is slow when sign-ups arrive in batches, and it is easy to mistype an email. This workflow takes each Fluent Forms submission and creates the user in Brilliant Directories for you.

The Fluent Forms trigger starts a run for every new entry a visitor submits. The answers in the entry become values you can map. Brilliant Directories then runs Create User, which adds a new user record to your directory website's database using the values you map, typically the applicant's name and email.

Every submission creates a user, because no step reviews the entry first. If you approve members by hand, add a check before the Brilliant Directories step. Create User always adds a new record, so test what your directory does with an email it already holds. Task History records each run and Brilliant Directories' response.

Professional association sign-ups

Members apply through a Fluent Forms form on the association's WordPress site, and each applicant gets a user record in the Brilliant Directories member directory.

Local business directory listings

Shop owners fill in a listing request form, and a Brilliant Directories user is created for them to complete their listing.

Moving sign-ups off a legacy site

While you move to Brilliant Directories, the old site's Fluent Forms sign-up form keeps working and creates each new member in the new directory.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
Fluent Forms New Form Submission
Fires when a new Fluent Forms submission is received on your WordPress site. Each answer is passed on so you can map it into the Brilliant Directories step.
Step 2Action
Brilliant Directories Create User
Adds a member to the database behind your Brilliant Directories site as a new user record. Map the form's email and name answers, and any others the directory needs, then connect your Brilliant Directories account.

What you need

FlowMatticCore
Fluent Forms PluginPlugin
Brilliant Directories AccountAccount

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

If you vet members first, put a Human in the Loop step before Brilliant Directories and set its timeout action to End Workflow, so no user is created without approval.
When your site has several Fluent Forms forms, add a Filter after the trigger that continues only for the directory sign-up form.
Submit a test entry after import, then check the new user in Brilliant Directories to confirm each mapped answer landed where you expected.

Questions about this workflow

What if the Fluent Forms applicant already has a Brilliant Directories account?

Create User adds a new record and doesn't search for an existing one. Brilliant Directories may reject the repeat email or create a second user. Test with a known address and check Task History.

Will Fluent Forms keep its own copy of each directory application?

Yes. The entry stays in Fluent Forms like any other. The workflow only reads the submission after it is received and passes its answers to Brilliant Directories.

Can a rejected applicant be kept out of Brilliant Directories?

Not as imported, since every entry creates a user. Add a Human in the Loop step with the timeout action set to End Workflow; a rejection ends the run before the user is created.