Start typing to search...

↑↓ Navigate Enter Select Esc Close

Google Sheets integration

The Google Sheets integration appends one row to a selected worksheet when a Kali Forms submission is processed.

What you need
  • a Google account that can access the destination spreadsheet;
  • a Google Cloud project where you can configure the OAuth consent screen and credentials;
  • the Google Sheets API and Google Drive API enabled in that project;
  • an OAuth 2.0 Web application client ID and client secret;
  • permission to approve the scopes requested by the installed Kali Forms build;
  • a spreadsheet containing a worksheet/tab and a header row that matches the intended mappings.

Google’s official workflow covers project, consent screen, client, and credential creation in Create access credentials.

Understand the requested access

Source inspection of Kali Forms Pro 2.0.0 confirmed that this integration requests:

  • https://www.googleapis.com/auth/spreadsheets — read, create, edit, and delete all Google Sheets spreadsheets;
  • https://www.googleapis.com/auth/drive — read and manage all files in the authorized user’s Google Drive.

Google classifies these as sensitive and restricted broad scopes. See the official Sheets scope list and Drive scope guidance. This build does not request the narrower drive.file scope.

Use a dedicated organizational Google account with access only to the spreadsheets the site needs. Your organization may require administrator approval or Google app verification before broad scopes can be authorized.

Create the Google OAuth client
  1. Sign in to Google Cloud Console with an authorized administrator or project owner.
  2. Create or select a project dedicated to this WordPress integration.
  3. Open APIs & Services > Library.
  4. Enable Google Sheets API.
  5. Enable Google Drive API. Kali Forms uses Drive to discover spreadsheets.
  6. Configure the Google Auth platform or OAuth consent screen:
    • enter the app name and support contact;
    • choose Internal only when every authorized user belongs to the same eligible Google Workspace organization; otherwise choose External;
    • declare the Sheets and Drive scopes listed above;
    • add the account that will connect Kali Forms as a test user while the app is in Testing.
  7. Open Clients or Credentials, select Create client, and choose Web application.
  8. In Kali Forms, open Kali Forms > Google Sheets and copy the displayed Redirect URI.
  9. Add that URI to the OAuth client’s Authorized redirect URIs exactly, including scheme, host, path, and query string.
  10. Create the client and copy its Client ID and Client secret.

Google requires the authorization request’s redirect URI to match a configured URI exactly. See OAuth 2.0 for web-server applications.

On the local verification site, Kali Forms displayed:

https://website.com/wp-admin/edit.php?post_type=kaliforms_forms

Do not reuse that value on another site. Copy the URI displayed by the actual production or staging installation. Production OAuth redirects should use HTTPS.

If the consent configuration remains in Testing, Google limits it to listed test users and may expire authorizations after seven days. Review Google Auth platform publishing status.

Connect Kali Forms to Google
  1. In WordPress, go to Kali Forms > Google Sheets.
  2. Paste the OAuth Client ID into Client ID.
  3. Paste the OAuth Client secret into Client secret.
  4. Leave Enable debug log disabled initially. Enable it only for controlled troubleshooting because logs may expose spreadsheet or submission metadata.
  5. Select Save.
  6. Use the connection/authorization control that appears after valid credentials are saved.
  7. Sign in with the dedicated Google account.
  8. Verify the project/app name and requested scopes on Google’s consent screen, then approve only if they match the intended integration.
  9. Return to WordPress and confirm the page reports the Google account as connected.
Prepare the spreadsheet
  1. Create or open the destination spreadsheet using the connected Google account.
  2. Add a dedicated worksheet/tab, for example Responses.
  3. Add one header in row 1 for each value you will map, such as Submitted at, Email address, and Message.
  4. Give the connected account Editor access to the spreadsheet.
  5. Avoid merged header cells and duplicate headers.

Kali Forms appends rows to the selected tab beginning at its A1 range. Google documents request limits and retry guidance in the Sheets API usage limits.

Map form fields to columns
  1. Go to Kali Forms > All forms and edit the form.
  2. Open Integrations > Google sheets.
  3. Enable Google Sheets integrations.
  4. Select the spreadsheet returned from the connected Google Drive account.
  5. Select the worksheet/tab.
  6. For each spreadsheet column, select the Kali Forms field whose submitted value should be appended.
  7. Map only fields needed in the spreadsheet. Treat submissions as personal data when they contain names, email addresses, phone numbers, or message content.
  8. Wait for autosave, reload the builder, and confirm the spreadsheet, tab, and mappings remain selected.
Verify safely
  1. Use a staging form and synthetic data.
  2. Note the last populated row in the selected worksheet.
  3. Submit the form once.
  4. Confirm exactly one new row appears and each value is under the correct header.
  5. Submit a second value containing safe punctuation and non-ASCII characters to check encoding.
  6. Confirm no unexpected spreadsheet or Drive file was modified.
  7. Delete the synthetic rows and any saved Kali Forms entries after testing.

Do not use a live customer submission as the first test.

Disconnect and revoke access
  1. Disable the form-level integration before revoking access so new submissions do not repeatedly fail.
  2. Use the Google Sheets disconnect control in Kali Forms to remove its locally stored OAuth token.
  3. In the Google account, remove the app’s third-party access.
  4. In Google Cloud Console, rotate or delete the OAuth client secret if it was exposed or the integration is retired.
  5. Remove the dedicated account’s access to the spreadsheet when it is no longer needed.

The client secret and OAuth refresh token must never appear in screenshots, repositories, logs, or support messages.

Was this page helpful?
0 0