Connectors API

Name: Connectors API API
Brand: Google Cloud Connectors API
Availability: InStock

✓ Official Vendor SpecCloud 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.

Quickstart

Get started with Connectors API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create a google cloud connector connection"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Connectors API API.

Create and configure connections to Salesforce, ServiceNow, BigQuery, and other backends with provider-specific config nodes

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

GET STARTED

Start building with Connectors API API

Explore with Jentic

View OpenAPI Document

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.

Use Cases

Patterns agents use Connectors API 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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Google OAuth client secrets and refresh tokens are stored encrypted in the Jentic vault. Agents call connectors.googleapis.com with short-lived access tokens minted per request, so raw client credentials never enter the agent context.

Intent-based discovery

Agents search Jentic by intent (e.g. 'create salesforce connection in google cloud') and Jentic returns the matching connectors.create operation with its full input schema, including connectorVersion and authConfig requirements.

Time to first call

Direct integration: 2-3 days to handle OAuth, regional endpoints, and long-running operation polling. Through Jentic: under 1 hour by chaining search, load, and execute against the connections collection.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Dataflow API

Run streaming and batch pipelines that move data through configured connector endpoints

Use Dataflow when the workload is large-scale ETL; use Connectors API when the workload is a transactional SaaS call from a workflow

Complementary

Google Cloud Data Catalog API

Catalogue the data assets reachable through provisioned connections

Pair with Connectors API when an agent needs to first list available data assets before querying a connection

Alternative

Google Cloud Pub/Sub API

Event-driven messaging is an alternative integration pattern for asynchronous SaaS sync

Choose Pub/Sub when the integration is event-based; choose Connectors API when the integration is request/response against a SaaS system of record

FAQs

Specific to using Connectors API 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 the Jentic vault, 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.