Can HumDay connect to Google People?

Yes. HumDay reads Google People's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 23 operations are documented.

Do I need to write code to automate Google People?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Google People account.

What can HumDay do in Google People?

13 of the 23 documented operations change something in Google People, and 10 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Google People account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Google People is held behind that approval.

Automate Google People

HumDay reads Google People’s own published API description and derives 23 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.

What Google People is

Provides access to information about profiles and contacts.

API host: people.googleapis.com

What HumDay can do in Google People

13 documented operations change something in Google People.

POSTCreate a new contact group owned by the authenticated user./v1/contactGroups
POSTCreate a batch of new contacts and return the PersonResponses for the newly Mutate requests for the same user should be sent sequentially to avoid increased latency and failures./v1/people:batchCreateContacts
POSTCreate a new contact and return the person resource for that contact./v1/people:createContact
POSTCopies 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./v1/{resourceName}:copyOtherContactToMyContactsGroup
DELETEDelete an existing contact group owned by the authenticated user by specifying a contact group resource name./v1/{resourceName}
PUTUpdate the name of an existing contact group owned by the authenticated user./v1/{resourceName}
POSTModify the members of a contact group owned by the authenticated user./v1/{resourceName}/members:modify
POSTDelete a batch of contacts./v1/people:batchDeleteContacts
POSTUpdate a batch of contacts and return a map of resource names to PersonResponses for the updated contacts./v1/people:batchUpdateContacts
DELETEDelete a contact person./v1/{resourceName}:deleteContact
PATCHUpdate contact data for an existing contact person./v1/{resourceName}:updateContact
DELETEDelete a contact's photo./v1/{resourceName}:deleteContactPhoto
PATCHUpdate a contact's photo./v1/{resourceName}:updateContactPhoto

What HumDay can read from Google People

These are the operations a schedule or a trigger can watch.

GETProvides a list of contacts in the authenticated user's other contacts that matches the search query./v1/otherContacts:search
GETProvides a list of contacts in the authenticated user's grouped contacts that matches the search query./v1/people:searchContacts
GETProvides a list of domain profiles and domain contacts in the authenticated user's domain directory that match the search query./v1/people:searchDirectoryPeople
GETList all contact groups owned by the authenticated user./v1/contactGroups
GETList all "Other contacts", that is contacts that are not in a contact group./v1/otherContacts
GETGet a list of contact groups owned by the authenticated user by specifying a list of contact group resource names./v1/contactGroups:batchGet
GETProvides a list of domain profiles and domain contacts in the authenticated user's domain directory./v1/people:listDirectoryPeople
GETProvides a list of the authenticated user's contacts./v1/{resourceName}/connections
GETProvides information about a list of specific people by specifying a list of requested resource names./v1/people:batchGet
GETProvides information about a person by specifying a resource name./v1/{resourceName}

How automating Google People works

Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
See it proven. The program runs and shows you the result before it is allowed near your live Google People account.
Grant access, then go live. You approve the specific Google People operations it may use — and only those.