How to send form submissions to Google Sheets

Two ways to get form submissions into a spreadsheet: export a CSV by hand, or connect Google Sheets so each new submission is added as a row.

Copying form submissions from notification emails into a spreadsheet by hand is slow, and it is the kind of task where rows get missed.

There are two reliable ways to move submissions into Google Sheets: export a CSV file when you need one, or connect the sheet so new rows appear on their own. This guide covers both with FormDB, including the exact behaviour of the integration.

Two ways to get submissions into a spreadsheet

CSV export

Google Sheets integration

How it runs

You click a button and import a file

Each new submission adds a row

Plans

Every plan, including Free

Paid plans

Past submissions

Included

Not included

Where data goes

Any spreadsheet you choose

A new spreadsheet FormDB creates

Good for

One-off reports, backups, existing sheets

A sheet that stays up to date

CSV stands for comma-separated values. It is a plain text file with one line per row, and every spreadsheet program can open it.

Option 1: export a CSV and import it

Open the form's Submissions tab in FormDB and click Export CSV. The file contains the folder you are looking at (Inbox, Spam or Trash), and if you have typed something in the search box, only the matching submissions. Rows are ordered newest first, up to 50,000 per export.

The columns are:

  • id and submitted_at, the submission's id and the time it arrived in UTC.
  • One column per field defined in the form builder, in builder order.
  • Any other field names that appeared in the submissions.
  • country and referer, the visitor's country and the page the form was sent from.

Values with several entries, such as checkboxes, are joined with a semicolon. File upload fields contain the file names, not the files or links to them.

To bring the file into Google Sheets:

  1. Open a spreadsheet, or create a new one.
  2. Choose File, then Import, then the Upload tab, and select the CSV file.
  3. Pick whether to create a new spreadsheet, insert a new sheet, or append to the current one.
  4. Confirm the import.

One detail of the export is deliberate. Any cell that begins with =, +, - or @ gets an apostrophe in front of it. Spreadsheets treat such cells as formulas, so a visitor could otherwise type a formula into your form and have it run when you open the file. This is known as formula injection, and the apostrophe prevents it.

The export is manual. FormDB has no scheduled exports, so if you want the sheet to stay current without clicking, use the integration. More on the inbox and export is in submissions inbox.

Option 2: connect the Google Sheets integration

The integration is available on paid plans. It is set up per form:

  1. Open the form and go to the Integrations tab.
  2. Choose Google Sheets and connect your Google account.
  3. Approve the permission request from Google.

The integration is switched on as soon as the connection completes. There is nothing to map.

What FormDB creates

FormDB creates a new spreadsheet in your Google Drive, named after your form, with a sheet called Submissions. The first row is a frozen, bold header:

Submitted at | Submission ID | name | email | message

After the two fixed columns there is one column for each field in your form builder, using the field's name.

You cannot point the integration at a spreadsheet that already exists, and you cannot choose a different tab. If you need the data in an existing workbook, either use CSV export or pull the data across inside Google Sheets with a function such as IMPORTRANGE.

What access FormDB asks for

The permission requested is Google's drive.file scope. It gives FormDB access only to files it creates or that you open with it. It does not allow FormDB to read the other files in your Drive.

How rows are written

Each new submission is added as one row at the bottom of the sheet.

  • Submitted at holds the time as an ISO 8601 timestamp, for example 2026-11-17T10:00:00.000Z.
  • Lists such as checkbox selections are joined with a comma and a space.
  • Values are written as plain text, not interpreted as formulas.
  • New fields get new columns. If a submission contains a field with no column yet, FormDB adds a header for it at the end of the row and fills it in.
  • File uploads are written as download links, one per line in the cell.

Things to know before you rely on it

  • Past submissions are not copied. Only submissions that arrive after you connect are written. To fill in the history, export a CSV and paste the older rows in.
  • Spam is not written. Submissions flagged as spam stay in the Spam folder and do not reach the sheet. Marking one as not spam later moves it to the inbox but does not send it to the sheet.
  • Do not rename the header cells. Columns are matched by the exact header text. If you change email to Email address, FormDB will not recognise the column and will add a new email column at the end. Keep the Submissions tab and its headers as they are, and do your formatting, formulas and charts in a separate tab that reads from it.
  • File links expire. The download links written into the sheet stop working 7 days after the row is added. For a working link after that, open the submission in the FormDB dashboard, which generates a fresh one each time.
  • Rows arrive shortly after the submission, not in the same instant. Delivery happens in the background once the visitor has received their response.

What happens when a delivery fails

If Google is unreachable or returns a temporary error, FormDB retries with increasing delays, up to 6 attempts in total over roughly a quarter of an hour. Errors that will not fix themselves, such as Google access having been revoked, fail straight away with a message asking you to reconnect.

The Integrations tab has a delivery log showing recent deliveries with their status and attempt count. There is also a Send test action, which writes the form's latest submission to the sheet again. It confirms the connection works, and it does mean that submission appears twice.

A submission that fails to reach the sheet is not lost. It is still in your FormDB inbox, and you can add it to the sheet from a CSV export.

Which option to choose

Use CSV export when you need a snapshot: a monthly report, a backup, or a one-time move into a sheet you already have.

Use the integration when people look at the sheet daily and expect it to be current. Many teams use both: connect the integration for new rows, and run one export at the start to bring in the history.

If your data belongs in a database-style tool instead, FormDB has similar integrations for Notion and Airtable.

Next steps

The Google Sheets documentation walks through the connection screen by screen. Plans that include integrations are listed on the pricing page, and you can create a free account to collect submissions and try CSV export before deciding.

Your form can be livebefore your coffee is cold.

Create a form, paste one URL and send yourself a test. The Free plan covers 250 submissions a month, with no credit card required.