GitHub OAuth scope issue preventing writes to workflow files in Zapier integration

(I found the "Zapier Platform UI: GitHub integration" tutorial in the community — that's a guide for building a custom integration from scratch and isn't documentation of the official Zapier GitHub app's actual scopes, so flagging that I've already ruled it out.)

We're using the Zapier GitHub integration (via the Zapier MCP server, connected app client id 39c98b34a63d2928778c) to let an AI agent (Claude) commit small, routine fixes directly to our repo — bumping pinned GitHub Actions versions (e.g. actions/checkout@v4 → v7) in our CI/CD workflow files, as part of keeping our security-scanning pipeline current without a human manually editing YAML every time Dependabot flags something.

The problem: the "Create/Update File" GitHub action works perfectly for every file in the repo except anything under .github/workflows/. Writes there fail with a plain 404 Not Found from GitHub's API — no other error detail.

What we've confirmed on our end:

• We isolated it to the path prefix specifically — root files, and even files under .github/ outside workflows/, write fine. Only .github/workflows/* 404s.
• On GitHub's side, writing to that path requires the OAuth token to carry the workflow scope (this is documented GitHub API behavior, separate from repo).
• We checked our Authorized OAuth Apps page (github.com/settings/connections/applications) for the Zapier app and its granted scopes are: gist, notifications, read:org, repo, user. No workflow scope.
• We tried "Replace connection" on the Zapier Connections page hoping it would re-trigger a GitHub consent screen with more scopes — it didn't; it just routed to the GitHub integration's marketing/docs page, no reauth prompt.

What we're asking: does Zapier's GitHub OAuth integration ever request the workflow scope? If it's simply not part of the fixed scope set your app requests at authorization time, can you confirm that so we stop looking for a toggle that doesn't exist — and is there a roadmap item or workaround (a different auth method, a GitHub App instead of OAuth App, etc.) for writing to workflow files specifically?

Happy to provide the exact 404 response body or a HAR if useful for troubleshooting.