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-"]
}
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-"]
}