Google Cloud Functions
Google CloudOAuth 2.0Connection test available
Invoke Google Cloud Functions (Google OAuth2).
OCNORA ships 19 typed Google Cloud Functions operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.
Before you connect Google Cloud Functions
- Authentication
- OAuth 2.0
- Credential
- {"client_id", "client_secret", "refresh_token"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
What you can do with Google Cloud Functions
Operations, grouped by what they do to your data.
Update 1
Delete and cancel 1
A sample Google Cloud Functions workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Cloud Functions trigger is needed.
- 2Get Functioncloud_functions.get_functionRead a Cloud Function's state, URL, runtime and entry point (2nd gen API).
- 3Abort Function Upgrade Functioncloud_functions.abort_function_upgrade_functionAborts generation upgrade process for a function with the given name from the specified project.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 19
- Abort Function Upgrade FunctionAborts generation upgrade process for a function with the given name from the specified project.cloud_functions.abort_function_upgrade_function
- CallSynchronously invoke a Google Cloud Function and return its result.cloud_functions.call
- Commit Function Upgrade As Gen2 FunctionCommits a function upgrade from GCF Gen1 to GCF Gen2.cloud_functions.commit_function_upgrade_as_gen2_function
- Commit Function Upgrade FunctionFinalizes the upgrade after which function upgrade can not be rolled back.cloud_functions.commit_function_upgrade_function
- Create FunctionCreates a new function.cloud_functions.create_function
- Delete FunctionDeletes a function with the given name from the specified project.cloud_functions.delete_function
- Detach Function FunctionDetaches 2nd Gen function to Cloud Run function.cloud_functions.detach_function_function
- Generate Download Url FunctionReturns a signed URL for downloading deployed function source code.cloud_functions.generate_download_url_function
- Generate Upload Url FunctionReturns a signed URL for uploading a function source code.cloud_functions.generate_upload_url_function
- Get FunctionRead a Cloud Function's state, URL, runtime and entry point (2nd gen API).cloud_functions.get_function
- Get OperationGets the latest state of a long-running operation.cloud_functions.get_operation
- List FunctionsList Cloud Functions (2nd gen API) in a project region with state and URL.cloud_functions.list_functions
- List LocationsLists information about the supported locations for this service.cloud_functions.list_locations
- List OperationsLists operations that match the specified filter in the request.cloud_functions.list_operations
- List RuntimesReturns a list of runtimes that are supported for the requested project.cloud_functions.list_runtimes
- Redirect Function Upgrade Traffic FunctionChanges the traffic target of a function from the original 1st Gen function to the 2nd Gen copy.cloud_functions.redirect_function_upgrade_traffic_function
- Rollback Function Upgrade Traffic FunctionReverts the traffic target of a function from the 2nd Gen copy to the original 1st Gen function.cloud_functions.rollback_function_upgrade_traffic_function
- Setup Function Upgrade Config FunctionCreates a 2nd Gen copy of the function configuration based on the 1st Gen function with the given name.cloud_functions.setup_function_upgrade_config_function
- Update FunctionUpdates existing function.cloud_functions.update_function
Google Cloud Functions questions
- How does OCNORA authenticate with Google Cloud Functions?
- With a stored OAuth 2.0 credential, shaped {"client_id", "client_secret", "refresh_token"}. A connection test can check it when you add it.
- What can I automate with Google Cloud Functions?
- 19 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google Cloud Functions operation I need is not listed?
- Where Google Cloud Functions has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Google Cloud Functions?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google Cloud Functions calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
See your first Google Cloud Functions workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.