Google Cloud Composer
Trigger Airflow DAGs and inspect Cloud Composer environments (Google OAuth2).
OCNORA ships 7 typed Google Cloud Composer 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 Composer
- 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 Composer
Operations, grouped by what they do to your data.
Create and send 2
Read and search 2
Update 1
Delete and cancel 1
Other operations 1
A sample Google Cloud Composer workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Cloud Composer trigger is needed.
- 2Get Environmentcloud_composer.get_environmentFetch a Composer environment (state, Airflow URI, DAG bucket).
- 3Create Environmentcloud_composer.create_environmentCreate a new environment.
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 7
- Create EnvironmentCreate a new environment.cloud_composer.create_environment
- Delete EnvironmentDelete an environment.cloud_composer.delete_environment
- Get EnvironmentFetch a Composer environment (state, Airflow URI, DAG bucket).cloud_composer.get_environment
- List EnvironmentsList Cloud Composer environments in a location.cloud_composer.list_environments
- Poll CommandRead the output of a previously executed Airflow CLI command.cloud_composer.poll_command
- Trigger DAGTrigger an Airflow DAG run via the Composer CLI endpoint.cloud_composer.trigger_dag
- Update EnvironmentUpdate an environment.cloud_composer.update_environment
Google Cloud Composer questions
- How does OCNORA authenticate with Google Cloud Composer?
- 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 Composer?
- 7 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google Cloud Composer operation I need is not listed?
- Where Google Cloud Composer 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 Composer?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google Cloud Composer 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 Composer 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.