Describe the form you want in a sentence; Intake drafts it in Google Forms, you read it over, and it lands in the account you connected.
You describe the form you need and Intake writes it: every question, its answer type, whether it is required, and the order they appear in. You get a proposal to read, not a form that already exists. That order matters more than it sounds. A form that appears before you have read it is a form you have to undo; a proposal you can edit is a form you can approve.
Why nothing is created without you
The model that writes the proposal cannot call Google. It proposes a structure, and Intake checks that structure against what Google Forms can actually express — which question types exist, which settings are allowed — before it shows you anything. If a request cannot be expressed in the target, you are told that rather than shown a form that quietly drops half of it. When you confirm, the form is created in the Google account you connected, and you get a real link to it. Not a preview, not an export file: the form, in your account, with your name on it.
Create an account, connect Google Forms, and describe the form from the home screen. The first one takes a sentence and a click. If your description is vague, Intake asks a clarifying question instead of guessing — and that question costs nothing. Every account gets 20 credits a day, refreshed at midnight UTC. A credit is one logical operation: one form, or one edit. A failed operation costs nothing, and a clarification costs nothing.
What was not there yet
Google Forms was the only target at launch. Typeform came later. Microsoft Forms was never a target, because Microsoft does not expose a supported API for creating or editing forms — a Microsoft connection would have been a promise the product could not keep. At launch, editing meant going to the provider. Intake could create, but not yet revise in place.