beta // transparent output

HubSpot Form Filler

Map query parameters, cookies, and literal values for HubSpot forms you control, then generate a readable configuration for review.

Workflow shell

Show the operator what gets mapped, validated, and generated before anything goes live.

This should behave like a controlled workflow surface: define the form, review the mapping, decide what belongs in query params, cookies, or literal values, and then generate the snippet or test configuration from one readable screen.

Input review

Define the form and mapping surface

source type target
campaign value passed through the landing URL
required contact field
used for context, not arbitrary hidden-field guessing
Pre-submit checks
  • Portal ID and form GUID look valid enough to generate helpers.
  • Email still maps cleanly as the required contact field.
  • Target fields are unique and do not collide.
  • Snippet generation stays public, while real submission remains protected.
Generated output

Return artifacts an operator can actually use

prefill-helper.js json config enabled 
{
  "portalId": "198234",
  "formGuid": "8d5f-2af1-11d1-bf4e",
  "mappings": [
    { "sourceType": "query", "source": "utm_campaign", "target": "latest_campaign" },
    { "sourceType": "literal", "source": "email", "target": "email" },
    { "sourceType": "cookie", "source": "hubspotutk", "target": "hutk" }
  ]
}
Snippet output

JS helper + JSON config

Give operators a copyable surface instead of forcing them to improvise hidden-field logic.

Validation pass

Required fields and collisions

Catch mismatched property names, missing required fields, and duplicate assumptions before any live test runs.

Test boundary

Owned forms only

Keep real submission behavior behind authorization so the public product never becomes a reckless submitter.

What the beta does

The fastest way to create broken form workflows is to mix hidden fields, query parameters, cookies, and field mappings without a clear pattern.

The beta helps you:

  • document the source and destination for each field
  • spot duplicate or conflicting mappings
  • generate a readable JSON configuration and helper snippet
  • separate browser-side prefill logic from authenticated submission logic

What it does not do

This public beta does not submit records to HubSpot, look up private portal data, or authenticate to your account. Live submission belongs behind an owned, secured server-side process with appropriate permissions.

Review before implementation

Confirm the portal and form identity, exact internal property names, required fields, consent requirements, source preservation rules, and the behavior expected after submission. Test only against forms and data you are authorized to use.

Continue with the implementation guide

Confirm the prefill behavior before placing generated logic on a live form. The lifecycle operations trail connects mapping, validation, submission, and troubleshooting guidance.

What this connects to

Turn the output into a rule your team can repeat.

Use the related hub, implementation notes, and templates to document the decisions behind the generated output.

Topic hubs