GCP Workflows cost: a few cents per thousand steps
Google Cloud Workflows bills per step executed, with internal steps very cheap (and a free tier) and external HTTP calls slightly more, so orchestration itself is nearly free. The real cost is what the steps call. Here is the model.
Quick answer
Google Cloud Workflows bills per step executed: internal steps are very cheap (about $0.01 per 1,000 beyond a free tier of thousands per month) and external HTTP call steps slightly more. So orchestration itself is nearly free. The real cost is what the steps invoke, the functions, APIs, and services the workflow calls, which is where the actual spend is.
Google Cloud Workflows orchestrates services, calling APIs and functions in sequence with conditionals, retries, and error handling. Its pricing is per step executed, and steps are cheap, so the orchestration layer is nearly free. As with other orchestrators, the cost is what the workflow calls, not the workflow engine.
Per step, internal and external
| Step type | Cost (approximate) |
|---|---|
| Internal steps | ~$0.01 / 1,000, with a monthly free tier |
| External HTTP call steps | Slightly more per 1,000 |
Internal steps (assignments, conditionals, control flow) cost about a cent per thousand, with thousands free per month. External steps (HTTP calls to other services) cost a bit more. Even a workflow with many steps running frequently costs little in Workflows charges, so the engine is a rounding error.
The real cost is downstream
Each external step calls something, a Cloud Function, a Cloud Run service, an API, and that invoked work is where the cost is. A workflow orchestrating expensive functions costs almost nothing in Workflows but potentially a lot in the functions it calls. So optimize the called services, not the orchestration, the same principle as Cloud Scheduler and Cloud Tasks.
Controlling the real cost
Do not worry about Workflows' step price; optimize what the steps call. Make the invoked functions and services efficient, avoid unnecessary steps and calls, and batch work where possible. The orchestration is essentially free; the workload it coordinates is the cost.
FAQ
How is GCP Cloud Workflows priced?
Per step executed: internal steps (assignments, conditionals, control flow) cost about $0.01 per 1,000 with a monthly free tier of thousands, and external HTTP call steps cost slightly more per 1,000. So orchestration itself is nearly free; even a workflow with many steps running frequently costs little in Workflows charges.
Is GCP Workflows expensive?
No. Steps are very cheap (about a cent per thousand internal steps, with a free tier), so the orchestration engine is a rounding error. The real cost is what the workflow's steps invoke, the functions, services, and APIs it calls, not the Workflows charges themselves.
What is the real cost of using GCP Workflows?
The work each external step calls, a Cloud Function, Cloud Run service, or API, is where the cost is. A workflow orchestrating expensive functions costs almost nothing in Workflows but potentially a lot in the functions it invokes. Optimize the called services, not the orchestration.
How do I reduce workflow-related cost?
Focus on what the steps call, not the Workflows price. Make invoked functions and services efficient, avoid unnecessary steps and external calls, and batch work where possible. The orchestration is essentially free; the workload it coordinates is the meaningful cost.
What is the difference between internal and external Workflows steps?
Internal steps handle control flow, assignments, conditionals, loops, and cost about a cent per thousand with a free tier. External steps make HTTP calls to other services and cost slightly more per thousand. Both are cheap; the external calls' cost is dominated by the services they invoke, not the step charge.
Does C3X estimate Workflows cost?
Workflows is negligible; the cost is what steps call. C3X prices the surrounding infrastructure, including the Cloud Functions and Cloud Run services workflows invoke, which is where the meaningful cost is. Step counts and the called workloads' cost are what you model.
What to do next
Price the services your workflows orchestrate before you deploy. C3X reads your Terraform and prices your resources against a live catalog. Start with the quickstart.
Share this post
Try C3X on your own Terraform
Free and open source. No API key required. One command to install, one command to estimate.