Google Contacts fields that sync to Notion

2sync syncs the standard Google Contacts field set to Notion: names (full, first, last), up to three email addresses and three phone numbers each with its own label field, addresses, company, job title, birthday, nickname, photo, contact labels and groups, notes, and the contact's own URL.

Seven fields are mapped for you when you create the automation, and 34 more are available under + Add Field. Direction is set per field, and 2sync preselects a sensible default for each: two-way, one-way to Notion, or one-way to Google Contacts. Change any of them in field mapping.

Which of these fields survive a CSV import or a Zapier workflow instead of a two-way sync is covered in how to sync Notion with Google Contacts.

Synced fields

Mapped by default

These seven rows are already in the field mapping table when you create a Google Contacts automation.

Labels (Relation) matches on the group name, so it needs a Notion database of labels to point at. Labels (Multi-Select) needs nothing beyond a Multi-select property.

Available under + Add Field

Click + Add Field in the field mapping section for the other 34 Google Contacts fields, listed here as the dropdown lists them.

Each one arrives set to one-way into Notion, and you can switch it to two-way or one-way to Google Contacts once the row is in the table. Person ID is the exception: its direction controls stay grayed out, so Google's own identifier only ever reads into Notion.

Relation fields

Map Company to a relation instead of a text or select property when you keep a separate Notion database of organizations. See relations for how the matching works.

Metadata fields

Trigger deletion on Google Contacts deletes the contact when the mapped checkbox is checked. See delete behavior before you map it.

Name fields

The Full Name field maps to Notion's Title property, the main name of each database page. The First Name and Last Name fields sync separately as Rich Text properties.

Editing the full name in Notion updates the individual name fields in Google Contacts. Editing first or last name separately updates the full name accordingly.

Email

Google Contacts supports up to three email addresses per contact. The primary email maps to the main Email property, and additional emails map to Email 2 and Email 3 as separate properties.

Each address carries its own label in Google, and that label is a field of its own. Email 1 Label, Email 2 Label and Email 3 Label map to Text properties, so Home, Work or anything custom arrives in Notion alongside the address.

The primary email address is also used for attendee relation matching in calendar syncs. When linking calendar events to contacts, 2sync matches attendees by their primary email.

Phone

Google Contacts supports up to three phone numbers per contact. The primary number maps to Phone, the extras to Phone 2 and Phone 3.

Each of the three takes either a Notion Phone Number property or a Text property, so pick Text when you would rather keep extensions, notes or non-standard formats exactly as typed.

The type label is a field of its own, not something the sync drops. Phone 1 Label, Phone 2 Label and Phone 3 Label map to Text properties and bring Mobile, Home or Work across with the number.

Phone numbers sync with their formatting preserved.

Address

The first address is broken out component by component. Address 1 gives you Line 1, Line 2, City, State/Region, Zip Code, Country and Label as separate fields, so you can map the city or the country to its own Notion property and then filter, group or sort by it.

Full Address 1, Full Address 2 and Full Address 3 hold the same three addresses as combined strings. Map those when one Text property is all you need.

The second and third addresses are not broken out the same way. Address 2 and Address 3 expose only Country and Label, so anything more detailed than that has to come from Full Address 2 and Full Address 3.

Company and job title

Company maps to a Select or Text property, and to a Relation when you keep a separate Notion database of organizations. Job Title maps to Text. Both are especially useful for CRM workflows. Filter or group your Notion database by company to see all contacts at an organization. See the Notion CRM guide for setup ideas.

Birthday

The Birthday field syncs as a Date property. Google Contacts stores birthdays with an optional year. If no year is set in Google, the date syncs to Notion with the year omitted.

Nickname

The Nickname field maps to Rich Text. This is the informal name stored in Google Contacts, separate from the Full Name, First Name, and Last Name fields.

Photo

Photos sync bidirectionally as a Files property. Profile pictures update automatically when changed in either Google Contacts or Notion. Large images are optimized during sync to keep your Notion database fast.

Labels and groups

Google Contact labels (also called groups) sync as a Multi-select property. Labels created in either Google Contacts or Notion sync bidirectionally. Adding a new label in Notion creates a matching group in Google Contacts.

Labels can also map to a Relation instead, matched on the group name, if you keep your labels as their own Notion database. Both rows are in the field mapping table by default, so pick the one you want and leave the other unmapped.

Use labels for organizing contacts by category (Clients, Vendors, Personal, VIP) and for filtering which contacts sync to keep your Notion database focused.

Contact limits

What should I do next?

Now that you know which fields sync:

1. Set up your Google Contacts sync if you haven't connected yet
2. Build a Notion CRM with your contacts
3. Configure sync direction per field
4. Set default values for empty fields

Related

• Google Contacts sync for the full setup guide
• Create a Notion CRM for a step-by-step CRM setup guide
• Notion property types for supported property formats
• Default values for setting fallback values on empty fields
• Relations for linking contacts to calendar events and projects
• Sync direction for per-field data flow control

FAQ