Google Workflows API
Browse all Google APIs40
AI ReadinessNon-Ready (F)40/100
Official vendor OpenAPI document · agent-readyCloud InfrastructureServerlessoauth28 EndpointsREST
For Agents
Manage Cloud Workflows definitions: create, update, list, and version workflows that orchestrate Google Cloud and third-party API calls. Execution is handled by the separate Workflow Executions API.
Use for: Create a new workflow from a YAML definition, List all workflows in the us-central1 region, Update the source code of an existing workflow, List revisions of a workflow for rollback
Not supported: Does not handle workflow execution, scheduling, container image building, or runtime step orchestration - use for managing Cloud Workflows definitions only.
The Google Workflows API manages the definitions of Cloud Workflows - a serverless service that orchestrates calls to Google Cloud, third-party APIs, and HTTP endpoints in declarative YAML. Through this API you create, update, list, and delete workflow definitions and inspect available revisions for rollback and audit. To actually execute a workflow you call the companion Workflow Executions API; this API is purely the control plane for the definition lifecycle.
Install Jentic One Beta
Connect the Workflows API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Workflows 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%2Fworkflows" | 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%2Fworkflows" | 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 Workflows API.
Create a new workflow definition from a YAML or JSON source body
Update an existing workflow definition in place, producing a new revision
List all workflows in a region with name, description, state, and revisionId
List historical revisions of a workflow for rollback or audit
Delete a workflow that is no longer needed
Use Cases
Patterns agents use Workflows API for, with concrete tasks.
★ GitOps deployment of workflow definitions
Treat workflow YAML as code in a Git repository and have CI deploy changes through the Workflows API on every merge. POST /v1/{+parent}/workflows creates new workflows; PATCH on an existing workflow name pushes updates and produces a new revision the team can roll back to with listRevisions. This brings the same review-and-deploy hygiene to orchestrations that engineers expect for application code.
Create a workflow under projects/{project}/locations/us-central1/workflows with name=order-fulfilment and a sourceContents body, then list revisions to confirm the new revisionId.
Multi-region orchestration management
Platform teams managing workflows across multiple regions use list endpoints to inventory definitions and coordinate updates. The /v1/{+name}/locations and /v1/{+parent}/workflows endpoints make it straightforward to render an internal dashboard that shows every workflow, its state, and its current revisionId. Combined with the operations endpoints, the same UI can show in-flight create or update operations.
Call GET /v1/{+name}/locations to enumerate regions, then for each region call /v1/{+parent}/workflows and emit a table of name, state, and revisionId.
Safe rollout with revision rollback
When a new workflow revision misbehaves, listRevisions exposes prior versions so the team can roll back by patching the workflow back to a known-good source. Each revision is immutable and addressable, so this functions as a built-in change-management surface. It is especially useful when a workflow change interacts with downstream APIs in unexpected ways.
List revisions for a workflow, find the revision before the most recent, fetch its sourceContents, and patch the workflow back to that source.
Agent-driven workflow authoring through Jentic
An agent that designs an orchestration can call Workflows through Jentic to materialise the YAML it generated. Jentic search for create a cloud workflow returns the workflows create operation; the agent fills in name, description, and sourceContents and executes. Credential isolation in Jentic keeps the OAuth token out of the model's context.
Through Jentic, create a workflow with sourceContents generated by the agent and verify the returned operation completes by polling /v1/{+name}/operations.
Key Endpoints
8 endpoints — the google workflows api manages the definitions of cloud workflows - a serverless service that orchestrates calls to google cloud, third-party apis, and http endpoints in declarative yaml.
METHOD
PATH
DESCRIPTION
GET
/v1/{+parent}/workflows
List workflows in a region
POST
/v1/{+parent}/workflows
Create a new workflow
GET
/v1/{+name}
Get workflow details
GET
/v1/{+name}:listRevisions
List historical revisions of a workflow
GET
/v1/{+name}/locations
List supported locations
GET
/v1/{+name}/operations
Track long-running operations
GET
/v1/{+parent}/workflows
List workflows in a region
POST
/v1/{+parent}/workflows
Create a new workflow
GET
/v1/{+name}
Get workflow details
GET
/v1/{+name}:listRevisions
List historical revisions of a workflow
GET
/v1/{+name}/locations
List supported locations
GET
/v1/{+name}/operations
Track long-running 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.
W
Workflows API
- Non-Ready (F)40/100
71
Foundational Compliance56
Developer Experience & Jentic Compatibility17
AI-Readiness & Agent Experience94
Agent Usability63
Security67
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
71
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
84%
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).
100%
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.
17
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
68%
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).
67
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: B+Signals: 1
67%
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 Workflows API by hand means setting up OAuth 2.0 for your Google Cloud project, refreshing access tokens, and matching definition management calls against the workflows.googleapis.com host. Through Jentic you install once, import the Workflows API from the API Directory, store the OAuth credential once, and your agent calls it.
Permission scoping
The Workflows API puts the workflow in the URL path (/v1/{name}), so a rule can pin your agent to one workflow: it can read that workflow and list its revisions and nothing else. You choose the operations it may call, so creating or deleting workflow definitions is not included unless you add it.
Credential isolation
Your Google Cloud OAuth credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. Its client secret and refresh token never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a workflow definition' or 'list workflow revisions', and Jentic returns the workflows create or listRevisions operation with its input schema 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 Workflows API through Jentic.
What authentication does the Workflows API use?
OAuth 2.0 (Oauth2 and Oauth2c schemes) scoped to https://www.googleapis.com/auth/cloud-platform. Through Jentic the OAuth credentials are stored encrypted in the vault and short-lived access tokens are minted at execution time.
Does this API also run workflows?
No. Workflows is only the definition control plane. To execute a workflow, call the Workflow Executions API at workflowexecutions.googleapis.com. This separation lets the two services scale independently - definition reads are infrequent while executions can fan out heavily.
What are the rate limits for the Workflows API?
Per-project quotas on workflow create, update, and list calls are configured in the Cloud Console under APIs and Services and are sized for definition management rather than runtime traffic. Most teams never hit them; the runtime quotas live on the Workflow Executions API instead.
How do I create a workflow through Jentic?
Search Jentic for create a cloud workflow, load the schema for POST /v1/{+parent}/workflows, and execute it with parent=projects/{project}/locations/{loc}, name, description, and a sourceContents body. The response is a long-running operation; poll /v1/{+name}/operations until done is true.
Can I roll back to a previous workflow revision?
Yes. Call /v1/{+name}:listRevisions to see all historical revisions and their sourceContents, then PATCH the workflow with the desired source to make that revision live. Each PATCH creates a new revisionId rather than overwriting history.
Can I limit what my agent is allowed to do with the Workflows API?
Yes. Because the Workflows API carries the workflow name in the URL path (/v1/{name}), your self-hosted Jentic One instance lets you write a rule that pins the agent to a single workflow so it can read that workflow and list its revisions and nothing else. You decide which operations it may call, so creating, updating, or deleting workflow definitions stays off limits unless you add those operations yourself. The OAuth credential is held by your instance and injected only for the calls you have permitted.
GET STARTED