Flowlu

Flowlu is an all-in-one business-management platform with built-in CRM, project management, finance, and knowledge base. Advanced Form Integration sends form submissions to Flowlu as new records: any combination of Organization, Contact, Opportunity, Case, or Task in a single submission.

What you’ll need

• An active Flowlu account.
• Your Flowlu subdomain (e.g., yourcompany from yourcompany.flowlu.com).
• A Flowlu API Key with all-apps access (Portal Settings → API Settings).
• The Advanced Form Integration plugin installed and activated.

Get your Flowlu API credentials

1. Log in to your Flowlu account.
2. Navigate to Portal Settings → API Settings.
3. Create a new API key, ensuring access to all apps is enabled.
4. Copy the API Key.
5. Note your subdomain: the prefix in your Flowlu URL.

Connect Flowlu to AFI

1. In WordPress, go to AFI → Settings.
2. Enable Flowlu and click Save Changes.
3. Open the Flowlu tab.
4. Enter the subdomain and API Key.
5. Click Save Changes.

Create the integration

1. Go to AFI → Add New.
2. Configure the trigger.
3. In Action → Platform, select Flowlu.
4. In Task, choose Add Records.
5. Pick the Owner: the Flowlu user who will own the created records.
6. Tick one or more record types:

• Organization
• Contact
• Opportunity
• Case
• Task

1. Click Get Fields to load the field schemas for each selected type.
2. Map the form fields. Common fields:

• Organization: Name, Email, Phone, Address, Website, Industry.
• Contact: First Name, Last Name, Email, Phone, Company.
• Opportunity: Name, Budget, Pipeline Stage, Source.
• Case and Task: Title, Description, Assignee, Due Date.

1. Optional: configure Conditional Logic.
2. Click Save Integration.

Tasks supported

Add Records

Creates one or more linked records in Flowlu in a single API call. Useful for “Lead inquiry → Organization + Contact + Opportunity” workflows where the entire CRM hierarchy needs to be created at once.

Select-type fields (industries, pipeline stages) auto-load their valid options from your Flowlu account.

Conditional logic example

Create an Opportunity (in addition to the Contact) only when the form’s interested_in_buying field is “yes”. Information-only inquiries create just the Contact via a separate integration.

Troubleshooting

Integration doesn’t fire

Open AFI → Log and find the most recent entry. The log shows the request payload sent to Flowlu and the response received, usually pointing straight at the cause.

“Authentication failed”

Flowlu requires both subdomain and API Key. Confirm the subdomain has no protocol or trailing slash, just the prefix (e.g., acmecorp).

Required field missing

Each record type has its own required-field rules. If you tick “Organization” but don’t map a Name, the entire request fails. Either map the required field or untick that record type.

Related docs

• Send Contact Form 7 submissions to Flowlu
• Send WPForms submissions to Flowlu
• Send Gravity Forms submissions to Flowlu
• Conditional Logic