Is there a workaround for Hubspot Form submissions overwriting the existing property value?
Here’s my use case:
Trying to setup an event registration form without overwhelming ourselves with a property for each event item. There are multi-line text properties we’d like to keep a reportable, easily accessible view of:
- Talk Submission
- Build System(s)
- What topics would you like to learn about at the event?
- What are the primary languages/frameworks you are using?
- What are the biggest developer and build challenges you face?
Ideally when a form is submitted, the contact record would update by appending the new text values to their existing one. Instead, a new form submission replaces the existing values.
This will allow us to discover future event opportunities, create more value for our users, follow up on leads, and make better content decisions. It’d be incredibly useful to find an automatic way to keep these submission values in Hubspot.
Another consideration: if we continue using our current setup and automate the spreadsheet to create contacts in Hubspot we’d still face this same issue.
Current Setup:
Multiple google forms for each event that feed into individual spreadsheets with a list of contacts and their responses listed. After event all data is imported manually and data quality is checked in hubspot. Copying + Pasting anything that shouldn’t be overwritten.
Problem-solving attempts:
I created matching properties for their “history” and attempted to create a workflow testing both “copy” and “set” actions to append the new submission data to the existing history, but it all overwrites.
Additional Notes:
- I understand there’s a property history, but there’s no access to reporting using the property history.
- Allow appending more than once, so it’ll still append on the 18th submission as it did on the 2nd.
- I understand you can export property history and re-add that way, but this is very time-consuming.
Hi @SNeubeck,
If you want to append something to an existing property, you would use the ‘Set property’ workflow action, correct, and set it up like below:
This would append “+1” to the current value.
Best regards!
Does this function with two properties?
@SNeubeck what exactly do you mean? Applying the same logic to two properties? If so, yes, simply add another workflow step for “Set property value” for the second property.
Here’s the workflow I’m currently attempting:
@SNeubeck what exactly should it do? Once you explain, I can confirm or advise what to change.
Trying to solve this:
Ideally when a form is submitted, the contact record would update by appending the new text values to their existing one. Instead, a new form submission replaces the existing values.
I am using “Most Recent Talk Submission” as the form submission value and “All Talk Submissions” as the storage value. When someone submits an event form and there is already information available, the value from “Most Recent Talk Submission” is appended to “All Talk Submissions” without overwriting any existing information.
The workflow would be:
1. A contact submits a form to attend an event this month.
2. The “Most Recent Talk Submission” value is filled using the form value.
3. Depending on their event history:
a. First-time attending an event/submitting a talk (i.e., the “All Talk Submissions” property is unknown):
i. Set “All Talk Submissions” by copying the value of “Most Recent Talk Submission”
ii. Ideally, include the date the talk was submitted.
b. The contact attended an event in the past and submitted a talk:
i. Update “Most Recent Talk Submissions.”
ii. Append the newest “Most Recent Talk Submission” to the existing value in “All Talk Submissions.”
iii. Ideally, include the date the talk was submitted.
c. If there’s no new talk submission, no action is taken.
Do I need another property, perhaps? a sort of “staging zone” specifically for this automation?
@SNeubeck looks like your workflow is doing this exactly then 
A few things:
- For the middle branch, you’re documenting the recent conversion date, for the left one you aren’t. You might want to add that.
- If you want to test whether this works as intended, simply limit enrollment to your own email address (Email is any of [your email address]), then submit the form yourself a few times and check the property afterwards.
Best regards!
The problem is it doesn’t. 
- Yeah, the date thing isn’t really part of the problem. I understand it needs to be added to the other branch. I’m not concerned about that component until I get the property appending correctly
- As mentioned, I’ve tested it repeatively doing exactly as you mentioned. The property is still not appending, it’s overwriting.
I’ll dig in further and return if I find a solution. Thank you.
@SNeubeck can you share a screenshot of the branch criteria and a screenshot of the property history for both properties?
