Send landing-page enquiries to HubSpot

Choose a contact delivery workflow

You can send Pageree leads to HubSpot through an external automation or a configured HTTP request to a supported HubSpot endpoint. Pageree provides generic HTTP delivery; this guide does not describe a native HubSpot app.

For many small teams, a webhook automation that finds or creates a contact is easier to maintain than a direct API integration. It can also handle ownership, existing contacts, and follow-up steps explicitly. You must configure and test the workflow in your own accounts.

Option A: use an automation

Create a webhook trigger in your automation service. Connect HubSpot using that service’s authorized connection, then choose its contact lookup and create-or-update actions. Check the exact behavior for an email that already exists.

Map only the properties you need. Keep a person’s enquiry in an appropriate property or activity supported by your chosen action. Do not assume every free-text field is a built-in HubSpot contact property.

Submitted value	Example destination
Email	Contact email
First name	First name, if collected separately
Last name	Last name, if collected separately
Company	An appropriate contact property; not automatically an associated company record
Enquiry	An explicitly selected or created property/activity

Inspect the received webhook sample before mapping. Pageree’s default payload places submitted fields under data; the names match your published form fields.

Option B: configure a direct API request

HubSpot documents contact creation, properties, and update behavior in its Contacts API reference. Use the current endpoint and authorization instructions for the API version you choose. Confirm required scopes and valid property names in your account.

A direct request needs a server-side authorization header and a JSON body in HubSpot’s expected shape. Keep access tokens in the approved delivery configuration, never in public HTML or client-side JavaScript. Do not copy an old endpoint or a sample property name without checking it.

Creating a contact on every submission is not the same as reliably updating existing contacts. If duplicate handling requires multiple API operations, use an automation or integration service that performs them. Do not force that logic into a single request that cannot support it.

Ask your assistant for a reviewed setup

Help route leads from my Pageree page [page ID] into HubSpot through
[approved automation webhook / reviewed direct API configuration].
Inspect the actual form schema. Map only approved properties.
Keep credentials server-side and out of the page.
Explain how existing contacts, repeat enquiries, errors, and retries
are handled. Do not mark a contact as subscribed to marketing merely
because they requested a demo or quote.
Help me test a new email and an existing email through the public form,
then check the resulting HubSpot records.

Verify the destination, including repeat submissions

Use test records you control. Submit through the published page, then inspect the contact, mapped fields, and any enquiry activity in HubSpot. Repeat with the same email and a changed message. Confirm the workflow preserves the information you need.

An accepted webhook is not proof that a downstream CRM action succeeded. Review automation failures and HubSpot responses. Pageree’s fallback email and 30-day lead recovery backup can help recover accepted enquiries, but a fallback notification is not a successful CRM write.

Keep subscription consent separate from contact creation. HubSpot has its own communication preferences API; do not treat a lead form as blanket permission for unrelated campaigns.

Start with email delivery if you do not yet need CRM routing. Use the form troubleshooting guide when the visible page and destination disagree.