-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Google forms design changes have breaked the code #2
Comments
Nope. Since http://twiliosheet.azurewebsites.net/ wasn't working at all I gave up. |
I was able to get it to work by making the form an old style one. In the new form just select "Go back to the old Google Forms". And then use the url from the live old style form |
Bummer, this is exactly what I'm looking for but running into the same problem. Selecting "Go back to the old Google Forms" no longer works either. It generates an identical URL that generates the error in TwilioSheet: "The URL you entered looks like a valid URL for a Google Form, I'm just having trouble validating it. Perhaps you entered the URL for an example form? " |
What you have to do is go to: File => Add Collaborators. Then you copy that link. |
I tried the File => Add Collaborators link, but got the message "The URL you entered looks like a valid Google Form, but it doesn't have any inputs for Twilio data. Update your form to accept at least one Twilio parameter and try again." Pretty sure my form is right - it has SmsSid (Short Answer), From (Short Answer), Body (Paragraph). Tried them all as Paragraph as well. Tried setting access permissions to Anyone. Still no joy. Ideas? |
In reply to my past comment: you must first follow the above steps to switch to the old Google forms. Once there, the add contributors buttons works! |
It's working! My steps:
|
Hi! It seems that Google has changed the design of its forms and the code doesn't work with new design. I found an existing form with old design and re-used that but it seems that at least the code on http://twiliosheet.azurewebsites.net/ isn't working with that either.
The text was updated successfully, but these errors were encountered: