Can HumDay connect to Google Apigee Registry?

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

Do I need to write code to automate Google Apigee Registry?

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 Apigee Registry account.

What can HumDay do in Google Apigee Registry?

15 of the 26 documented operations change something in Google Apigee Registry, and 11 read from it. HumDay only ever uses the specific operations your approved contract needs.

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

Automate Google Apigee Registry

HumDay reads Google Apigee Registry’s own published API description and derives 26 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 Apigee Registry

15 documented operations change something in Google Apigee Registry.

POSTAdds a tag to a specified revision of a spec./v1/{name}:tagRevision
POSTCreates a specified API./v1/{parent}/apis
POSTCreates a specified spec./v1/{parent}/specs
POSTCreates a specified version./v1/{parent}/versions
POSTCreates a specified artifact./v1/{parent}/artifacts
POSTCreates a specified deployment./v1/{parent}/deployments
DELETEDeletes a long-running operation./v1/{name}
PATCHUsed to modify a specified spec./v1/{name}
PUTUsed to replace a specified artifact./v1/{name}
POSTStarts asynchronous cancellation on a long-running operation./v1/{name}:cancel
POSTSets the current revision to a specified prior revision./v1/{name}:rollback
DELETEDeletes a revision of a spec./v1/{name}:deleteRevision
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
POSTProvisions instance resources for the Registry./v1/{parent}/instances

What HumDay can read from Google Apigee Registry

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

GETGets the latest state of a long-running operation./v1/{name}
GETReturns the contents of a specified artifact./v1/{name}:getContents
GETLists all revisions of a spec./v1/{name}:listRevisions
GETGets the access control policy for a resource./v1/{resource}:getIamPolicy
GETReturns matching APIs./v1/{parent}/apis
GETReturns matching specs./v1/{parent}/specs
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
GETReturns matching versions./v1/{parent}/versions
GETReturns matching artifacts./v1/{parent}/artifacts
GETReturns matching deployments./v1/{parent}/deployments

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