We’re looking to implement imporvements to our HubSpot. Right now, our phone team creates contacts and fills out online application forms for customers directly in HubSpot. Those forms trigger the creation of a child object with all the necessary data populated.
However, we also have a field team that works with new prospective applicants in person. They collect the same information, but they currently use paper forms, and someone later enters that data manually into HubSpot.
What I’m trying to figure out is: Is it possible to create an online form for our field team that, when submitted, automatically creates and associates all the required objects in HubSpot (e.g., contacts, applications, child objects, and deals)? Our challenge is that the field team may not have the time or tech skills to navigate HubSpot the way our phone team does, so we need something simple and automated.
Hey @AC2027 HubSpot forms only directly support contacts, companies and ticket properties so you can only create those records.
You can however trigger a workflow to create records from form submissions. So you can capture everything you need in contact propertied, then trigger a workflow based on the form submission and use the "Create record" workflow action to create the associated record and copy the values from your contact properties into the new record.
Tom Mahon Technical Consultant | Solutions Engineer | Community Champion Baskey Digitial
Hey @AC2027 you’re thinking in the right direction, and this is a pretty common pattern when you have a field team that needs a very simple input flow.
Out of the box, HubSpot forms can only directly create or update contacts, companies, and tickets. They can’t directly create deals or custom objects. That limitation hasn’t changed, even with how HubSpot works today. The workaround is automation. You use the form purely as a data capture layer, then let workflows do the heavy lifting behind the scenes. HubSpot documents this form behavior here (https://knowledge.hubspot.com/forms/create-and-edit-forms )
The usual setup looks like this. Your form is built with contact properties only, even if some of those fields logically belong to an application or child object. When the form is submitted, a contact is created or updated automatically.
That submission then triggers a workflow. Inside the workflow, you use the “Create record” action to create the deal and any custom objects you need, and you map values from the contact properties into those newly created records. You can also associate everything in the same workflow step so the contact, application object, and deal are linked correctly.
For a field team, this works well because the experience is just “fill out one simple form on a phone or tablet.” They never have to log into HubSpot, understand pipelines, or touch multiple objects. From their point of view, it feels like a single submission. From HubSpot’s point of view, it’s a contact plus automation. The workflow action for creating records is documented here (https://knowledge.hubspot.com/workflows/create-records-with-workflows )
One thing to plan carefully is data duplication. Since all fields must exist as contact properties first, you’ll want clear rules about whether those values remain on the contact long-term or are just a temporary staging layer before being copied to child objects. If you want, one key detail to clarify is whether the same person might submit multiple applications over time, because that affects how you design the workflow logic.
Did my answer help? Please mark it as a solution to help others find it too.
Ruben Burdin HubSpot Advisor Founder @ Stacksync Real-Time Data Sync between any CRM and Database
Hey @AC2027 you’re thinking in the right direction, and this is a pretty common pattern when you have a field team that needs a very simple input flow.
Out of the box, HubSpot forms can only directly create or update contacts, companies, and tickets. They can’t directly create deals or custom objects. That limitation hasn’t changed, even with how HubSpot works today. The workaround is automation. You use the form purely as a data capture layer, then let workflows do the heavy lifting behind the scenes. HubSpot documents this form behavior here (https://knowledge.hubspot.com/forms/create-and-edit-forms )
The usual setup looks like this. Your form is built with contact properties only, even if some of those fields logically belong to an application or child object. When the form is submitted, a contact is created or updated automatically.
That submission then triggers a workflow. Inside the workflow, you use the “Create record” action to create the deal and any custom objects you need, and you map values from the contact properties into those newly created records. You can also associate everything in the same workflow step so the contact, application object, and deal are linked correctly.
For a field team, this works well because the experience is just “fill out one simple form on a phone or tablet.” They never have to log into HubSpot, understand pipelines, or touch multiple objects. From their point of view, it feels like a single submission. From HubSpot’s point of view, it’s a contact plus automation. The workflow action for creating records is documented here (https://knowledge.hubspot.com/workflows/create-records-with-workflows )
One thing to plan carefully is data duplication. Since all fields must exist as contact properties first, you’ll want clear rules about whether those values remain on the contact long-term or are just a temporary staging layer before being copied to child objects. If you want, one key detail to clarify is whether the same person might submit multiple applications over time, because that affects how you design the workflow logic.
Did my answer help? Please mark it as a solution to help others find it too.
Ruben Burdin HubSpot Advisor Founder @ Stacksync Real-Time Data Sync between any CRM and Database
Hey @AC2027 HubSpot forms only directly support contacts, companies and ticket properties so you can only create those records.
You can however trigger a workflow to create records from form submissions. So you can capture everything you need in contact propertied, then trigger a workflow based on the form submission and use the "Create record" workflow action to create the associated record and copy the values from your contact properties into the new record.
Tom Mahon Technical Consultant | Solutions Engineer | Community Champion Baskey Digitial
hey, yes as far as i know this can be done, All you need to do is make a hubspot form and when a user will fill that form automatically your contact will be created, furthermore u can also add non-hubspot forms which when filled, can create a contact in hubspot