What is JotForm?
JotForm is a free online form builder which helps you create online forms without writing a single line of code. No sign-up required.
At JotForm, we want to make sure that you’re getting the online form builder help that you need. Our friendly customer support team is available 24/7.
We believe that if one user has a question, there could be more users who may have the same question. This is why many of our support forum threads are public and available to be searched and viewed. If you’d like help immediately, feel free to search for a similar question, or submit your question or concern.
Trigger Google Script with form submissionAsked by GVUgraphics on February 04, 2015 at 09:03 PM
Thanks a lot for your reply. To narrow this problem one more time the workflow is the following: data from Jot web form goes to spreadsheet (this works fine) => new submissions activate the trigger which run a custom scrip bound to the spreadsheet.
And here is the problem.
The script itself works fine and if a onEdit or onChange trigger installed it fires when you manually make a change in a spreadsheet. But nothing happens when a new submission arrives and of course this submission make a massive change in a spreadsheet. Adding onFormSubmit trigger doesn't work neither. It looks like a trigger doesn't consider Jot form submission as an event at all. With Google forms everything works just fine. It seems to me Jot form submission should pass some additional info to the spreadsheet to be detected as a form submission event.
Adding onChange or onEdit functions in a script doesn't help.
Thanks a lot in advance
Thank you for your patience. I did some research regarding your issue and I am afraid I was not able to locate anything different that would help in this situation. With reference to what my fellow colleagues mentioned in this thread as well as this one, I can't seem to locate anything else that would be fruitful at this time. I have decided to escalate your issue as a Feature Request to our development team so they can take a look at the situation and possibly develop a widget or some sort of workaround for your inquiry. A specific time-frame cannot be suggested at this time but I can assure you that they will be looking into this situation. I hope an update will be provided soon seeing that the suggested one on the original thread was not working for you. I appreciate your patience.
Hi Sean, any news on this feature request?
I'm afraid the we do not have any specific news at this time. This feature request has been assigned to one of our developers, but as our developers are actively working on some more pressing matters, and already have a lot of work on their plate, we can't give you any estimate on when or if this is going to be implemented.
We will let you know through this thread when we have any relevant updates for this issue. Thank you for your understanding and patience.
To quote from my another reply:
Unfortunately, this behavior is defined by Google's policies and external changes cannot trigger Google app scripts.
However, there is way to get over it by using a time-based trigger and saving the last edit date on a different document. It is not actually too difficult as fully described here:
I hope it will work out for you. If you need any assistance, please let me know.
Based on our developer's reply, I think this is the restrictions that he's talking to: https://developers.google.com/apps-script/guides/triggers/#restrictions.