Can HumDay connect to Google SAS Portal (Testing)?

Yes. HumDay reads Google SAS Portal (Testing)'s own published API description and derives the operations from it, so there is no hand-built connector to wait for. 20 operations are documented.

Do I need to write code to automate Google SAS Portal (Testing)?

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 SAS Portal (Testing) account.

What can HumDay do in Google SAS Portal (Testing)?

15 of the 20 documented operations change something in Google SAS Portal (Testing), and 5 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Google SAS Portal (Testing) 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 SAS Portal (Testing) is held behind that approval.

Automate Google SAS Portal (Testing)

HumDay reads Google SAS Portal (Testing)’s own published API description and derives 20 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 HumDay can do in Google SAS Portal (Testing)

15 documented operations change something in Google SAS Portal (Testing).

POSTCreates a new SAS deployment through the GCP workflow./v1alpha1/customers:provisionDeployment
POSTCreates a new node./v1alpha1/{parent}/nodes
POSTCreates a device under a node or customer./v1alpha1/{parent}/devices
POSTCreates a new deployment./v1alpha1/{parent}/deployments
POSTCreates a signed device under a node or customer./v1alpha1/{parent}/devices:createSigned
POSTMoves a node under another node or customer./v1alpha1/{name}:move
POSTGets the access control policy for a resource./v1alpha1/policies:get
POSTSets the access control policy on the specified resource./v1alpha1/policies:set
POSTReturns permissions that a caller has on the specified resource./v1alpha1/policies:test
POSTValidates the identity of a Certified Professional Installer (CPI)./v1alpha1/installer:validate
DELETEDeletes a node./v1alpha1/{name}
PATCHUpdates an existing node./v1alpha1/{name}
POSTGenerates a secret to be used with the ValidateInstaller./v1alpha1/installer:generateSecret
POSTSigns a device./v1alpha1/{name}:signDevice
PATCHUpdates a signed device./v1alpha1/{name}:updateSigned

What HumDay can read from Google SAS Portal (Testing)

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

GETReturns a list of requested customers./v1alpha1/customers
GETLists devices under a node or customer./v1alpha1/{parent}/devices
GETReturns a requested node./v1alpha1/{name}
GETLists nodes./v1alpha1/{parent}/nodes
GETLists deployments./v1alpha1/{parent}/deployments

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