How it works
Google Sheets integration lets you connect a live spreadsheet as your data source. When you merge, Mergram fetches the latest data from the sheet — no need to re-upload a file every time your data changes.
Why use Google Sheets?
Google Sheets keeps your data live. Team members can update the spreadsheet in real time, and the next merge automatically picks up the changes. This is ideal for recurring merges like weekly invoices or monthly reports.
Prerequisites
- A Google account with access to the spreadsheet you want to use
- A Google Sheet with data organized in rows and columns (first row = headers)
- A Mergram account
Getting started
-
Connect your Google account
In the editor, click Use Google Sheet. You’ll be prompted to sign in with Google and grant Mergram access to your spreadsheets. Mergram uses the
drive.filescope — it can only see spreadsheets you explicitly select. -
Select a spreadsheet
Browse your Google Drive and pick the spreadsheet you want to use. Mergram shows a preview of the available sheets.
-
Choose a worksheet tab
If the spreadsheet has multiple tabs, select the one containing your data. Mergram reads the first row as column headers.
-
Merge as usual
Place fields on the canvas and merge. The data is always fetched live from the sheet at merge time.
Can't find your spreadsheet?
Make sure it’s shared with the Google account you connected, or that the spreadsheet isn’t restricted to specific people. Spreadsheets set to “Anyone with the link” are also accessible.
Sheet Picker & Worksheet Selection
- Google Sheets support — Full support for multi-tab Google Sheets
- Tip dialog — If a spreadsheet has multiple tabs, a picker dialog appears automatically
- Tab selection — Each tab shows its name, row count, and column count
- Live data — Always reads the latest data from the sheet at merge time
Keep your header row first
Mergram always uses the first row as column headers, just like with uploaded files. Avoid blank rows at the top of your sheet and ensure column headers match your field names for auto-mapping.
Permissions & security
- Per-file access — Mergram uses Google’s
drive.filescope. It can only access spreadsheets you explicitly select. It never modifies your data. - OAuth tokens — Your Google OAuth token is encrypted (AES-256-GCM) and stored securely.
- Disconnect anytime — Revoke access from Settings → Connections at any time.
- Per-team connections — Each team can have one Google Sheets connection. All team members use the same connection.
Token expiry
Google OAuth tokens may expire or be revoked. If you see an authentication error when loading a sheet, reconnect your Google account from Settings → Connections.
Best Practices
- Use a dedicated data tab — Keep merge data on its own tab, separate from calculations or notes
- Protect the header row — Lock the first row in Google Sheets to prevent accidental changes to column headers
- Share with team — Ensure the Google Sheet is accessible to the account connected to Mergram. If multiple team members edit the sheet, use Google Sheets’ sharing features
- Use data validation — Apply data validation in Google Sheets to ensure values are in the correct format before merging
Limitations
- One connection per team — All team members share the same Google account connection
- Read-only — Mergram cannot write data back to Google Sheets (though the OAuth scope technically permits file-level access)
- No auto-merge scheduling — Merges must be triggered manually or via the API. Mergram does not automatically merge on a schedule when the sheet changes
- Google API limits — Very large spreadsheets (tens of thousands of rows) may take longer to fetch due to Google API rate limits