When connecting Quform to SharpSpring, it can present some difficulties when multiple forms are on the page—even if they are not all Quform forms. If a Quform is alone on a page, SharpSpring's standard form code should work. This article will detail how to connect Quform forms to SharpSpring.
The following user roles can connect Quform forms to SharpSpring:
Forms are accessed through the toolbar.
When connecting multiple forms on the same page, an ID needs to be declared in order for the SharpSpring code to determine which form to capture. With Quform, the ID can be dynamic. After viewing the ID and declaring it in the SharpSpring code, the ID may be different the next time, preventing the SharpSpring code from finding the form. However, by utilizing the form's unique class, you can better connect the form to SharpSpring. This grabs the dynamic ID and stores it in the variable, so that the SharpSpring code can obtain the form’s ID even though it isn’t the same on every page load.
For information on accessing and creating Quforms, refer to the following:
To connect Quform forms to SharpSpring, do the following:
The variable should be different for each form you are connecting on the page. It is fine to just use formID1, then formID2, and so on, but be aware that the name is not important so long as it is unique.
Note: The unique class is important because it has a dynamic ID but a static class. Normally, static IDs are needed, but Quform does not have such.
Important: Be sure to use the class of the form you are connecting where “.iphorm-form-1” is shown. Additionally, be sure to place a period before iphorm.
Note: Leave your original endpoint value where the X values are. Be sure to place the variable name where formID1 is.
The following example is code with two form classes:
<form id="iphorm-2b2177d7c1692" class="iphorm iphorm-form-1" action="/connect-with-us/contact-us/#iphorm-41ab457e683f4" method="post" enctype="multipart/form-data" novalidate="novalidate">
The following example is a complete Quform code: