Google Workflows API

Name: Workflows API
Brand: Workflows API
Availability: InStock

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

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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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

GET STARTED

Start building with Workflows API

Explore with Jentic

View OpenAPI Document

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

Why Jentic?

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

Credential isolation

OAuth 2.0 client credentials are stored encrypted in the Jentic vault. Agents receive scoped access tokens; refresh tokens and client secrets never leave the vault.

Intent-based discovery

Agents call Jentic search with intents like create a workflow or list workflow revisions and Jentic returns the workflows create or listRevisions operation with its full input schema.

Time to first call

Direct integration: half a day for OAuth setup and operation polling. Through Jentic: under 30 minutes to create and verify a workflow.

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.

Google Workflows API

Connect the Workflows API to your agent

Capabilities

Start building with Workflows API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs