Google Sheets
Send Instagram leads to Google Sheets automatically
Somebody comments on your post, your automation sends the DM, they fill in the form, and a new row shows up in Google Sheets. You connect Google once and then stop thinking about it. No CSV downloads at the end of the week, no half remembered exports, no lead sitting in an inbox you forgot to check.
Short answer
To send Instagram leads to Google Sheets, attach a form to your comment to DM automation, connect your Google account, and pick a spreadsheet. Every submission is appended as a row within seconds, aligned to your existing column headers.
Set up in three steps
Sign in to Google once
You connect your Google account at the account level, not once per form. Every form you build afterwards can point at a spreadsheet without another login.
Pick a sheet or make a new one
Choose an existing spreadsheet through the Google file picker, or create one from inside the app and we write the header row for you.
Watch the rows arrive
Someone answers your form in the DM and the row appears seconds later. No refresh button, no nightly export, no copy and paste.
Your sheet can change and nothing breaks
This is the part most integrations get wrong. They append values in the order the form defines them, so the first time you drag a column or add one of your own, every answer quietly shifts one place to the left and you find out weeks later.
We read the header row of your sheet before every single write and match each answer to the column with that name. Move things around, add a status column, keep a formula on the end. The next row still lines up.
Why people leave it on
Columns are matched by name
We read the live header row before every write. Reorder your columns, insert a status column, rename a header, and the answers still land where they belong.
Your own columns survive
The notes column you added by hand is never touched. We fill in the columns we recognise and leave the rest of the row for you.
One sheet, many forms
Point a waitlist form and a booking form at different tabs of the same spreadsheet, or at two different files. Both are fine.
Optional context columns
Turn on the meta columns and each row also carries the submission time, referrer, and the Instagram participant id, so you can tie a lead back to the conversation.
You keep the file
The spreadsheet is yours, in your Drive, under your sharing rules. Cancel with us tomorrow and the data stays exactly where it is.
Access limited to that one file
We ask for per file access instead of full Drive access. Picking a spreadsheet grants us that spreadsheet and nothing else in your Drive.
What we can and cannot see in your Drive
We use the per file Google scope, so our access is limited to files you create through the app and files you hand us by choosing them in Google's own file picker. We cannot list your Drive, cannot read the folder next to it, and cannot open a spreadsheet you never selected.
That is also why the picker exists in the flow rather than a text box asking for a spreadsheet id. The picker is Google's interface running inside a Google window. You browse everything you own, and the moment you choose a file, that one file is shared with us. Revoke it at any time from your Google account, or disconnect from the Connections page.
Questions people ask first
Does this work with an existing spreadsheet?
Yes. You browse your Drive through the Google file picker and choose any spreadsheet you already use. If the sheet already has a header row, we match against it. If it is empty, we write the headers first.
What happens if I rename a column?
The field that used to write there stops matching, so that column fills in blank rather than pushing values into the wrong place. Open the connector, remap the field to the new header, and the next submission lands correctly.
How fast does a row appear?
Usually within a couple of seconds of the person tapping submit. Delivery runs right after the submission is saved, so a slow or broken spreadsheet never blocks the answer from being recorded on our side.
What if a delivery fails?
The connector shows the last delivery status and the exact error, so you find out from the app rather than from a gap in your data. Fix the cause, then use the test button to confirm before you rely on it again.
Do I need Zapier or Make for this?
No. The connection is built in and there is no per task charge in the middle. If you already run a Zapier or Make workflow, the webhook destination can feed it instead.
Need it somewhere other than a spreadsheet?
Send the same submission to your own server, your CRM, or a Zapier and Make catch hook with the webhook destination. Both can run on one form at the same time, so the sheet stays as your readable copy while your system gets the structured one.
Connect your accountAsk for it
Need something that is not here yet?
Tell us what you were hoping to find. Requests from people who are still deciding are the ones that shape what gets built next, and they go straight to the person who writes the code. Leave an email and you get an answer, not a silent roadmap.
Bigger idea, or a build of your own? The full request page has more room.