Advertising disclosure: this page contains no advertising (affiliate) links. If we add any, each will be marked next to the link and this notice will be updated. Where we rely on vendor documentation or have not tested something, the text says so.

What a HubSpot Free form actually does with a client intake, measured over two runs

Tested 2026-08-22 and 2026-08-23 on a HubSpot Free portal, with no automation tool attached. We built a six field intake form in HubSpot's own form builder (name, email, company, service interest, budget range, message), published it as a standalone page, and submitted a scripted set of cases twice on separate days. Every result below was read back through HubSpot's API and the receiving inbox. The full case by case record is on the evidence record for this pack.

This page answers one question: if you are already on HubSpot Free, what do you get from its own form, and what do you not get. The comparison against a form plus automation stack is on the decision page.

What it does, measured

• A new email address becomes a contact in about one second. Measured 1.03 s in run 1 and 1.18 s in run 2, from submit to the record's creation time. The contact carries the source (form), the form name as its first conversion, and lifecycle stage lead. All six fields land on the record, including the two dropdowns.
• A repeat submission of the same email updates the same contact. We resubmitted 123 seconds later in run 1 and 73 seconds later in run 2 with a changed company, service interest and budget. Both times the same record was updated, no second contact appeared, and the contact's form submission counter went from 1 to 2.
• Special characters survive. Søren Ø'Brien-Kärkkäinen at Åland & Partners Oy in run 1 and Åsa Ø'Neill-Väisänen at Öresund & Kumppanit Oy in run 2 arrived intact.
• The form blocks two bad inputs before anything is created. A malformed address (user@domain) produced "Email must be formatted correctly" and no record. An empty required field produced a field level and a form level error and no record. Both runs.
• You get an email per accepted submission. New addresses produce a "new submission" notification, repeat addresses a "contact reconversion" notification, to the address configured on the form.
• Cost: nothing. No automation operations are consumed, because there is no automation layer, so there is no operations budget to size. We did not test whether HubSpot itself limits form submission volume on the free plan.

What it does not do, measured

• No deal is created. After both runs, a search for deals created on the test days returned only one deal, and that came from an unrelated automated test, not from the form. If your intake needs a deal record in a pipeline, the free form alone does not produce it. HubSpot's own documentation lists record creation as a workflow action that is available to paid users (help page captured 2026-08-21, copy in the evidence pack).
• We configured no acknowledgement to the lead. This is our own limit, not a proven product one. HubSpot Free does offer one simple workflow per form called "Send an email after form submission" (documentation captured 2026-08-21, and the option was present in our form editor). We did not use it, for two reasons we hit while setting it up: the email is a marketing email, so it is sent only to contacts marked as marketing contacts, and saving it requires an email footer containing a physical postal address, which this lab does not publish. So on this page, "no acknowledgement" means "not configured by us", not "impossible on Free". If you are willing to publish a postal address and manage marketing contacts, test that path yourself before deciding.

Two behaviours worth knowing before you rely on the record

Two submissions arriving at almost the same moment produce one contact, and the counter shows one. We submitted the same new address twice in parallel, 106 milliseconds apart in run 1 and 235 milliseconds apart in run 2. Both runs produced exactly one contact, which is the good news. But both runs also produced two notification emails (one "new submission", one "reconversion"), while the contact's own submission counter read 1, not 2. In run 1 it still read 1 twenty hours later, so this is not indexing lag. If you count intake volume from the contact record, a near simultaneous duplicate can be missed; the notification stream showed both.

In both runs the later arrival supplied the stored values. Read from the submit timestamps rather than our case labels: run 1 kept the submission that arrived 106 milliseconds second, run 2 kept the one that arrived 235 milliseconds second. We did not measure how the server ordered the two requests internally, so treat this as a consistent observation across two runs rather than a documented rule.

A note for anyone monitoring their own form with a script

We hit this while automating the tests, and it is not a lead reliability finding, but it may cost someone a day of confusion. In our lab, a submission sent by a browser whose user agent string contained "HeadlessChrome" received the normal success page and created nothing: no contact, no notification. The same submission from an ordinary Chrome window was created normally, including when the automation flag was left visible. So the filter followed the user agent string, not automation as such. Observed twice for the drop, and once for the ordinary browser control.

We did not test a human visitor's browser being wrongly filtered, and we did not look at HubSpot's own submissions or spam views to see whether the dropped submissions were recorded there. Nothing here says that ordinary visitor submissions are lost. What it does mean: if you monitor your own form with a headless browser, a green result can be false.

Who this is enough for

Enough, on the evidence above: you want inbound contacts in HubSpot Free with their form answers, you handle the reply yourself from the notification email, and you do not need a deal record created automatically.

Not enough: you need the lead to get an immediate acknowledgement without publishing a postal address, you need a deal in a pipeline per intake, or you need duplicate submissions merged rather than one of the two silently kept.

Evidence pack hubspot-native-intake-v1, two independent runs on 2026-08-22 and 2026-08-23, verified through the HubSpot API and the receiving inbox. Case by case results, limitations and artifact list on the evidence record. Material statements map to this page's claim ledger; anything untested is labeled.