Send MetForm leads from Elementor pages to monday.com

Check how your form was built

Start here, because one kind of MetForm form never reaches monday.com, and nothing tells you.

MetForm has two builders. Forms built in the Elementor editor work. MetForm 4.3.3 added MetForm Builder, which works without Elementor, and the plugin can’t read those forms. It reads MetForm’s fields from Elementor’s form data, and those forms don’t have any.

1. Form built in MetForm Builder
2. Listed in Form ID, with no fields
3. Visitor sees the thank-you message
4. Nothing reaches monday.com

We tested this on MetForm 4.3.4 with a form made by MetForm’s own code using that builder. The form appeared in the list, and its field list came back empty. On a real submission the visitor saw the thank-you message and MetForm stored the entry, but the plugin sent nothing and showed no error.

So a form can look healthy from every side. To check yours:

1. Open a template and pick the form in Form ID.
2. Click Data.
3. If none of the form’s fields are listed, rebuild the form with Elementor as the builder.

Give every field its own Name

In MetForm, Label is what the visitor reads and Name is what identifies the field. The plugin uses Name as the field’s id, so two fields that share one are the same field as far as anything downstream can tell.

We built a form with two fields named alike and typed apples in the first and oranges in the second. The browser posted only oranges, and MetForm stored only oranges. The plugin then sent two rows with the same id, both saying oranges. The answer apples was gone before the plugin saw it, so no setting here can bring it back.

A new field’s Name starts as its type, such as mf-text. So two Text fields can collide if nobody renames them. It’s an easy mistake on a landing page, where you copy a field and change only the label.

Before you map a form, click each field in the Elementor editor and check that its Name is different from the others. Use names that describe the answer, such as lead-email.

What the test form sent

This is a real test submission through the form, on MetForm 4.3.4 with Elementor 4.3.6 and connector 1.3.0. The table shows what left WordPress. The last column is our suggestion.

MetForm stored the choice as pricing, and the plugin sent the label, so Status labels read well. For date, number, consent and checkbox fields, see Supported WordPress form plugins.

A second test filled in Email only. Name and Interested in arrived as empty text, because Name wasn’t required on this form. An empty name means a placeholder item name, so make Name required, or map Email to ✏️ Name instead.

Run one form per landing page

The plugin has no field to tell you which page a lead came from, and MetForm has no hidden field it sends. The simple answer is one form per campaign, each with its own automation and its own group:

Landing page leads

Spring pricing page

Name	Email	Interested in
Elif Kaya	elif@example.com	Pricing call

Connect your site once. Then, for each landing page:

1. Give the form a title that names the campaign. Form ID shows titles only.
2. Pick the form in Form ID.
3. Click Group/Item and pick that campaign’s group.
4. Click Data and map the fields.
5. Create the automation, then submit a test entry from the live page.

Which forms appear in Form ID

The list depends on the form’s WordPress status. We checked each one:

So you can build the automation while a landing page is still a draft. It also means an old draft can sit next to the live form, and the list shows titles only. Give retired forms a title that says so, or trash them.

If you’re on Elementor Pro’s Form widget

MetForm is one of three routes for forms on Elementor pages. Elementor Pro’s own Form widget isn’t supported, so read Elementor forms and monday.com before you rebuild anything. It covers when a webhook tool is the better choice. For everything else, read the WordPress forms to monday.com guide.