クリエイティブな才能を開花させよう

A way to deactivate a form so that it no longer receives submissions, but can be reactivated and used again. For example, I need to modify the form and stop receiving submissions for a while, but I want to be able to use the same form in the future without having to clone it, since the submission link would remain the same. So, having a way to deactivate it just so that it is no longer public and submissions are not made, but that I can reactivate it in a simple way, would be very helpful. ...その他を表示

Hello!   I'm a HubSpot partner and I have encountered an instance where my HubSpot customer wants to use the county as a routing option for internal emails. That's great and doable; however, when the customer has nearly two hundred offices around the country, this leads to an overwhelming number of counties listed for a customer to choose from on the form.   Our idea: Use conditional options! By having a State dropdown menu and creating a dropdown for County, we could apply the conditional option for each state.   The Result: The conditional option only works on the contact record and not on forms.     HubSpot, please make this happen for us!   And community, if you have a solution, I would LOVE to hear it! ...その他を表示

When it comes to Forms and receiving submissions, there should be an option to turn off excluding submissions based on IP addresses. Form submissions are different from traffic.    Or at the very least, there needs to be an option to export excluded submissions when exporting the full submissions list. Even if they're separated by tabs.    Use Case Example: We created an RSVP form for an upcoming event that includes clients and employees. A few employees filled out the form when they were in the office, which meant their IP address was one of the ones included in our excluded list (since we're trying to filter out internal traffic from external). But in this case, we need to see their RSVPs with the full list. They shouldn't be excluded. Now we're having to manually add them in, which won't be sustainable with a much larger list size in the future.  ...その他を表示

Often times we enter fake data into our own form to test workflows or we get spammed with fake accounts. I'd like the ability to delete form submissions so they don't impact the metrics. ...その他を表示

I would like to see the option to unpublish a form and or to set a limit to the submissions. For example I would like to set a limit of 100 submissions due to a webinar subscription.   November 7, 2022 Edit: 931 days and counting. Can someone please make this a meme?   April 6, 2023 Edit: 1081 days and counting. This isn't funny anymore.   January 2, 2024 Edit: Day 1352 – Still no option to unpublish a form or cap webinar sign-ups. We're considering switching to smoke signals for faster results! 😂   Come on, tech wizards, let's make this happen before we're sending messages via carrier pigeons! ...その他を表示

The new forms tool has some great upgrades but when it comes to styling it is now really limited. I would like a way to have more control, ideally being able to add a link to a stylesheet (I hate that these are now in iframes and you have no control over the CSS). At the very least, it is really painful that you can't remove the padding on the forms.  ...その他を表示

In the future, it would be incredibly helpful if HubSpot forms could allow users to create multiple contacts from a single form submission. Use Case Example: Imagine a scenario where a customer is filling out a form on behalf of someone else, or needs to provide information for multiple stakeholders, such as their manager, billing contact, company owner, or other relevant parties. Proposed Solution: Add a “+” or “Add Contact” button to the form, allowing users to dynamically add more contact fields as needed. When clicked, a pop-up or conditional section appears where the user can enter the details for the additional contact (name, email, role, etc.). All submitted contact details are processed and create separate contact records in HubSpot, linked to the original submission. Benefits: Streamlines data collection for group registrations, event sign-ups, or any scenario involving multiple stakeholders. Reduces friction for customers who need to provide information for more than one person. Improves data accuracy by capturing all necessary details in one go. Example Workflow: User fills in their own details. Clicks “Add Contact” to include their manager’s information. Optionally adds more contacts (billing, owner, etc.) as needed. Form submission creates all relevant contact records in HubSpot. ...その他を表示

Hoping someone has a solution here, but have a form in HubSpot used internally for submitting tickets to our Support Team on behalf of a customer. Additionally, we have IP Addresses excluded from our site analytics to avoid inflating numbers.   Found this article that explains if you have IPs excluded their submissions will be considered spam - which is exactly what we are experiencing. Legitimate internal form submissions are sitting in spam until someone happens upon it OR we get a complaint their ticket never created.    I don't see a way around this so my question to the community: Is there a way to set a notification of spam submissions? If we can at least be proactive by knowing it's sitting in spam we can deal with this limitation. But with our current situation of not knowing until it's a problem, we're needing a better solution. Even if it's via API, I'm willing to get creative.   Appreciate the ideas! ...その他を表示

Overall, the new form editor with enhanced conditional logic is a VAST improvement with tons of promise, two big drawbacks in current beta state that are preventing us from actually testing in a client-facing capacity though -   Hidden Fields: Currently, you cannot use hidden fields in the same way that you can with the legacy forms editor. You can hide fields when certain conditions are met, but in the old from, it was really helpful to be able to use hidden fields to pass values along to contacts/companies/tickets upon submission. Theoretically this is still possible with workflows (contact has submitted "x" form, populate with "y" values), but there's a lot of reasons why it would be better to accomplish this natively in the form as opposed to through workflow. Both because of maintenance/number of workflows, and to keep a stronger hold on permissions around workflows in general.   Non-contact/company properties: Currently, this is the big blocker in allowing us to actually test this beta with a public-facing form in the new editor. The new logic is a VAST improvement over what we had previously, but we're primarily trying to create tickets based on form submissions to take advantage of this logic. In current state, the only way we could do that is creating a bunch of contact properties that we don't have much use for and syncing them over to a ticket. Ideally, we'd be able to ask for ticket properties in the form editor same as we can in the legacy editor. Sync fields (with their various limits) is not a good solution here either, because we'd still be creating contact properties that have no use other than to be a container to sync over to a ticket, which is not ideal.    ...その他を表示