Return a list of the watches owned by the invoking project in Google Forms
A documented Google Forms operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
Return a list of the watches owned by the invoking project.
- GETReads data · forms
forms.googleapis.com/v1/forms/{formId}/watches
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Google Forms operations the program may use, and this is one of them.
- You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.
Other Google Forms operations
- Create a new form using the title given in the provided formPOST · changes data
- Create a new watch. If a watch ID is providedPOST · changes data
- Change the form with a batch of updatesPOST · changes data
- Delete a watchDELETE · changes data
- Renew an existing watch for seven daysPOST · changes data
- List a form's responsesGET · reads data
- Get one response from the formGET · reads data
Questions
- Can HumDay return a list of the watches owned by the invoking project in Google Forms?
- Yes. This operation is published in Google Forms's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Does this change anything in my Google Forms account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Google Forms.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Google Forms account.
Where this came from
Read from a published API description for Google Forms at forms.googleapis.com/$discovery/rest?version=v1. The description above is the provider’s own wording, not ours. Last published 2023-04-21.