Can HumDay connect to Google Books?

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

Do I need to write code to automate Google Books?

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 Books account.

What can HumDay do in Google Books?

21 of the 51 documented operations change something in Google Books, and 30 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Google Books 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 Books is held behind that approval.

Automate Google Books

HumDay reads Google Books’s own published API description and derives 51 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 Books is

The Google Books API allows clients to access the Google Books repository.

API host: books.googleapis.com

What HumDay can do in Google Books

21 documented operations change something in Google Books.

POSTAdd a user-upload volume and triggers processing./books/v1/cloudloading/addBook
POSTInitiates sharing of the content with the user's family./books/v1/familysharing/share
POSTUpdates a user-upload volume./books/v1/cloudloading/updateBook
POSTInitiates revoking content that has already been shared with the user's family./books/v1/familysharing/unshare
POSTInserts a new annotation./books/v1/mylibrary/annotations
POSTSets the settings for the user./books/v1/myconfig/updateUserSettings
POSTRate a recommended book for the current user./books/v1/volumes/recommended/rate
POSTAccepts the promo offer./books/v1/promooffer/accept
POSTMarks the promo offer as dismissed./books/v1/promooffer/dismiss
POSTRequest concurrent and download access restrictions./books/v1/myconfig/requestAccess
POSTRemove the book and its contents/books/v1/cloudloading/deleteBook
POSTRequest downloaded content access for specified volumes on the My eBooks shelf./books/v1/myconfig/syncVolumeLicenses
POSTRelease downloaded content access restriction./books/v1/myconfig/releaseDownloadAccess
POSTAdds a volume to a bookshelf./books/v1/mylibrary/bookshelves/{shelf}/addVolume
POSTGets the summary of specified layers./books/v1/mylibrary/annotations/summary
DELETEDeletes an annotation./books/v1/mylibrary/annotations/{annotationId}
PUTUpdates an existing annotation./books/v1/mylibrary/annotations/{annotationId}
POSTMoves a volume within a bookshelf./books/v1/mylibrary/bookshelves/{shelf}/moveVolume
POSTClears all volumes from a bookshelf./books/v1/mylibrary/bookshelves/{shelf}/clearVolumes
POSTRemoves a volume from a bookshelf./books/v1/mylibrary/bookshelves/{shelf}/removeVolume
POSTSets my reading position information for a volume./books/v1/mylibrary/readingpositions/{volumeId}/setPosition

What HumDay can read from Google Books

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

GETRetrieves a list of public bookshelves for the specified user./books/v1/users/{userId}/bookshelves
GETReturns a list of promo offers available to the user/books/v1/promooffer/get
GETReturn a list of recommended books for the current user./books/v1/volumes/recommended
GETReturn a list of books uploaded by the current user./books/v1/volumes/useruploaded
GETRetrieves a list of bookshelves belonging to the authenticated user./books/v1/mylibrary/bookshelves
GETPerforms a book search./books/v1/volumes
GETReturn a list of books in My Library./books/v1/volumes/mybooks
GETReturns notification details for a given notification id./books/v1/notification/get
GETRetrieves a list of annotations, possibly filtered./books/v1/mylibrary/annotations
GETGets the current settings for the user./books/v1/myconfig/getUserSettings
GETList categories for onboarding experience./books/v1/onboarding/listCategories
GETGets information regarding the family that the user is part of./books/v1/familysharing/getFamilyInfo
GETReturns a list of offline dictionary metadata available/books/v1/dictionary/listOfflineMetadata
GETList available volumes under categories for onboarding experience./books/v1/onboarding/listCategoryVolumes
GETRetrieves metadata for a specific bookshelf for the specified user./books/v1/users/{userId}/bookshelves/{shelf}
GETRetrieves metadata for a specific bookshelf belonging to the authenticated user./books/v1/mylibrary/bookshelves/{shelf}
GETReturn a list of associated books./books/v1/volumes/{volumeId}/associated
GETList the layer summaries for a volume./books/v1/volumes/{volumeId}/layersummary
GETReturns Series metadata for the given series ids./books/v1/series/get
GETRetrieves volumes in a specific bookshelf for the specified user./books/v1/users/{userId}/bookshelves/{shelf}/volumes
GETReturns a stream of personalized book clusters/books/v1/personalizedstream/get
GETGets volume information for a single volume./books/v1/volumes/{volumeId}
GETReturns Series membership data given the series id./books/v1/series/membership/get
GETRetrieves my reading position information for a volume./books/v1/mylibrary/readingpositions/{volumeId}
GETGets volume information for volumes on a bookshelf./books/v1/mylibrary/bookshelves/{shelf}/volumes
GETGets the volume annotations for a volume and layer./books/v1/volumes/{volumeId}/layers/{layerId}
GETGets the layer summary for a volume./books/v1/volumes/{volumeId}/layersummary/{summaryId}
GETGets the annotation data for a volume and layer./books/v1/volumes/{volumeId}/layers/{layerId}/data
GETGets the annotation data./books/v1/volumes/{volumeId}/layers/{layerId}/data/{annotationDataId}
GETGets the volume annotation./books/v1/volumes/{volumeId}/layers/{layerId}/annotations/{annotationId}

How automating Google Books 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 Books account.
Grant access, then go live. You approve the specific Google Books operations it may use — and only those.