Can HumDay connect to Google Cloud IDS?

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

Do I need to write code to automate Google Cloud IDS?

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 Cloud IDS account.

What can HumDay do in Google Cloud IDS?

6 of the 11 documented operations change something in Google Cloud IDS, and 5 read from it. HumDay only ever uses the specific operations your approved contract needs.

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

Automate Google Cloud IDS

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

Cloud IDS (Cloud Intrusion Detection System) detects malware, spyware, command-and-control attacks, and other network-based threats. Its security efficacy is industry leading, built with Palo Alto Networks technologies. When you use this product, your organization name and consumption levels will be shared with Palo Alto Networks.

API host: ids.googleapis.com

What HumDay can do in Google Cloud IDS

6 documented operations change something in Google Cloud IDS.

POSTCreates a new Endpoint in a given project and location./v1/{parent}/endpoints
DELETEDeletes a long-running operation./v1/{name}
PATCHUpdates the parameters of a single Endpoint./v1/{name}
POSTStarts asynchronous cancellation on a long-running operation./v1/{name}:cancel
POSTSets the access control policy on the specified resource./v1/{resource}:setIamPolicy
POSTReturns permissions that a caller has on the specified resource./v1/{resource}:testIamPermissions

What HumDay can read from Google Cloud IDS

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

GETGets the latest state of a long-running operation./v1/{name}
GETGets the access control policy for a resource./v1/{resource}:getIamPolicy
GETLists information about the supported locations for this service./v1/{name}/locations
GETLists operations that match the specified filter in the request./v1/{name}/operations
GETLists Endpoints in a given project and location./v1/{parent}/endpoints

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