Integration · Feedback in

Your Google Sheet of feedback, flowing in.

Connect Google Sheets and the doc the team already maintains becomes a live source. Same auto-mapping as CSV, same pipeline, no copy-paste.

How it connects

Four steps to a live source.

Sync the voice-of-customer spreadsheet your team already maintains.

Connect with OAuth.

Pick the sheet.

Google Picker. Choose one sheet, confirm.

Map the columns.

Same auto-detection as CSV. Adjust if needed; preview before importing.

Review and import.

See what’s going to land before it commits.

What you get

One mapper across CSV and Sheets.

The same 85%-confidence column detector runs on both — anything CSV recognizes, Sheets recognizes.

Picker-scoped access.

Annsa can only read files you explicitly pick. Nothing else in your Drive.

Encrypted refresh tokens.

Tokens stored Fernet-encrypted, auto-refresh transparent.

The proof

drive.file OAuth scope means Annsa only sees what you select via Google Picker — no broader Drive access.

OAuth · drive.file

Only the selected sheet enters Annsa

Google Pickerselected filetoken encrypted

sync ready

What access does Annsa have to my Drive?

Only the files you explicitly pick via Google Picker. The OAuth scope is drive.file — narrow by design.

How does Google Sheets column mapping work?

Annsa uses the same auto-detection as its CSV importer. Recognized formats skip mapping; otherwise the wizard walks you through it.

What happens if I disconnect Sheets?

Sync stops. Feedback Annsa already imported from the Google Sheet is preserved.

Are Google Sheets tokens encrypted?

Yes — Annsa stores Google refresh tokens Fernet-encrypted at rest and auto-refresh transparently.

annsa

drive.file scope, Fernet-encrypted tokens — Annsa only ever sees the sheet you pick.