Google Sheets export

Append Nimriz event batches to a customer-owned Google Sheet for operational reporting.

Availability: Google Sheets setup is available on Professional and Enterprise plans.

Requirements

• A Professional plan or higher.
• A Google account with edit access to the spreadsheet.
• The exact target tab name and a deterministic column list.

Google Sheets setup uses managed Google authorization. Complete the destination fields shown in the dashboard. When Select spreadsheet appears, the connection uses Google Picker and the per-file drive.file scope so you can choose one spreadsheet that the connected Google account can edit. Existing configured connections created under the earlier authorization contract keep their saved spreadsheet until the connection is reconnected or revoked. Provider tokens are stored separately from destination configuration and encrypted at rest.

Prepare the sheet

1. Create or open the destination spreadsheet.
2. Choose the target tab and record its exact name.
3. Leave row 1 empty so the first successful test can create the configured header, or pre-create a header that exactly matches the configured columns.

The default column order is:

event_id,event_type,timestamp,short_url,conversion_type,conversion_value,conversion_currency,country,utm_source,utm_campaign

You may configure another ordered column list. Values are read from the mapped Nimriz event payload in that exact order.

Connect Google Sheets in Nimriz

1. Go to Integrations›Destinations›Browse catalog and choose Google Sheets.
2. Complete the destination fields shown, including the Tab name and columns.
3. Select Save destination. Nimriz creates the destination disabled.
4. Open the destination and select Connect provider.
5. Authorize the Google account that can edit the spreadsheet. For a per-file connection, the consent request is limited to files you select for Nimriz.
6. If Select spreadsheet appears, use it to choose one editable Google Sheet in Google Picker.
7. Select Send test event. The test reads row 1, initializes an empty header when needed, and appends a real sample row.
8. After the test succeeds, turn on the destination enable switch.

Enablement requires healthy Google authorization, a valid configured spreadsheet, and a successful test for the latest tab and column configuration. Per-file connections also require a current Picker selection.

Changing the spreadsheet, tab, columns, or other stored connector configuration requires another successful test. Reconnecting also clears prior test readiness. When Select spreadsheet appears after reconnect, choose the Sheet again before testing and enabling.

Delivery behavior

Nimriz appends event batches with the Sheets API using raw values and inserted rows. It never recreates a deleted spreadsheet or tab. A non-empty header must exactly match the configured columns; Nimriz fails safely instead of silently changing the sheet. Google's spreadsheets.values.append reference documents the underlying append operation.

Delivery is at least once. An ambiguous timeout can produce a duplicate row, so use event_id when downstream processing needs deduplication.

Google applies per-minute read and write quotas to the Sheets API. Nimriz treats quota responses as retryable and applies bounded backoff. Review Google's current Sheets API usage limits when planning a high-volume export.

Data and privacy

For this destination, Nimriz stores the configured spreadsheet identifier, the configured tab name, and the ordered columns. Per-file connections also store the server-verified spreadsheet title and selection details. Nimriz reads the selected tab's header row and appends only the mapped Nimriz event rows you configured.

For a per-file connection, the short-lived Google access token used by Picker stays in the authenticated dashboard session and is not stored in browser storage. Refresh tokens never reach the browser. Nimriz MCP tools do not expose Sheet contents or configuration, Google OAuth credentials, provider payloads, or provider errors.

Nimriz does not use Google Workspace data to create, train, or improve generalized AI or machine learning models, and does not transfer that data to third-party AI or machine learning providers for those purposes. See the Privacy Policy for the complete Google Limited Use, storage, and deletion disclosures.

Revoke or remove access

Revoking the Google connection deletes the encrypted Google OAuth token material stored by Nimriz, clears the selected spreadsheet, invalidates test readiness, and disables the destination. Rows already written to the Sheet stay in the customer-owned spreadsheet until you change or delete them in Google.

If Nimriz cannot confirm provider-side revocation, remove Nimriz from your Google Account permissions as well.

Troubleshooting

• Header mismatch: make row 1 exactly match the configured columns, including order and spelling.
• Spreadsheet selection required: when Select spreadsheet is available, use it to choose one editable Google Sheet.
• Spreadsheet or tab not found: review the spreadsheet controls shown for the destination and verify the exact tab name. If Select spreadsheet is available, choose the Sheet again.
• Spreadsheet cannot be selected: confirm that the connected Google account can edit it and that it is a Google Sheets file.
• Authorization needs attention: reconnect Google from the destination detail page. If Select spreadsheet appears, choose the Sheet again, then run another test before enabling.