Send Formidable Forms quote requests to monday.com

The quote board

A quote request needs three things on the board: who’s asking, how much they want and which package. This guide sends a Formidable Forms quote form to a board like this one:

Quote requests

New quotes

Name	Email	Quantity	Package	Add-ons
Hana Okafor	hana@example.com	12	growth	Priority support, Extra training
Ravi Shah	ravi@example.com	0	starter

Look at that first row. The two choice fields don’t match, and that’s the first thing to fix.

What the test form sent

We sent a real submission through this form on Formidable Forms 7.0, with connector 1.3.0. The table shows what left WordPress. The last column is our suggestion.

Why Package and Add-ons disagree

Both fields on the test form used separate values, so each choice had a label and a stored value. The plugin treats them differently:

The plugin turns stored values back into labels for checkboxes and multi-select dropdowns only. A single-choice dropdown goes through as it’s stored. Radio Buttons take the same path.

This changes your board in three ways:

• Status and Dropdown columns. The answer becomes the label, and a label that doesn’t exist yet is created. Your board gets growth, and a form sending “Growth plan” would add a second label for the same package.
• Renaming doesn’t stick. The app asks monday.com to create any label it can’t find. If you rename growth on the board, the next growth can create that label again.
• Conditions. A text rule compares what arrived, so Text has to be growth, not “Growth plan”.

The fix is on the form. Before you map anything, do one of these:

1. Turn off Use separate values on the field, so the label is what’s stored.
2. Keep it on, and set each stored value to the text you want on the board.

Check first whether anything else reads those values, such as a calculation.

Formidable’s docs call Use separate values a premium feature, and the free plugin shows the checkbox locked. Our test ran on the free plugin only because the form was built through its code. If you’re on the free plugin, you shouldn’t see this difference.

Handle a blank Quantity

A second submission left Quantity empty, and it arrived as 0. So a Numbers column shows 0, not an empty cell, and a typed 0 looks the same. For a quote, read a 0 as “not given”, or make the field required.

The good news is that a blank can’t trigger a “large order” rule, because 0 never passes a greater than check. That makes Quantity safe for routing big requests to a separate group:

Set Question to Quantity, Condition to greater than and Number to 10, then pick a group such as Large orders. A condition template only creates an item when the check passes, so smaller requests need their own automation with less than or equal to 10. A blank Quantity lands in that second one, as 0. See Run an automation only when an answer matches.

Map the quote form

With your site connected, pick the form in Form ID, then click Data:

Use the Name (Full Name) row for the item name. It’s built from the first and last boxes, so you don’t have to choose a part.

What won’t reach the board

• The HTML note. “We reply within two working days” is on the form but not in the mapping. A real test confirmed that HTML fields are skipped.
• The sample form. Formidable creates a form called Contact Us on activation, and it appears in Form ID next to yours.

For every other field type, see Supported WordPress form plugins. Zapier and Integrately also connect Formidable Forms to monday.com. Zapier alternatives compares the routes, and the WordPress forms to monday.com guide covers everything else.