Can HumDay connect to Google Cloud Functions?

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

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

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

What can HumDay do in Google Cloud Functions?

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

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

Automate Google Cloud Functions

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

Manages lightweight user-provided functions executed in response to events.

API host: cloudfunctions.googleapis.com

What HumDay can do in Google Cloud Functions

7 documented operations change something in Google Cloud Functions.

POSTCreates a new function./v2/{parent}/functions
DELETEDeletes a function with the given name from the specified project./v2/{name}
PATCHUpdates existing function./v2/{name}
POSTSets the access control policy on the specified resource./v2/{resource}:setIamPolicy
POSTReturns a signed URL for downloading deployed function source code./v2/{name}:generateDownloadUrl
POSTReturns permissions that a caller has on the specified resource./v2/{resource}:testIamPermissions
POSTReturns a signed URL for uploading a function source code./v2/{parent}/functions:generateUploadUrl

What HumDay can read from Google Cloud Functions

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

GETReturns a list of runtimes that are supported for the requested project./v2/{parent}/runtimes
GETReturns a list of functions that belong to the requested project./v2/{parent}/functions
GETGets the latest state of a long-running operation./v2/{name}
GETGets the access control policy for a resource./v2/{resource}:getIamPolicy
GETLists information about the supported locations for this service./v2/{name}/locations
GETLists operations that match the specified filter in the request./v2/{name}/operations

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