Feature Requests

A current workaround is to create multiple endings with different redirects. However, building extra steps for more complex forms would not make sense. It would be a lot easier if there were some flexibility regarding the form logic that would allow users to define parameters (e.g. variables, specific answers, etc.) that can be passed on when users are redirected. Or perhaps there's a better suggestion? Thanks for your feedback User Story: As a user of HeyForm, I want to be able to see advanced options for the Endings Screen "Redirect on completion Settings", so I can select for each variable that has been set in the Form Logic if it should be passed on as an additional parameter with the Redirect URL. This would allow the users to create dynamic (rule-based) landing pages targeted to specific audiences (based on their answers). Acceptance Criteria: Users can select to define advanced options after enabling "Redirect on completion" (Ending Screens) The system presents all available variables that can be passed on as a URL parameter which can be added via "+" from a dropdown selection list (nice to have add-on: the parameters are presented as a sortable list to allow changing the order of the parameters after they have been added) After saving the settings, the redirect URLs are dynamically amended with the parameters that have been defined by the user (nice to have: cross-check/warning in the Logic Editor if the user wants to remove a variable that has been selected as part of the URL redirect parameters)

Description: Allow users to customize the URL slug for their forms. Instead of the default randomly generated URL, users can set a custom, more memorable URL slug. User Story: As a user of HeyForm, I want to be able to customize the URL slug of my forms so that I can create more memorable and brand-consistent links for sharing with my audience. Acceptance Criteria: Users can enter a custom slug when creating or editing a form. The system checks for slug uniqueness across the platform to prevent duplicates. If a custom slug is already in use, the user is prompted to choose a different one. The custom slug is reflected in the final form URL, replacing the default random string. The form is accessible via both the default and custom URL for backward compatibility. Users receive a notification if their custom slug conflicts with any future system-wide URL updates.

Description: Integrate PayPal as a payment gateway option within HeyForm. Users filling out forms should be able to complete payments directly using PayPal. This feature should support various currencies and ensure secure transactions, with an easy setup process for form creators. User Story: As a form creator, I want to enable PayPal payments on my forms so that users can complete transactions securely and efficiently. Acceptance Criteria: The form creator can select PayPal as a payment method when creating or editing a form. Users can pay using PayPal directly from the form. Transactions are processed securely and confirmations are sent to both the form creator and the user.

Description: Allow users to connect their Notion account to HeyForm via API, and automatically sync form responses from HeyForm to a selected Notion database. User Story: As a user, I want to link my Notion workspace with HeyForm so that form responses automatically populate into my selected Notion database. This will enable seamless integration of my forms with existing notes and databases for centralized data management. Acceptance Criteria: Users should be able to authenticate their Notion account from within HeyForm. A successful connection should confirm with a message and appear under "Integrations". Option to select a Notion database when setting up the integration. Form fields should map correctly to the Notion database columns. Sync should occur in real-time or with minimal delay.