Multiple different forms for single contact

[inigoveiss]

Hello all!!

I am developing a service availability checking form that can be submitted multiple times by a single contact via API.

Examples of different form submissions are:

• Service 1 from 2019/01/09 to 2019/05/09.
• Service 2 from 2019/01/09 to 2019/05/09.
• Service 2 from 2019/02/09 to 2019/05/09.

Which is the best option to store all the information in the contact?

I am new to hubspot and I don't know where can I find info for my question.

Thanks in advance!!

[IsaacTakushi]

Welcome, @inigoveiss.

To clarify, is "Service 1 from 2019/01/09 to 2019/05/09" an example of an inquiry a contact would submit that you need reflected on a HubSpot contact record?

If so, you could create custom contact properties to reflect both the services and ranges requested. There are several field types to choose from (e.g. dropdown select and date picker), so you can create as few or as many custom properties as meet your needs.

Please let me know if I have misunderstood your question or can provide additional guidance.

[inigoveiss]

We need 3 different fields or properties: servie, start date, end date.

We currently have over 500 services. A combo with every option is not viable.

I'm trying to make it work with workflows for submissions.

[IsaacTakushi]

Hi, @inigoveiss.

Thanks for clarifying.

From your description, I'd recommend trying a dropdown or multiple checkbox type field for your services and date picker fields for each of your start and end dates.

You can create custom contact properties in your account by following these steps.

[inigoveiss]

Hi @IsaacTakushi ,

thanks for your answers.

that is what I have. However, as a user can submit 0 to N forms, each time the fields get replaced.

I'm working with workflows for the submissions and seems to work in my case.

The only thing is that I have to check the form submissions instead of the contact info.

[IsaacTakushi · Accepted solution]

Hi, @inigoveiss.

Ah, I see. Yes, that is a limitation of contact properties.

One alternative I can think of would be the Timeline API. This would allow you to create custom inquiry/submission events which would appear on a contact's timeline with the information they submitted. You can then segment lists and workflows with these events.