Google Developer Connect
Connect third-party source code management to Google (Google OAuth2).
OCNORA ships 10 typed Google Developer Connect 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 Developer Connect
- 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 Developer Connect
Operations, grouped by what they do to your data.
Create and send 2
Update 1
Delete and cancel 2
Other operations 1
A sample Google Developer Connect workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Developer Connect trigger is needed.
- 2Get Connectiondeveloper_connect.get_connectionGets details of a single Connection.
- 3Create Connectiondeveloper_connect.create_connectionCreates a new Connection in a given project and location.
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 10
- Create ConnectionCreates a new Connection in a given project and location.developer_connect.create_connection
- Create Git Repository LinkCreates a GitRepositoryLink.developer_connect.create_git_repository_link
- Delete ConnectionDeletes a single Connection.developer_connect.delete_connection
- Delete Git Repository LinkDeletes a single GitRepositoryLink.developer_connect.delete_git_repository_link
- Get ConnectionGets details of a single Connection.developer_connect.get_connection
- Get Git Repository LinkGets details of a single GitRepositoryLink.developer_connect.get_git_repository_link
- List ConnectionsLists Connections in a given project and location.developer_connect.list_connections
- List Git Repository LinksLists GitRepositoryLinks in a given project, location, and connection.developer_connect.list_git_repository_links
- Process Git Hub Enterprise WebhookProcessGitHubEnterpriseWebhook is called by the external GitHub Enterprise instances for notifying events.developer_connect.process_git_hub_enterprise_webhook
- Update ConnectionUpdates the parameters of a single Connection.developer_connect.update_connection
Google Developer Connect questions
- How does OCNORA authenticate with Google Developer Connect?
- 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 Developer Connect?
- 10 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google Developer Connect operation I need is not listed?
- Where Google Developer Connect 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 Developer Connect?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google Developer Connect 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 Developer Connect 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.