When new form submission is received in AidaForm, add a new contact in FluentCRM

When someone submits one of your AidaForm forms, FlowMattic adds them to FluentCRM as a contact, or updates their existing contact if the email address is already there, so your WordPress CRM holds every respondent.

AidaForm

FluentCRM

Download this workflow Browse more workflows

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

The When new form submission is received in AidaForm, add a new contact in FluentCRM workflow on the FlowMattic canvas, with 2 steps across AidaForm, FluentCRM — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

AidaForm collects responses on its own platform, while FluentCRM keeps your contacts inside WordPress. Without a link between them, every respondent has to be exported and imported before you can email them. This workflow sends each AidaForm response straight into FluentCRM.

The AidaForm trigger, New Response, fires when a form is submitted, and its answers become data you can map. The FluentCRM step uses Create or Update Contact, which matches on email address. A new email creates a contact; an email FluentCRM already holds updates that contact instead of adding a duplicate.

Every response reaches FluentCRM because nothing filters them. Make the email question required in AidaForm so each response has an address to match on. Task History shows each run and what FluentCRM returned.

Webinar or event registration

Registrants fill in an AidaForm form and appear in FluentCRM, ready for reminder emails sent from your WordPress site.

Customer feedback with follow-up

Customers answer an AidaForm feedback form. Their FluentCRM contact is updated with the details you map, so you can email them about their answers.

Quote requests for a service business

Prospects ask for a quote on an AidaForm form embedded in a landing page, and become FluentCRM contacts your team can send a proposal to.

How this workflow runs

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

Step 1Trigger
AidaForm New Response
Starts each time someone sends in an AidaForm response. The respondent's answers are passed on to be mapped into the FluentCRM contact.
Step 2Action
FluentCRM Create or Update Contact
Creates a FluentCRM contact from the response, or updates the existing contact with the same email address. Map the email answer and any name or phone answers to the contact.

What you need

FlowMatticCore
AidaForm AccountAccount
FluentCRM PluginPlugin

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.

Add a Filter after the trigger that continues only when the consent question is answered yes, so only people who agreed to hear from you are added to FluentCRM.
After the FluentCRM step, add FluentCRM's Add Tags to Contact action to tag respondents with the form they came from. The contact exists by then, so the tag can be applied.
Submit one test response after import, then check the captured answers in the FluentCRM step before mapping them to contact fields.

Questions about this workflow

What happens when an AidaForm respondent is already in FluentCRM?

The step is Create or Update Contact, which matches on email address. The existing contact is updated with the mapped answers rather than duplicated.

Does FluentCRM need to be on the same site as FlowMattic for AidaForm responses?

Yes. FluentCRM is a WordPress plugin, and the step adds contacts on the site where FlowMattic is installed.

What if a respondent leaves the AidaForm email question blank?

FluentCRM matches and creates contacts by email address, so the step has nothing to work with. Task History shows the error for that run. Make the email question required to avoid it.