🔓 Unlock all 10,000+ workflows & prompts free Join Newsletter →
✅ Full access unlocked — explore all 10,000 AI workflow and prompt templates Browse Templates →
Home › n8n › Workflow
January 22, 2026

Keep Notion and Google Contacts in sync, always

Keep Notion and Google Contacts in sync, always - n8n workflow automation template
Lisa Granqvist Partner Workflow Automation Expert
Keep Notion and Google Contacts in sync, always - n8n workflow automation template
Get a free AI assessment → Get a free AI assessment → ⬇️ Use template

Your contacts are never “done.” Someone changes a phone number, a client updates their company name, a teammate adds a new lead in the wrong place, and suddenly you’re stuck reconciling Notion vs. Google Contacts again. Duplicates creep in. Old data lingers. Trust drops fast.

This Notion Google Contacts automation hits service providers hardest (client details have to be right), but ops leads and small team owners feel it too. You get one reliable contact source, without the weekly cleanup session.

This guide walks you through what the workflow does, what you need, and how to tailor the sync rules (including deletions) so it matches how your team actually works.

How This Automation Works

Here’s the complete workflow you’ll be setting up:

n8n Workflow Template: Keep Notion and Google Contacts in sync, always

Why This Matters: Contact Data Drifts (Quietly)

Most contact “systems” start as good intentions. You capture a lead in Google Contacts because it’s fast. Later, you enrich it in Notion because that’s where your client notes live. Then the data splits. One tool has the right email, the other has the right phone number, and neither one is fully trustworthy. It’s not just annoying. It slows follow-ups, creates awkward outreach (“wrong name, sorry”), and turns every CRM-ish task into detective work.

It adds up fast. Here’s where it tends to break down:

  • New contacts get added in two places, so duplicates multiply over time.
  • Updates happen in the “wrong” tool, and nobody remembers to copy changes across.
  • Teams lose confidence and stop maintaining the database at all, which makes it worse next month.
  • Deletions are inconsistent, so you end up with ghost records that keep resurfacing.

What You’ll Build: A Two-Way Notion ↔ Google Contacts Sync

This workflow keeps a Notion contacts database and Google Contacts aligned automatically. You start with an initial import that pulls existing Google Contacts into Notion, so you aren’t rebuilding your list from scratch. After that, the automation listens for changes on both sides. When a contact gets created or updated in Google, the matching Notion page is created or updated to mirror it. When you edit a Notion record (like a company name, phone, or email), the corresponding Google Contact is updated as well. Deletions can also sync both ways, although you can disable that behavior if you’d rather archive instead.

The workflow begins with a “get changes” style trigger (webhooks and polling patterns) so it knows when something changed. It then filters and matches records, merges fields safely, and writes the final version back to the other system. That means you stop doing the tedious compare-and-copy routine.

What You’re Building

Expected Results

Say your team adds or edits about 10 contacts a week. Manually, it’s maybe 5 minutes to update Google Contacts and another 5 minutes to mirror the change in Notion, plus extra time when duplicates show up. That’s around 2 hours of small, annoying work each week. With this automation, you update a contact once (in either tool), then wait a minute or two for the sync to complete. The busywork mostly disappears.

Before You Start

  • n8n instance (try n8n Cloud free)
  • Self-hosting option if you prefer (Hostinger works well)
  • Notion for your contacts database and properties.
  • Google Contacts to store contacts in Google Workspace.
  • Google credentials (set up in n8n’s Credentials tab)

Skill level: Beginner. You’ll connect accounts and map a few fields, but you won’t need to write code.

Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).

Step by Step

An initial import gets you to “baseline.” The workflow pulls your existing Google Contacts and creates matching pages in Notion, so you start from a synced state instead of a half-migrated mess.

Changes are detected from both sides. A webhook-style trigger and API checks (via HTTP Request patterns) watch for new contacts, edits, and deletions in Google Contacts and Notion.

Matching, filtering, and field prep happen in the middle. The workflow uses filters and conditional logic (If nodes) to decide what to sync, optionally by label. It then merges fields and standardizes them with Set/Edit Fields so you don’t overwrite good data with blanks.

Updates get written back to the other tool. If Google changes, Notion updates. If Notion changes, Google updates. If a record is deleted and deletion sync is enabled, the corresponding item is removed on the other side too.

You can easily modify deletion behavior to archiving based on your needs. See the full implementation guide below for customization options.

Troubleshooting Tips

  • Google Contacts credentials can expire or need specific permissions. If things break, check n8n’s Credentials section and your Google account’s connected app access first.
  • If you’re using Wait nodes or external processing, timing can vary. Bump up the wait duration if downstream steps fail because a contact hasn’t fully propagated yet.
  • Notion property names must match what the workflow expects. If a field “doesn’t update,” open the Notion database, confirm the property type (text vs. phone vs. email), and then re-map that field in the Set/Edit Fields step.

Next Steps

If you like the idea of contacts syncing but you want more control over how labels map into Notion, Notion to Google Contacts, labels and contacts stay tidy is a solid companion workflow for keeping segmentation clean.

When your team is capturing leads from chats, Telegram to Notion, file everything without the mess helps you log context quickly so your contact records aren’t just names and numbers.

For teams using Notion as the hub, task sync is the next bottleneck. Keep Notion and Todoist tasks in sync, always is a practical add-on when follow-ups need to become real tasks automatically.

If you manage course or training operations, data drift happens there too. Canvas meets Notion for always current assignments keeps assignment info current so nobody is working from last week’s version.

Finally, if your contacts end up tied to invoicing or CRM records, consider connecting the same patterns to your back office system (many teams do this with Odoo) so contact updates don’t stop at the address book.


Quick reference:

Quick Answers

What’s the setup time for this Notion Google Contacts automation?

About 30 minutes if your Notion database is ready.

Is coding required for this contact sync?

No. You’ll mainly connect accounts and map fields between Notion and Google Contacts.

Is n8n free to use for this Notion Google Contacts workflow?

Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Notion and Google usage (usually already part of your stack).

Where can I host n8n to run this automation?

Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.

Can I modify this Notion Google Contacts workflow for different use cases?

Yes, but be intentional. You can keep updates two-way while disabling the deletion-related nodes so removals don’t cascade. Common customizations include syncing only a specific Google label, changing which Notion properties map to Google fields, and adding an “Archived” checkbox in Notion instead of deleting records.

Why is my Google Contacts connection failing in this workflow?

Usually it’s expired Google credentials or missing permissions in the Google account you connected. Re-authenticate the Google credential inside n8n, then retry the failing node. If you’re syncing a lot at once, you may also be hitting rate limits, so reduce batch sizes or add a short wait before writing updates.

What volume can this Notion Google Contacts workflow process?

Most small teams can run hundreds of contact updates a day without thinking about it.

Is this Notion Google Contacts automation better than using Zapier or Make?

For two-way contact sync, n8n is often a better fit because you can do matching logic, branching, and merges without paying extra for every path. Self-hosting is another big deal if you expect lots of updates, since you’re not boxed into a task quota the same way. Also, n8n’s HTTP Request flexibility makes “odd edge cases” fixable, which is honestly where sync automations live or die. Zapier or Make can still work if you want a very simple, mostly one-way sync and you prefer a more guided UI. If you’re unsure, Talk to an automation expert.

Once this is running, contacts stop being a recurring cleanup project. You update details where it’s convenient, and the workflow keeps the rest aligned.

Need Help Setting This Up?

Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.

Talk to Automation Expert →

Lisa Granqvist

Workflow Automation Expert

Expert in workflow automation and no-code tools.

×

Use template

Get instant access to this n8n workflow Json file

Copy and import json workflow into your n8n workflow

💬
Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.

Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.