LocalCloud Cloud Workflows Local Emulator
Get started
local.cloud — Cloud Workflows Local Emulator .md Open tab
LocalCloud Google Cloud in-a-box

Cloud Workflows

Workflows orchestrates a sequence of API calls and application steps. It makes retries, branching, and execution state explicit in a workflow definition.

When to use Cloud Workflows

Typical uses

Use when a process coordinates several API calls and needs explicit sequencing, branching, retries, and a queryable execution result.

Examples

  • Multi-step service orchestration
  • HTTP integrations with retry handling
Messaging & Workflow

Explore another service

View all
Local workflow

Example usage

Install the CLI, start LocalCloud, and export its environment in the same shell. Generated endpoints account for remapped ports.

1. Install and start · shell
curl -fsSL https://local.cloud/install.sh | sh
localcloud start --local-only
# Export GOOGLE_CLOUD_PROJECT and WORKFLOWS_EMULATOR_HOST
eval "$(localcloud env)"

Coordinate two local HTTP services

  1. Deploy a definition using documented HTTP calls and expressions.
  2. Start an execution with a small input payload.
  3. Inspect step history and verify the returned result.

Documented workflows

  • Workflow deployment and lifecycle
  • Local interpreter, standard library, and execution step history

Service boundaries

  • Limited connector and expression support
  • Active executions fail on restart with InstanceRestart
Try it in your project

Code examples and integrations

Start with the local guides. Official Google Cloud samples may need endpoint changes and can cover features outside the workflows listed here.

Integration

Build an integration test loop

Start the runtime, verify readiness, exercise your SDK, and clean up test state.

Open guide
Agent testing

Use Cloud Workflows with an AI agent

Before the agent changes application logic, have it create local Cloud Workflows state, read it back with the project SDK, and note which feature the check covered. That first local call catches accidental production routing and needs no GCP account, service-account key, or billing project.

Configure this repo

Set up this repository to use LocalCloud for local GCP development. First read https://local.cloud/ai/agents.md, then inspect this repo, identify the GCP services and SDK language, configure emulator environment variables, and run the narrowest integration test against localhost. Do not use real GCP credentials or production endpoints.

Production endpoints, auth, IAM, quotas, regional behavior, and final release validation still need the target Google Cloud project.

Agent resources has more prompts and the AGENTS.md template.

Related guides

Desktop view