Workers Build API
🏗️Workers Builds
Wrangler
Workers✅Solved
WranglerWorkers✅SolvedHi all, I’m trying to standardize prod/staging environments for several projects using Workers Builds, and I’m running into issues with the Builds API.
What I’m trying to do
Architecture wise, I have a monorepo with:
-
-
My Goal is that for every repo with this structure, automatically set up:
- A Workers Builds repo connection (GitHub → Cloudflare) with two build triggers per app:
- master → production Worker (no --env)
- staging → staging Worker (--env staging)
Path filters so each trigger only runs when its app (backend/frontend) or shared files change.
So I’m using a custom Node script that calls the Builds REST API directly:
This script parses all
The main blocker right now is the repository connection step.
My script does roughly this (simplified):
With a valid
Now, my questions:
1. GitHub app / account linkage
Knowing that I am super admin on the Cloudflare account where I'm trying to deploy, and that this account already has the Cloudflare Workers & Pages GitHub App installed and authorized for this GitHub organization (with projects already running)
And I’m still getting errors when trying to create the repo connection, even though the same GitHub org has already authorized the app.
- Do I need to do something specific to make the API work?
2. Correct values for
- The documentation is quite lacking on this part. What should these parameters be exactly? Should they be the GitHub handle/login, or the numeric IDs?
The documentation example for the
3. Any known limitations with the Builds API?
Is my approach generally correct, or do I need to pass through the manual steps of the dashboards every time I need to deploy a new project?
Thanks in advance!
What I’m trying to do
Architecture wise, I have a monorepo with:
-
apps/backend -
apps/frontend My Goal is that for every repo with this structure, automatically set up:
- A Workers Builds repo connection (GitHub → Cloudflare) with two build triggers per app:
- master → production Worker (no --env)
- staging → staging Worker (--env staging)
Path filters so each trigger only runs when its app (backend/frontend) or shared files change.
So I’m using a custom Node script that calls the Builds REST API directly:
This script parses all
apps/*/wrangler.jsoncThe main blocker right now is the repository connection step.
My script does roughly this (simplified):
With a valid
CLOUDFLARE_API_TOKEN CLOUDFLARE_ACCOUNT_IDNow, my questions:
1. GitHub app / account linkage
Knowing that I am super admin on the Cloudflare account where I'm trying to deploy, and that this account already has the Cloudflare Workers & Pages GitHub App installed and authorized for this GitHub organization (with projects already running)
And I’m still getting errors when trying to create the repo connection, even though the same GitHub org has already authorized the app.
- Do I need to do something specific to make the API work?
2. Correct values for
provider_account_idrepo_id- The documentation is quite lacking on this part. What should these parameters be exactly? Should they be the GitHub handle/login, or the numeric IDs?
The documentation example for the
repo_idworkers-sdk3. Any known limitations with the Builds API?
Is my approach generally correct, or do I need to pass through the manual steps of the dashboards every time I need to deploy a new project?
Thanks in advance!
Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
86,942Members
Resources
Was this page helpful?
