Can HumDay connect to Google BeyondCorp?

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

Do I need to write code to automate Google BeyondCorp?

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

What can HumDay do in Google BeyondCorp?

9 of the 18 documented operations change something in Google BeyondCorp, and 9 read from it. HumDay only ever uses the specific operations your approved contract needs.

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

Automate Google BeyondCorp

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

Beyondcorp Enterprise provides identity and context aware access controls for enterprise resources and enables zero-trust access. Using the Beyondcorp Enterprise APIs, enterprises can set up multi-cloud and on-prem connectivity solutions.

API host: beyondcorp.googleapis.com

What HumDay can do in Google BeyondCorp

9 documented operations change something in Google BeyondCorp.

POSTCreates a new AppGateway in a given project and location./v1/{parent}/appGateways
POSTCreates a new AppConnector in a given project and location./v1/{parent}/appConnectors
POSTCreates a new AppConnection in a given project and location./v1/{parent}/appConnections
DELETEDeletes a long-running operation./v1/{name}
PATCHUpdates the parameters of a single AppConnector./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
POSTReport status for a given connector./v1/{appConnector}:reportStatus
POSTReturns permissions that a caller has on the specified resource./v1/{resource}:testIamPermissions

What HumDay can read from Google BeyondCorp

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
GETGets instance configuration for a given AppConnector./v1/{appConnector}:resolveInstanceConfig
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 AppGateways in a given project and location./v1/{parent}/appGateways
GETLists AppConnectors in a given project and location./v1/{parent}/appConnectors
GETLists AppConnections in a given project and location./v1/{parent}/appConnections
GETResolves AppConnections details for a given AppConnector./v1/{parent}/appConnections:resolve

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