codex - 💡(How to fix) Fix Google Drive connector should support creating files in a specific folder [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#20448Fetched 2026-05-01 05:43:02
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Participants
Timeline (top)
labeled ×2
RAW_BUFFERClick to expand / collapse

I am using Codex automations with the Google Drive connector.

Current problem: The Google Drive connector can create a native Google Doc, but the create_file action does not let me choose the destination folder. The file gets created, but it is not placed inside the folder my automation needs.

Needed capability: Please add an optional parent_folder_id parameter to the Google Drive create_file action.

Desired shape: create_file( title: string, mime_type: string, parent_folder_id?: string )

Example: Create a Google Doc named "2026-04-30 Daily Brief" inside folder: 1zHAxnVkrYvdevAq3F7I0NmOGC6fVHx3-

Expected behavior: If parent_folder_id is provided, create the file directly inside that Drive folder. If parent_folder_id is omitted, keep the current behavior.

Why this matters: Recurring automations need predictable output filing. For example, my daily brief automation reads from Google Drive and should save the completed brief into a Daily_Briefs folder. Right now Codex can create the document, but cannot file it in the correct folder.

Suggested implementation: This maps to the Google Drive API files.create request using the parents field:

{ "name": "2026-04-30 Daily Brief", "mimeType": "application/vnd.google-apps.document", "parents": ["1zHAxnVkrYvdevAq3F7I0NmOGC6fVHx3-"] }

extent analysis

TL;DR

Add an optional parent_folder_id parameter to the Google Drive create_file action to specify the destination folder.

Guidance

  • Review the Google Drive API documentation for the files.create request to understand how the parents field can be used to specify the destination folder.
  • Consider modifying the create_file action to accept an optional parent_folder_id parameter, which can be passed to the parents field in the API request.
  • Test the updated create_file action with the parent_folder_id parameter to ensure it correctly creates files in the specified folder.
  • Verify that omitting the parent_folder_id parameter still results in the current behavior of creating files in the default location.

Example

{
  "name": "2026-04-30 Daily Brief",
  "mimeType": "application/vnd.google-apps.document",
  "parents": ["1zHAxnVkrYvdevAq3F7I0NmOGC6fVHx3-"]
}

Notes

The implementation of the parent_folder_id parameter will depend on the specific details of the Codex automation and Google Drive connector, which are not fully specified in the issue.

Recommendation

Apply a workaround by modifying the create_file action to accept the parent_folder_id parameter, as this will allow for more flexible file creation and organization in Google Drive.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING