Workers CI Read scope not available

I'm preparing to migrate several Pages projects to Workers, and need an equivalent to the Pages build webhooks, so that when I publish content in my CMS (Sanity), a build is triggered (Astro, mostly static but some dynamic routes).

It looks like I'll need to hit this Workers API endpoint (likely combined with a trigger ID obtained from other endpoints in the same "Worker Builds" section of the API docs):
https://developers.cloudflare.com/api/resources/workers_builds/subresources/triggers/methods/create_build/
But it requires

Workers CI Write

Workers CI Write

Workers CI Write

Workers CI Write permission, and none of the permissions in the API token setup match that. I tried adding all Workers-related permissions and I'm still getting an "invalid token" error message for any Workers Builds API endpoint.

Ideally Workers would have a built-in build trigger setup like Pages does, but since that doesn't seem to exist where can I create the correct token for this API?

Cloudflare API | Workers Builds › Triggers › Create Manual Build

Interact with Cloudflare's products and services via the Cloudflare API

Tom CallahanOP•12/16/25, 3:29 PM

I don't really understand how CloudFlare is pushing Workers as a replacement for Pages when building static sites when there appears to be no simple way to trigger a build via API. I get it with a traditional Worker where you only need a new build when code changes, but Pages is a very different use case -- our site gets "built" probably 100 times triggered by content changes for every actual code change.

Tom CallahanOP•12/16/25, 5:25 PM

Yeah but the implementation of connected services like R1, D2, KV is easier in Workers...

I just got this working -- it turns out that I was looking at the right endpoint, but I couldn't get it working with an API token, only with the older API key method that they warn against using. So either I'm doing something wrong (even though the same API token works fine for other API endpoints) or the docs saying these Workers Builds endpoints support using an API token are incorrect.

Also once I was able to make API calls, I had to make two other API calls first, one to list all of my Workers to find the 'external script id' of the one I wanted to target (which is not exposed anywhere in the dashboard, and it's actually the internal ID of the Worker, so I'm not sure why it's called "external"), and then using that script ID to call another endpoint to list the build triggers for that Worker (a build trigger is your GitHub/GitLab integration, I guess?) in order to get the Trigger ID to plug into the "Create Manual Build" endpoint. Now I can hit that last endpoint and it triggers a build as if GitHub had notified CF of a code change.

Fortunately those IDs seem to be stable, so now that I have the trigger ID I can stick that in an environment variable.

But the API nomenclature is not consistent with what things are called in the dashboard and their general Workers documentation, which is confusing -- "Workers" are "scripts" and "Git integrations" are "triggers". And what descriptions there are in the API docs are very sparse and uninformative. It also doesn't help that at least some of the API CURL examples are missing required URL parameters or any suggestion of what the values of those parameters might look like -- I had to take some wild guesses and lucked out.

Workers CI Read scope not available

Similar Threads

Similar Threads

Similar Threads