Google Connectors API
Browse all Google APIs40
AI ReadinessNon-Ready (D-)40/100
Official vendor OpenAPI document · agent-readyCloud InfrastructureServerlessoauth241 EndpointsREST
For Agents
Provision and manage Google Cloud Connectors so agents can discover SaaS connection profiles, attach runtime endpoints, and grant IAM access for downstream Application Integration or Workflows calls.
Use for: I need to create a Salesforce connection in Google Cloud Connectors, List all connections in the us-central1 region, Retrieve the schema of a ServiceNow connector, Set up a custom connector from an OpenAPI spec
Not supported: Does not transform data, run pipelines, or execute workflow logic - use only to provision and manage connection resources for Application Integration and Workflows.
Google Cloud Connectors API lets developers create and manage connections between Google Cloud services and third-party business applications such as Salesforce, ServiceNow, Jira, and SAP. It exposes connection lifecycle operations, custom connector definitions, managed zones, runtime endpoint attachments, and IAM policy management for connection resources. Connections are then consumable from Application Integration, Workflows, and Apigee for low-code orchestration. The API is region-scoped and uses long-running operations for resource provisioning.
Install Jentic One Beta
Connect the Connectors API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Connectors API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fconnectors" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fconnectors" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Connectors API.
Create and configure connections to Salesforce, ServiceNow, BigQuery, and other backends with provider-specific config nodes
Register and version custom connectors built from OpenAPI or gRPC specifications
Attach runtime endpoint configurations and managed zones to keep traffic within a VPC perimeter
Bind IAM roles to a connection so a workflow service account can invoke it
Inspect connection schema metadata, including entities, actions, and authentication requirements
Track long-running provisioning operations and roll back failed deployments
List supported connector providers and their published versions for selection at design time
Use Cases
Patterns agents use Connectors API for, with concrete tasks.
★ SaaS Workflow Orchestration
Wire Salesforce, ServiceNow, or NetSuite into a Google Cloud Workflow without writing per-vendor auth code. Connectors API provisions the connection profile and IAM bindings; the orchestrator references the connection by name and Cloud Connectors handles token refresh, schema discovery, and per-call execution. Setup completes in under an hour for a supported backend.
Create a Salesforce connection named 'sales-prod' in us-central1, attach an OAuth2 auth config, and grant roles/connectors.invoker to the workflow service account.
Custom Connector Publishing
Publish an internal API as a reusable Google Cloud connector. The Connectors API ingests an OpenAPI 3 specification, generates a custom connector resource, and exposes it to Application Integration users in the same project. Custom connectors inherit IAM, audit logging, and VPC-SC controls so internal services can be safely surfaced.
Register a custom connector named 'billing-api' from a Cloud Storage URI containing the OpenAPI spec, then publish version 1.0.0.
Connection Inventory Audit
Produce a region-by-region report of every connection, its underlying connector type, last activity, and IAM bindings. Useful for compliance reviews and cost attribution. The Connectors API enumerates connections per location and exposes IAM and node configuration so an auditor can confirm that no connection grants over-broad access.
List every connection across all regions in project 'acme-prod', fetch the IAM policy for each, and flag any that grant roles/owner.
AI Agent Backend Connection Setup
Let an AI agent stand up the backend connections it needs (CRM, ITSM, ERP) at runtime through Jentic. The agent searches for the connector type, the Connectors API provisions it under a service account, and the agent immediately calls the new connection through Application Integration without an engineer in the loop. Jentic isolates the OAuth client and rotates tokens per request.
Provision a ServiceNow connection in europe-west1 for a freshly onboarded tenant, wait for the long-running operation to finish, and bind roles/connectors.invoker.
Key Endpoints
41 endpoints — google cloud connectors api lets developers create and manage connections between google cloud services and third-party business applications such as salesforce, servicenow, jira, and sap.
METHOD
PATH
DESCRIPTION
GET
/v1/{+name}/connections
List connections in a project and location
POST
/v1/{+name}/connections
Create a new connection
GET
/v1/{+name}/providers
List available connector providers
POST
/v1/{+name}/customConnectors
Create a custom connector
POST
/v1/{+name}:setIamPolicy
Set the IAM policy for a connection
GET
/v1/{+name}/operations
Track long-running provisioning operations
GET
/v1/{+name}/connections
List connections in a project and location
POST
/v1/{+name}/connections
Create a new connection
GET
/v1/{+name}/providers
List available connector providers
POST
/v1/{+name}/customConnectors
Create a custom connector
POST
/v1/{+name}:setIamPolicy
Set the IAM policy for a connection
GET
/v1/{+name}/operations
Track long-running provisioning operations
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
C
Connectors API
- Non-Ready (D-)40/100
39
Foundational Compliance56
Developer Experience & Jentic Compatibility20
AI-Readiness & Agent Experience94
Agent Usability63
Security63
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
39
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: FSignals: 4
49%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
7%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
56
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: CSignals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
25%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
20
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
80%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
0%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
63
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
62%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
63
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: BSignals: 1
63%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Connectors API by hand means setting up Google OAuth 2.0, minting short-lived tokens against the cloud-platform scope, and addressing each connection resource by name against connectors.googleapis.com yourself. Through Jentic you install once, import the Connectors API from the API Directory, store the OAuth credential once, and your agent calls it.
Permission scoping
Connectors puts the parent and connection resource names in the URL path (/v1/{+name}/connections, /v1/{+name}/customConnectors), so a rule can pin your agent to one location: it can create and list connections there and nothing else. You choose the operations it may call, so setIamPolicy is not included unless you add it.
Credential isolation
Your Connectors OAuth credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a Salesforce connection in Google Cloud' or 'list available connectors', and Jentic returns the matching Connectors operation with its input schema, including connectorVersion and authConfig, so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Connectors API through Jentic.
What authentication does the Google Cloud Connectors API use?
The Connectors API uses Google OAuth 2.0 with the cloud-platform scope. Through Jentic the OAuth client and refresh tokens are stored encrypted in your Jentic One instance, and agents receive scoped access tokens per call instead of long-lived credentials.
Can I create a custom connector from my own OpenAPI spec with the Connectors API?
Yes. Use the customConnectors create endpoint to register a connector resource and then publish a customConnectorVersion that references your OpenAPI 3 specification stored in Cloud Storage. Once published the custom connector is selectable from Application Integration.
What are the rate limits for the Google Cloud Connectors API?
The Connectors API inherits standard Google Cloud per-project quotas: write requests are limited per minute and long-running provisioning operations have their own concurrency cap. Check the Quotas page in the Cloud Console for your project's exact ceilings.
How do I provision a new Salesforce connection through Jentic?
Run pip install jentic, then search Jentic for 'create google cloud connector connection', load the schema for connections.create on connectors.googleapis.com, and execute it with your project, region, connectorVersion, and authConfig payload.
Does the Connectors API run user-defined code or transformations?
No. Connectors API only provisions and manages connection metadata and IAM. Data transformations and orchestration live in Application Integration or Workflows, which call the connections at runtime.
Can I limit what my agent is allowed to do with the Google Cloud Connectors API?
Yes. Jentic One is self-hosted by you, so your own rules decide which Connectors operations and credentials the agent may use. Because Connectors puts the parent and connection resource names in the URL path, such as /v1/{+name}/connections and /v1/{+name}/customConnectors, you can pin the agent to a single project and region and let it only create and list connections there. You choose the operations it may call, so a sensitive operation like setIamPolicy is never available to the agent unless you explicitly add it.
GET STARTED