Google Sheets Integration

What Is the Google Sheets Integration?

Maverick exports project task data to Google Sheets — any grid view, with all visible columns, preserving the same row formatting (background colors, bold text, and italic text) that you see in the Maverick interface. A critical path task that displays in amber in Maverick shows up in an amber-tinted row in Google Sheets. A summary task that appears in bold in Maverick is bold in the sheet. No manual reformatting required.

Exports go directly to your Google Drive. Maverick creates a new spreadsheet, writes the header row from your column names, fills in the data rows, and applies all row-level formatting in a single operation. You can configure a Drive folder path — Maverick creates any missing folder segments automatically — and optionally override an existing sheet so the same spreadsheet is updated on every export rather than creating duplicates.

In the other direction, Maverick can import project tasks from any Google Sheet. The import reads the first row as column headers and maps each column to a task field by name. Any Google Sheet that your team already maintains — a list of milestones, a punch list, a status tracker — can become a Maverick project in seconds.

Service Account vs. OAuth2 — Which Should I Use?

Maverick supports two ways to authenticate with Google. You can configure one or both. The choice affects who owns the exported sheets and how exports are triggered.

Service Account

A service account is a non-human Google identity that belongs to your Google Cloud project. When Maverick exports using the service account, the sheet is created in the service account's Drive space and then shared with the requesting user so the sheet appears in their own Drive. This auth mode is best for scheduled, automated exports — the service account operates independently of any individual user's login session.

To configure the service account path, you provide three values from the JSON key file that Google generates: the service account's Client email, its Private key (the full RSA key block), and the Project ID of your Google Cloud project.

OAuth2 App

With OAuth2, each employee connects their personal Google account to Maverick. When they export, Maverick uses their own Google credentials — so the exported sheet lands directly in their own Drive with no sharing step. This is the simpler end-user experience for on-demand exports. The trade-off is that each user must complete a one-time consent flow, and exports can only happen when Maverick holds a valid refresh token for that user.

To configure the OAuth2 path, you register a web application in Google Cloud Console and provide the Client ID and Client secret. You also add the Maverick redirect URI so Google can return the authorization code after the user consents.

Both

You can configure both auth types simultaneously. Maverick will use the OAuth2 tokens when they are available for the current user, and fall back to the service account otherwise. This gives on-demand exports the direct-to-Drive experience while still allowing scheduled exports to run without any user session.

Get Your Service Account Credentials

The service account path requires three credential values: the service account's client email address, its RSA private key, and the Google Cloud Project ID. All three come from the JSON key file that Google Console generates when you create the key.

Step 1 — Create the Service Account

1. In Google Cloud Console, open IAM & Admin → Service Accounts in the left menu.
2. Click Create Service Account at the top of the page.
3. Enter a name such as Maverick Sheets Export. The service account ID and email address are auto-generated from the name — make a note of the email (it ends with @your-project-id.iam.gserviceaccount.com).
4. Click Create and Continue.
5. In the Grant Access step, assign the role Editor (or at minimum the Google Sheets Editor and Drive File roles). Click Continue, then Done.

Step 2 — Download the JSON Key File

1. On the Service Accounts list, click the email address of the account you just created.
2. Click the Keys tab.
3. Click Add Key → Create new key.
4. Select JSON and click Create.
5. A .json file downloads immediately. Store it securely — this is the only time Google will give you the private key.

Step 3 — Extract the Three Values

Open the downloaded JSON file in a text editor. It looks like this:

{
  "type": "service_account",
  "project_id": "my-gcp-project-id",
  "private_key_id": "abc123...",
  "private_key": "-----BEGIN RSA PRIVATE KEY-----\nMIIEo...\n-----END RSA PRIVATE KEY-----\n",
  "client_email": "maverick-sheets@my-gcp-project-id.iam.gserviceaccount.com",
  ...
}

• Copy the client_email value → paste into Client email in Maverick.
• Copy the entire private_key value including the -----BEGIN RSA PRIVATE KEY----- and -----END RSA PRIVATE KEY----- lines → paste into Private key in Maverick. The key contains literal \n sequences in JSON — Maverick handles these automatically.
• Copy the project_id value → paste into Project ID in Maverick.

Configure the Integration in Maverick

With your credentials in hand, open the Google Integration dialog in Maverick. Go to the Admin section and select Integrations → Google. The dialog shows three sections: Service Account, OAuth2 App, and Personal Google Account.

Auth Type

The Auth type dropdown at the top controls which credential sections are active. Choose Service Account to use only server-to-server authentication, OAuth2 App to use only personal account authentication, or Both to enable both simultaneously. Only administrator accounts need to configure this dialog — individual users do not need access to the admin credentials.

Service Account Fields

• Client email — the service account email address ending in @your-project-id.iam.gserviceaccount.com. Paste from the client_email field in the JSON key file.
• Private key — the full RSA private key block. Paste the entire value from the private_key field in the JSON file, including the -----BEGIN RSA PRIVATE KEY----- header and footer lines. The field accepts multi-line input.
• Project ID — the Google Cloud Project ID. Paste from the project_id field in the JSON file, or copy it from the project selector in Google Cloud Console. This is a short identifier like my-gcp-project-id, not the project's display name.

The private key and client secret fields are write-only — once saved, the stored value is not displayed again. Leave these fields blank when saving if you only want to update other fields.

OAuth2 App Fields

• Client ID — the OAuth client ID ending in .apps.googleusercontent.com. Paste from the Google Cloud Console credentials dialog.
• Client secret — the short alphanumeric secret. Paste from the credentials dialog. Leave blank if only updating the Client ID.
• Redirect URI — this field is pre-filled and read-only. Copy it from here and add it to the Authorized Redirect URIs list in Google Cloud Console when setting up the OAuth client.

After entering all credentials, click Save. Maverick encrypts and stores all sensitive values. Use the Open Google Console button in either section to jump directly to the Google Cloud Console in a new browser tab.

Export to Google Sheets

With credentials configured, the Google Sheets export is available from the same place as other Maverick exports. Right-click any row in a project tasks grid to open the context menu and choose Export → Google Sheets. You can also find the same option in the File menu in the Maverick application ribbon.

Before exporting, configure the view to match the output you want. Apply a filter, set a sort order, show or hide columns. The export captures the current view exactly as displayed — only visible columns are written, in the order they appear, with all row-level formatting intact.

Export Options

• File name — the title of the Google Sheet that will be created or updated. Defaults to the current view name.
• Add today's date as a suffix — appends the current date to the file name, creating a new dated snapshot on each export rather than overwriting the previous one. Useful for weekly status reports where you want a full history.
• Drive folder — the folder path inside your Google Drive where the sheet should be stored. Enter a folder name or a path such as Clients/Acme/2026. Maverick creates any missing folder segments automatically. Leave blank to save directly to the root of My Drive.
• Override existing sheet if folder and name match — when checked, Maverick finds an existing sheet with the same name in the same folder and overwrites it with the new data instead of creating a duplicate. When unchecked, a new sheet is always created.
• Remember these settings — saves the current options as the default for this view. Hold Alt and trigger the export to reopen this dialog even when settings are remembered.

Click Export. Maverick contacts Google, creates or updates the sheet, writes the header row and all data rows, applies row-level formatting (background color, text color, bold, italic), and returns the URL. The sheet opens in a new browser tab.

The Google Sheet Result

The exported sheet contains one row per task with all visible columns from the Maverick grid. Row formatting from Maverick is applied: summary rows appear in bold, critical path tasks in amber tinting, and any custom row colors from your view are preserved. The Name column is left-aligned; other columns follow the default Sheets alignment.

Dates are written as plain text strings in ISO format so they sort and filter correctly in Google Sheets without requiring a format conversion step. Numeric columns — Duration, Actual Work, Percent Complete — are written as numbers so Sheets formulas and charts read them directly.