You have to use the Discourse topic ID where the form submissions are posted here on the platform, not the ID of the Discourse topic defining the form questions. For the example of Edgeryders Forms, you find the right ID as follows:
Take the ID of the Discourse topic defining the form questions. For Edgeryders Forms, thatās 14481.
In that topic, find the topic ID of the output topic in this part "publish": { "topic": 14460 }. You can make sure that this is the topic youāre looking for by constructing its URL as above, and visiting it: https://edgeryders.eu/t/14460
Enter the output topicās ID 14460 into the query page as discussed above.
Follow-up question on multilingualism, in this case for an event that will happen in German for the Wellbeing projects cc (@Richard@Djan):
Top priority:
Can I translate the consent form and use that for the event, both technically (@owen) and from a precedural/research (@amelia) point of view?
@amelia:
I created this form for a German event, and Iām worried the English consent form might keep some people from registering: Edgeryders Forms
Is there any possibility that we shorten this part a bit? It seems a bit intimidating when you register and I just wanted to check if itās absolutely necessary to ask the questions in this way?
If it must remain the same, then I wanted to make sure that itās OK for me to translate and use that translation, or whether this translation has to go through some sort of review.
@owen:
I can translate the text of course, just how would I get the translation into the form - could you help with this? I found this thread - should I add the translation there?
High Priority:
Is it possible to edit/translate the confirmation e-mail that people get sent after registering? E.g. that it includes the event information again, and (this would be very helpful), tell them the username they signed up with and ask them to remember this to change their Zoom name during the event:
Medium Priority:
How do I configure those? Specifically the buttons for:
Submit
Save my answers (in the consent form, it doesnāt seem to be in the code here)
Medium Priority:
Is there a way to change these English parts as well?
Hi @hires, I still havenāt finished this yet, the post you linked to was my attempt to find the right format for translated consent forms. What you can do is copy that format and put the German text in a reply to the post, I will try to make some progress on it today.
Youāll need to ask Matt or Hugi this - I think they understand how that notification system works better than myself.
{
"type": "submit",
"text": "Send your answer"
}
Thatās part of the consent form. Not translatable right now.
Do you know the best way that I can edit/adjust the E-mail that automatically gets sent to the people who register through the tell form?
Is it even possible to add to the e-mail the user name that the participant chose? (It would be great that they have a reminder in their inbox to look up on the date of the event, when we ask them to rename themselves on zoom to this username)
Finally, do/could previously registered participants also receive an automatic e-mail that they are registered to the event? That would be great!
It is possible, but the same email is sent to all who register at all Edgeryders platforms, so it needs to be kept very general. Do you have suggestions that could work with those constraints?
OK, I see the challenge thereā¦ Would it maybe be possible to set a webhook with the form submission of just this one form that we could then connect with zapier to send an additional mail?
There is no such functionality right now, so no. In theory, @owen could build into the form software to have a field in the config with webhooks that are called on submission of a specific form. That sounds like just a few lines of code, if Iām scoping it right - but I have no idea how much @owen has on his plate now or what is currently priority.
I have added it to the request list, as Iām focusing on the translation support for the consent form, Iāll do it alongside that in the next update, which Iām hoping will be ready to test tomorrow.
This wouldnāt be too difficult to implement - I can probably fit it in the next update, but I think thatās the cap at the moment otherwise weāre pushing too many features at once.
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:
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:
Iām not sure, but as long is that data isnāt being stored, but just used to send an email through another service we control, that doesnāt sound like too much of an issue with GDPR? @matthias?
No need for a consent field in the form. To be compatible with GDPR, users would have to agree to our platformās privacy statement, and that statement would include a list of data processors with whom we have a GDPR compliant data processing agreement. Any third parties to which we send personal data technically have to be part of such a list. In practice, this is quite difficult to achieve.
