You can send a Shopify form entry to Google Sheets by appending each submission as a new row in a spreadsheet you choose. SK Form Builder does that through Google's official API, using a service account, and it writes a header row the first time it uses the sheet.
That live row is the right setup when a small team wants to filter leads in a spreadsheet instead of living only in the app inbox. If you want a file you open on your own schedule, export the same submissions as CSV, Excel, or PDF. The catalog does not assign the Google Sheets connection to Starter, Basic, or Pro. Those prices are free, $4.99 a month or $49.90 a year, and $12.99 a month or $129.90 a year. There is no feature-to-plan matrix, so confirm the connection on the plan screen before you promise the sheet to the team.
When a shared sheet is the better inbox
The app already stores every submission in an inbox. Staff can set a status of approve, reject, or pending, update statuses in bulk, and assign a response. That inbox is enough when one person owns the form.
A sheet helps when several people need the same list. A wholesale lead, a contact message, and a popup signup can sit in one grid that sales sorts by date or scans for a missing phone number. People who do not log in to Shopify can still read the rows if you share the spreadsheet with them through Google.
Treat the sheet as a copy that grows at the bottom. The catalog describes an append: each submission becomes a new row. It does not describe a sync that writes status changes from the sheet back into the app. If someone edits a cell, trains a filter view, or hides a column, that work stays in Google. The inbox remains the place where approve, reject, and assignment live.
Use one spreadsheet per form when the columns differ. A contact form and a wholesale application do not belong on the same tab unless you have already decided how you will tell the rows apart. The catalog does not document a combined workbook that merges every form automatically.
What the first row and the next rows contain
On first use, the app writes a header row. After that, each accepted submission adds one data row. Send a real test from the storefront, then look at the sheet before you share it. The catalog does not publish a fixed list of column names, so the header you see after that first test is the header to trust.
Expect the columns to follow the fields on that form: the name, the email, the message, and any question you added. Do not assume a public schema that is identical for every merchant. A form with a file upload and a form with a star rating will not produce the same grid.
The app also stores UTM parameters, device type, and the referrer on the submission itself. Those values are documented on the response and on the Shopify Flow trigger. The Sheets section of the catalog only says that the submission is appended as a row. After the test, check whether source, medium, and campaign appeared as columns. If they did not, keep UTM reporting in the app analytics or in Flow, and keep the sheet for the answers the team filters by hand.
Avoid a second header row
Because the app writes the header on first use, start with an empty sheet or an empty tab. If you type your own header before the first submission, you can end up with two header rows: yours, and the one the app writes. The catalog does not document a setting that merges those rows or that skips the automatic header.
- Create the spreadsheet and leave the first row blank.
- Connect that spreadsheet in the form's Google Sheets settings.
- Submit one complete test entry from the live theme.
- Confirm that row 1 is the header and row 2 is the test.
- Then share the sheet. Add filter views after the header exists, so you are filtering data rather than a second set of labels.
If a duplicate header is already there, delete or move the extra label row in Google after you have compared it with the app's header. Do that once, then leave row 1 alone. New submissions append below the existing data. They do not rebuild the header on every entry.
Export a Shopify form to a spreadsheet instead
A live append is noisy when the form is busy and the team only needs a weekly file. The inbox exports three formats: CSV, Excel, and PDF. A CSV or Excel file is the straightforward way to export a Shopify form to a spreadsheet, open it locally, and file it with the month's leads.
Large CSV exports of more than 1,000 rows run as a background job. The app emails the merchant a download link instead of holding the browser open. Plan for that email when you export a long history. Smaller exports can download directly. The catalog does not publish a row cap for Excel or PDF, so try one export of a real form before you promise a one-click file to finance or to an agency.
Choose the sheet when new leads must appear without a manual download. Choose the export when you want a snapshot, a backup, or a file you can attach to an internal email. You can use both: the sheet for the current week, and a CSV archive when you want a copy that no one can edit in the shared grid. A blocked spam attempt never becomes a row, so test with an address your domain list allows. If the row is missing and the merchant email arrived, check the inbox first, then the spreadsheet.
Questions about a form and a sheet
Does the sheet update if I edit the submission later?
The documented behavior is an append of each submission as a new row, with the header written on first use. Edit status and assignment in the app. Treat later cell edits in Google as spreadsheet work, not as a two-way update.
Which plan includes Google Sheets?
The catalog lists the three prices and does not assign Sheets, or the CSV export, to a named tier. Open the plan screen in the app and confirm the connection there.
Can I start with a file and add the live sheet later?
Yes. Export CSV or Excel from the inbox for the history you already have. Connect the sheet when you want new submissions to append on their own. Put the connection on an empty tab so the first-use header stays a single row.
Read the integration list on the SK Form Builder page, then send one test submission and confirm the new row before the team uses the sheet as the lead list.