Can HumDay connect to Google Network Connectivity?

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

Do I need to write code to automate Google Network Connectivity?

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 Network Connectivity account.

What can HumDay do in Google Network Connectivity?

8 of the 15 documented operations change something in Google Network Connectivity, and 7 read from it. HumDay only ever uses the specific operations your approved contract needs.

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

Automate Google Network Connectivity

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

This API enables connectivity with and between Google Cloud resources.

API host: networkconnectivity.googleapis.com

What HumDay can do in Google Network Connectivity

8 documented operations change something in Google Network Connectivity.

POSTCreates a new Network Connectivity Center hub in the specified project./v1/{parent}/hubs
POSTCreates a Network Connectivity Center spoke./v1/{parent}/spokes
DELETEDeletes a Network Connectivity Center spoke./v1/{name}
PATCHUpdates the parameters of a Network Connectivity Center spoke./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
POSTCreates a new internal range in a given project and location./v1/{parent}/internalRanges

What HumDay can read from Google Network Connectivity

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

GETGets details about a Network Connectivity Center spoke./v1/{name}
GETGets the access control policy for a resource./v1/{resource}:getIamPolicy
GETLists the Network Connectivity Center hubs associated with a given project./v1/{parent}/hubs
GETLists the Network Connectivity Center spokes in a specified project and location./v1/{parent}/spokes
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 internal ranges in a given project and location./v1/{parent}/internalRanges

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