Google Sheets
Sync contacts from a spreadsheet into Lemu, and push contact updates back to it
The Google Sheets integration is a data-source integration: it keeps a Lemu contact list in sync with rows in a spreadsheet, and lets you push a contact's changes back to the sheet. Unlike Slack, Jira, and Google Calendar, it isn't used from a journey node — it runs in the background.
Connecting#
- On Settings → Integrations, click Connect on the Google Sheets card.
- A popup opens Google's OAuth consent screen. Sign in and approve access.
- Pick a spreadsheet — search by name from the spreadsheets visible to the connected Google account.
- Map columns — after picking a spreadsheet (and sheet, if it has more than one tab), Lemu reads its header row and proposes a best-guess mapping from column names to contact fields (e.g. a column literally named "Phone" or "Email" is matched automatically). Review and adjust the mapping, then confirm.
A phone column mapping is required — a contact with no phone number can't be called. Every other field is optional.
Once confirmed, Lemu creates a contact list named {Spreadsheet title} — {Sheet name} and starts syncing into it.
How sync works#
New rows
Lemu registers a trigger on the sheet that fires as soon as a new row is added, so new contacts show up close to real time.
Edited rows
Row-added triggers can't detect an existing row's values changing, so every 15 minutes Lemu also does a full re-read of the sheet, which picks up both new rows and edits to existing ones. This is a backstop, not the primary path — most new contacts arrive via the trigger well before the next poll.
Outbound: Lemu → Sheet
From a contact's detail page, you can manually push its current field values back to the mapped row in the sheet. This is a one-off, user-triggered action — Lemu doesn't write back automatically as you edit a contact.
Manual resync
You don't have to wait for the next scheduled poll — trigger an immediate resync for the integration from the Integrations page if you need the latest sheet data right away.
If Lemu can't read the sheet#
If the connected account doesn't have access to the sheet you're trying to pick or map (for example, the OAuth grant didn't include the right Sheets scope), reconnect the integration — see Disconnecting and reconnecting — which forces a fresh consent screen where you can grant the missing permission.
Disconnecting#
Click Disconnect on the Google Sheets card in Settings → Integrations. This stops the sync immediately and revokes Lemu's access to the spreadsheet — the contact list and its existing contacts stay in Lemu, but they'll no longer receive updates until you reconnect and re-select the sheet.