Skip to main content
Best answer

Google contacts creates "Other contact"


I have a zap that ads new contacts to our Google Workspace. I need it to add the same contact to two different people’s address books.

The zap adds the contact to one account just fine, but in the other account, it places the contact in the “Other Contacts” category.

I duplicated the “add contact” step and just replaced the Google Account, so I cannot comprehend what went wrong, or what the difference between the two zap steps is…

Any thoughts?

Best answer by kpellegrBest answer by kpellegr

I noticed that the contacts *do* end up in the contacts folder. It is as if they go into “other contacts” first and that Google Contacts moves them to “Contacts” automatically.

I haven’t seen it “live” in action, but if I open the contacts the next day, they are in the “Contacts” folder.

 

I can’t seem to find any setting to change this; but I guess the problem is “solved” :-)

 

Thank you for following-up!

View original
Did this topic help you find an answer to your question?
This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

3 replies

Troy Tessalone
Forum|alt.badge.img+14

Hi @kpellegr 

Good question.

That may be a setting in the Google Account for how to handle new contacts.


chanelle
Forum|alt.badge.img+8
  • Zapier Staff
  • 628 replies
  • February 8, 2023

Hey there @kpellegr, I agree with Troy. It sounds like this may be a setting in your Google Account, were you able to check and confirm this? Let us know if the issue still persists! 


  • Author
  • Beginner
  • 1 reply
  • Answer
  • February 9, 2023

I noticed that the contacts *do* end up in the contacts folder. It is as if they go into “other contacts” first and that Google Contacts moves them to “Contacts” automatically.

I haven’t seen it “live” in action, but if I open the contacts the next day, they are in the “Contacts” folder.

 

I can’t seem to find any setting to change this; but I guess the problem is “solved” :-)

 

Thank you for following-up!