Are there properties specific to forms that can be used as a tag?

I am working on an integration with HubSpot and our sales platform, Dynamics. We want to have a tag on a form that flags to the integration which form submissions need to be synced across to Dynamics. The idea is the code within Dynamics will be looking for this tag, so if any new forms are created with it, it will know to sync those submissions too.

However, I am not sure if it possible to tag a form as it seems the only properties I can add to the form are contact/company/other object properties. I dont think this will work for us as the integration would then be looking at contact records for the property to be populated and then have to work back to form submission. Also I worry if someone has already completed a form then they will already have a value for this property, so if they complete a new one it will not be picked up by the integration.

Does anyone know if there are form properties that can be used insted to do this? Or another solution to this issue.

Hi @ABeney,

Have you considered using a hidden form field for this? Pass contact property values with hidden form fields

This would identify each form submission coming through one of the relevant forms and would allow you to pass this information on.

If this wouldn’t work, can you please share a bit more context as to why?

Best regards!

Thanks for the suggestion, though I dont think this would work as it is still a contact property even though it is hidden (rather than a property about the form). This would be the same issue as I mentioned before where once the value was set on a contact, it wouldnt be able to pick up if they submitted another form with the same property, as it would already be set. It also doesnt then relate directly to the form and the logic would have to be much more complex as it would need to search for the value, find the contact then find form submissions on that record and take out the relevant information from there.

The only workaround I can think of is doing it based on form name, so the logic looks for any forms with a name containing X. The reason I am not sure about this is because name can be changed easily by someone without realising the impact.