Using Edgeryders Forms

Documentation & Support Collaboration
,
68

I have uploaded the latest build here for testing.

Here is a list of what has changed:

  • The form picks up translations of the consent forms in this topic.
  • Each consent form translation uses an ISO code (“de” for German, “en” for English) to determine what language it is in.
  • When you create your form, you can set the default language using the ISO code as such in the form config:
"language": "de"

  • This will load the consent form in that language. It will also change the default text of non configurable text items such as “username” and “email” to the respective language. These translations are built into the application, so to add new ones means updating the application.

  • You can set a webhook URL in the form config, as such:

      "webhook": "https://hooks.zapier.com/hooks/catch/4667961/onxl5ey/",
  • Setting the webhook will ping that URL with the following JSON payload:
data: {
 email: the submitted email,
 username: the submitted username,
 form: the ID of the form
}

  • I have tested this with Zapier and it works fine, you can then use Zapier to pass that data on to an action.

  • There are two issues with doing this that need to be discussed (@hugi, @matthias ):

    • What this entails for GDPR, as we are now sending user data to a third party. If it requires another consent field, this could be added to the (already long) consent form.
    • This does not work for users who already have an account. As I understand it, there is no way of getting the email of an existing user through the API. So custom email notifications can only be sent to new user registrations.

  • You can configure the form link (at the top of the page), in the configuration as such:

"form_link": "Teilnehmen"

I have updated @hires form configuration with these changes so you can preview them here.

When this is ready and we’re ok with the changes made above, I can push them to the live site.

3 Likes