Can HumDay connect to Google Street View Publish?

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

Do I need to write code to automate Google Street View Publish?

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 Street View Publish account.

What can HumDay do in Google Street View Publish?

9 of the 14 documented operations change something in Google Street View Publish, and 5 read from it. HumDay only ever uses the specific operations your approved contract needs.

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

Automate Google Street View Publish

HumDay reads Google Street View Publish’s own published API description and derives 14 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 Street View Publish is

Publishes 360 photos to Google Maps, along with position, orientation, and connectivity metadata. Apps can offer an interface for positioning, connecting, and uploading user-generated Street View images.

API host: streetviewpublish.googleapis.com

What HumDay can do in Google Street View Publish

9 documented operations change something in Google Street View Publish.

POSTCreates an upload session to start uploading photo bytes./v1/photo:startUpload
POSTCreates an upload session to start uploading photo sequence data./v1/photoSequence:startUpload
POSTDeletes a list of Photos and their metadata./v1/photos:batchDelete
POSTAfter the client finishes uploading the photo with the returned UploadRef, CreatePhoto publishes the uploaded Photo to Street View on Google Maps./v1/photo
POSTAfter the client finishes uploading the PhotoSequence with the returned UploadRef, CreatePhotoSequence extracts a sequence of 360 photos from a video or Extensible Device Metadata…/v1/photoSequence
POSTUpdates the metadata of Photos, such as pose, place association, connections, etc./v1/photos:batchUpdate
PUTUpdates the metadata of a Photo, such as pose, place association, connections, etc./v1/photo/{id}
DELETEDeletes a Photo and its metadata./v1/photo/{photoId}
DELETEDeletes a PhotoSequence and its metadata./v1/photoSequence/{sequenceId}

What HumDay can read from Google Street View Publish

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

GETLists all the PhotoSequences that belong to the user, in descending CreatePhotoSequence timestamp order./v1/photoSequences
GETLists all the Photos that belong to the user./v1/photos
GETGets the metadata of the specified Photo batch./v1/photos:batchGet
GETGets the metadata of the specified Photo./v1/photo/{photoId}
GETGets the metadata of the specified PhotoSequence via the Operation interface./v1/photoSequence/{sequenceId}

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