HumDay

Copies an "Other contact" in Google People

A documented Google People operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.

Automate this

What this operation does

Copies an "Other contact" to a new contact in the user's "myContacts" group Mutate requests for the same user should be sent sequentially to avoid increased latency and failures.

  • POSTChanges data · otherContactspeople.googleapis.com/v1/{resourceName}:copyOtherContactToMyContactsGroup

How HumDay uses it

  1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
  2. The contract names it. Before anything is built, you see exactly which Google People operations the program may use, and this is one of them.
  3. You approve access. Because this one changes data, it cannot run until you have explicitly granted it.

Other Google People operations

All 23 Google People operations

Questions

Can HumDay copies an "other contact" in Google People?
Yes. This operation is published in Google People's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
Will this change my Google People data?
Yes — this is a POST operation, so it changes something in Google People. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
Do I need to write code?
No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Google People account.

Where this came from

Read from a published API description for Google People at people.googleapis.com/$discovery/rest?version=v1. The description above is the provider’s own wording, not ours. Last published 2023-04-21.