Pick a depth. Each prompt opens in your AI pre-loaded with the lesson. Click a row to preview the prompt.
Before any flow can run, the automation tool needs permission to act inside your other apps — to read new Tally submissions and to write rows into your Google Sheet. This authorization step is where most beginners either freeze ('why is Zapier asking to see all my spreadsheets?!') or click through blindly, and both reactions cost you later. Freeze and you never ship; click blindly and you cannot answer the question every real client asks in the first call: 'wait, what exactly does this thing have access to?' Being able to explain app connections in plain words — what was granted, where to see it, how to revoke it — is a trust skill you will use in every single client engagement, because you will be asking businesses to connect their email, their CRM, and sometimes their payment data.
Here is the exact setup, using Tally (a genuinely free form builder) and Google Sheets. First the pieces: at tally.so, create a form called 'Project Inquiry' with three questions — Full name (short text), Email (email field), and What do you need? (long text) — and publish it; Tally gives you a public link like tally.so/r/abc123. In Google Sheets, create a spreadsheet called 'Leads' with headers in row 1: Name, Email, Message, Submitted At. Now the connection: in your automation tool, add Tally as a trigger app. Tally connects with an API key — in Tally you go to Settings, then API keys, create a key, and paste it into the connection dialog. That key is a password that lets the tool read your form submissions; treat it like one.
Google Sheets connects differently, through a sign-in flow called OAuth: a Google window pops up, names the app requesting access, and lists what it wants — including 'See, edit, create, and delete all your Google Sheets spreadsheets.' Read that sentence and notice the word 'all': you are not granting access to one spreadsheet, you are granting the tool's connection to your whole Sheets account, and the flow you build chooses which file it touches. That is normal and how nearly every integration works, but the professional habit is knowing the audit trail: at myaccount.google.com under Security, then 'Third-party apps and services', you can see every app you have granted access to and revoke any of them with one click, instantly breaking any flow that used it. A practical client-work tip while you are here: connections belong to accounts, so when you later build for clients you will connect their accounts, not funnel their data through your own.