Can HumDay connect to Google Blogger?

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

Do I need to write code to automate Google Blogger?

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

What can HumDay do in Google Blogger?

16 of the 33 documented operations change something in Google Blogger, and 17 read from it. HumDay only ever uses the specific operations your approved contract needs.

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

Automate Google Blogger

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

The Blogger API provides access to posts, comments and pages of a Blogger blog.

API host: blogger.googleapis.com

What HumDay can do in Google Blogger

16 documented operations change something in Google Blogger.

POSTInserts a post./v3/blogs/{blogId}/posts
DELETEDeletes a comment by blog id, post id and comment id./v3/blogs/{blogId}/posts/{postId}/comments/{commentId}
POSTMarks a comment as spam by blog id, post id and comment id./v3/blogs/{blogId}/posts/{postId}/comments/{commentId}/spam
POSTMarks a comment as not spam by blog id, post id and comment id./v3/blogs/{blogId}/posts/{postId}/comments/{commentId}/approve
POSTRemoves the content of a comment by blog id, post id and comment id./v3/blogs/{blogId}/posts/{postId}/comments/{commentId}/removecontent
DELETEDeletes a post by blog id and post id./v3/blogs/{blogId}/posts/{postId}
PATCHPatches a post./v3/blogs/{blogId}/posts/{postId}
PUTUpdates a post by blog id and post id./v3/blogs/{blogId}/posts/{postId}
POSTInserts a page./v3/blogs/{blogId}/pages
POSTReverts a published or scheduled post to draft state./v3/blogs/{blogId}/posts/{postId}/revert
POSTPublishes a post./v3/blogs/{blogId}/posts/{postId}/publish
DELETEDeletes a page by blog id and page id./v3/blogs/{blogId}/pages/{pageId}
PATCHPatches a page./v3/blogs/{blogId}/pages/{pageId}
PUTUpdates a page by blog id and page id./v3/blogs/{blogId}/pages/{pageId}
POSTReverts a published or scheduled page to draft state./v3/blogs/{blogId}/pages/{pageId}/revert
POSTPublishes a page./v3/blogs/{blogId}/pages/{pageId}/publish

What HumDay can read from Google Blogger

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

GETLists post and user info pairs./v3/users/{userId}/blogs/{blogId}/posts
GETSearches for posts matching given query terms in the specified blog./v3/blogs/{blogId}/posts/search
GETGets one user by userid./v3/users/{userId}
GETGets one post and user info pair, by postid and userid./v3/users/{userId}/blogs/{blogId}/posts/{postId}
GETLists blogs by user./v3/users/{userId}/blogs
GETGets a post by path./v3/blogs/{blogId}/posts/bypath
GETGets a post by blog id and post id/v3/blogs/{blogId}/posts/{postId}
GETGets one blog and user info pair by blog id and user id./v3/users/{userId}/blogs/{blogId}
GETLists posts./v3/blogs/{blogId}/posts
GETGets a comment by id./v3/blogs/{blogId}/posts/{postId}/comments/{commentId}
GETLists comments by blog./v3/blogs/{blogId}/comments
GETGets page views by blog id./v3/blogs/{blogId}/pageviews
GETLists comments./v3/blogs/{blogId}/posts/{postId}/comments
GETGets a blog by url./v3/blogs/byurl
GETGets a blog by id./v3/blogs/{blogId}
GETGets a page by blog id and page id./v3/blogs/{blogId}/pages/{pageId}
GETLists pages./v3/blogs/{blogId}/pages

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