Google Drive - create file from template and store in shared drive

[michelle0927]

Resolves #19231

Summary by CodeRabbit

• New Features

  • Added optional "Destination Drive" parameter to the create-file-from-template action.
  • Improved parameter labeling: the existing drive field is now explicitly labeled as "Drive Containing Template" for clarity.

• Chores

  • Version update to 0.1.18.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

2 Skipped Deployments

Project	Deployment	Preview	Comments	Updated (UTC)
pipedream-docs	Ignored			Nov 26, 2025 7:03pm
pipedream-docs-redirect-do-not-edit	Ignored			Nov 26, 2025 7:03pm

[coderabbitai]

Walkthrough

The PR adds a new destinationDrive property to the Google Drive create-file-from-template action, enabling users to specify the destination drive separately from the template drive. This allows template files from "My Drive" to be used for creating files in shared drives. Version incremented to 1.4.1.

Changes

Cohort / File(s)	Summary
Google Drive create-file-from-template action components/google_drive/actions/create-file-from-template/create-file-from-template.mjs	Added destinationDrive public prop for specifying destination folder location. Updated drive prop label to "Drive Containing Template". Modified folderId, isSharedDrive, and addParents logic to use destinationDrive instead of drive for destination operations. Version 0.1.17 → 0.1.18.
Package version components/google_drive/package.json	Version bump 1.4.0 → 1.4.1.

Sequence Diagram

sequenceDiagram
    participant User as User
    participant Action as Action: Create File from Template
    participant GDrive as Google Drive API

    Note over User,Action: Before: Single drive prop<br/>After: Separate drive & destinationDrive
    
    User->>Action: Select template (source)
    User->>Action: Select destination folder
    
    rect rgb(240, 248, 255)
    Note over Action: New Logic
    Action->>Action: Validate template from drive
    Action->>Action: Check destinationDrive<br/>for shared-drive status
    end
    
    Action->>GDrive: Create file in destination folder<br/>(with correct drive context)
    GDrive-->>Action: File created
    Action-->>User: Success

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Changes are focused within a single file with a clear, repetitive pattern (replacing drive references with destinationDrive in specific operational contexts)
• New property definition follows existing patterns and prop conventions
• Logic changes are cohesive and logically grouped (folder mapping, shared-drive detection, parent additions)

Possibly related PRs

• #19053: Introduced initial drive-based shared-drive logic for the create-file-from-template action; this PR refactors that approach by separating template and destination drive handling.

Suggested reviewers

• luancazarine
• GTFalcao

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The PR description is minimal, containing only 'Resolves #19231' without addressing the required 'WHY' section from the template. However, the linked issue provides comprehensive context about the objectives.	Expand the PR description to include a 'WHY' section explaining the rationale and the problem being solved, even though the linked issue provides necessary context.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: enabling template file creation in shared drives, which directly addresses the bug reported in the linked issue.
Linked Issues check	✅ Passed	The code changes directly address the bug by introducing a 'destinationDrive' prop that allows files to be created in folders on shared drives using templates from My Drive, resolving the core issue #19231.
Out of Scope Changes check	✅ Passed	All changes are focused on the 'create-file-from-template' component and the version bump is appropriately scoped to the linked bug fix. No extraneous changes are present.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch issue-19231

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 10ad254 and 13ac721.

📒 Files selected for processing (2)

• components/google_drive/actions/create-file-from-template/create-file-from-template.mjs (6 hunks)
• components/google_drive/package.json (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)

• GitHub Check: Publish TypeScript components
• GitHub Check: pnpm publish
• GitHub Check: Lint Code Base
• GitHub Check: Verify TypeScript components

🔇 Additional comments (3)

components/google_drive/package.json (1)

3-3: Package version bump is consistent with action changes

Version increment to 1.4.1 aligns with the updated action (0.1.18) and is appropriate for this behavioral expansion.

components/google_drive/actions/create-file-from-template/create-file-from-template.mjs (2)

12-12: Action version bump matches the new behavior

Updating the action version to 0.1.18 is appropriate for introducing the new destination drive behavior without breaking the key or name.

---

21-28: Template vs destination drive separation looks correct

Splitting the props into:

• drive (now labeled “Drive Containing Template”) for scoping templateId, and
• destinationDrive for scoping folderId,

cleanly models the bugfix requirement: template and destination folder can live on different drives, while the folder picker stays tied to the destination drive.

Also applies to: 40-59

[jcortes]

Hi @michelle0927 lgtm! Ready for QA!

[vunguyenhung]

Hi everyone, all test cases are passed! Ready for release!

Test reports

• [BUG] Google Drive - Cannot Create a Template File in a Destination Folder That's in a Shared Drive - Actions Batch 1: https://www.notion.so/BUG-Google-Drive-Cannot-Create-a-Template-File-in-a-Destination-Folder-That-s-in-a-Shared-Drive--2b7bf548bb5e81e5940df3257f10647e