Google Connectors
Enables users to create and manage connections to Google Cloud services and third-party business applications using the Connectors interface (Google OAuth2).
OCNORA ships 4 typed Google Connectors 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 Connectors
- 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 Connectors
Operations, grouped by what they do to your data.
Create and send 2
Read and search 2
A sample Google Connectors workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Connectors trigger is needed.
- 2Check Statusintegration_connectors.check_statusReports the status of the connection.
- 3Execute Http Requestintegration_connectors.execute_http_requestExecutes a generic HTTP request. This supports all payload formats including REST/JSON, GraphQL, XML, SOAP, and Multipart by passing the rendered payload as raw bytes.
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 4
- Check StatusReports the status of the connection.integration_connectors.check_status
- Execute Http RequestExecutes a generic HTTP request. This supports all payload formats including REST/JSON, GraphQL, XML, SOAP, and Multipart by passing the rendered payload as raw bytes.integration_connectors.execute_http_request
- Execute Sql QueryExecutes a SQL statement specified in the body of the request.integration_connectors.execute_sql_query
- List Custom Tool NamesLists custom tool names.integration_connectors.list_custom_tool_names
Google Connectors questions
- How does OCNORA authenticate with Google Connectors?
- 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 Connectors?
- 4 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google Connectors operation I need is not listed?
- Where Google Connectors 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 Connectors?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google Connectors 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 Connectors 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.