Can HumDay connect to Google Safe Browsing?

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

Do I need to write code to automate Google Safe Browsing?

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 Safe Browsing account.

What can HumDay do in Google Safe Browsing?

4 of the 7 documented operations change something in Google Safe Browsing, and 3 read from it. HumDay only ever uses the specific operations your approved contract needs.

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

Automate Google Safe Browsing

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

Enables client applications to check web resources (most commonly URLs) against Google-generated lists of unsafe web resources. The Safe Browsing APIs are for non-commercial use only. If you need to use APIs to detect malicious URLs for commercial purposes – meaning “for sale or revenue-generating purposes” – please refer to the Web Risk API.

API host: safebrowsing.googleapis.com

What HumDay can do in Google Safe Browsing

4 documented operations change something in Google Safe Browsing.

POSTReports a Safe Browsing threat list hit to Google./v4/threatHits
POSTFetches the most recent threat list updates./v4/threatListUpdates:fetch
POSTFinds the full hashes that match the requested hash prefixes./v4/fullHashes:find
POSTFinds the threat entries that match the Safe Browsing lists./v4/threatMatches:find

What HumDay can read from Google Safe Browsing

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

GETLists the Safe Browsing threat lists available for download./v4/threatLists
GETRead encodedRequest/v4/encodedUpdates/{encodedRequest}
GETRead encodedRequest/v4/encodedFullHashes/{encodedRequest}

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