The Google Drive integration lets Fabl automatically export your rundowns and scripts to a Drive folder every time you publish, removing the manual step of downloading and uploading files yourself. You choose the destination folder, the file format, and whether exports happen automatically on publish or only when you trigger them manually. Because Fabl writes directly to Google Drive using your own account credentials, exported files appear in Drive just like any other file — shareable, commentable, and searchable by your team.Documentation Index
Fetch the complete documentation index at: https://docs.fabl.studio/llms.txt
Use this file to discover all available pages before exploring further.
What the integration does
- Exports rundowns and scripts to a Google Drive folder you specify
- Supports PDF, CSV, and Google Docs formats
- Can run automatically on every publish event or on demand via a manual export button
- Names exported files using the rundown name and date so they are easy to identify
- Optionally organizes exports into per-show subfolders within your chosen Drive folder
Connect Google Drive
Open Integrations settings
Click your workspace avatar in the bottom-left corner of Fabl and select Settings. Navigate to the Integrations tab and find Google Drive.
Sign in to Google
Sign in with the Google account that owns or has edit access to the Drive folder you want to export into. If you are already signed in, Google prompts you to confirm which account to use.
Grant permissions
Review the permissions Fabl requests. Fabl needs permission to create and update files in Google Drive (it does not read or delete other files in your Drive). Click Allow to continue.
Choose your export folder
In the Google Drive integration settings panel, click Browse to open the folder picker. Navigate to the folder where you want Fabl to deposit exported files, then click Select.
Configure export folder and file format
After connecting, you can adjust all export options at any time from Settings → Integrations → Google Drive → Configure.Export folder
Click Change folder to pick a different destination. Fabl immediately starts writing new exports to the new location — previously exported files remain in the old folder.File format
Choose one or more output formats. Fabl generates a separate file for each selected format on every export:| Format | Best for |
|---|---|
| Sharing read-only rundowns with stakeholders who don’t use Fabl | |
| CSV | Importing rundown data into spreadsheet tools or databases |
| Google Docs | Collaborative editing of scripts directly in Google Workspace |
Subfolder organization
Enable Organize by show to have Fabl automatically create a subfolder named after each show inside your chosen export folder. All rundowns for that show are saved inside its subfolder.File naming
Exported files follow the pattern[Rundown Name] — [YYYY-MM-DD]. You cannot customize the naming pattern at this time, but the date suffix ensures that repeated exports of the same rundown do not overwrite each other.
Automatic vs. manual export
Automatic export
When Auto-export on publish is enabled, Fabl exports the rundown to Google Drive every time you click Publish on a rundown. The export runs in the background — you do not need to wait for it to complete before continuing your work.Manual export
To export a specific rundown without publishing it, open the rundown in Fabl, click the ••• menu in the top-right corner, and select Export to Google Drive. Fabl immediately sends the current version of the rundown to your configured Drive folder.Manual exports reflect the rundown’s current state at the moment you trigger them, including any unpublished changes. Use manual export when you want to share a work-in-progress without officially publishing it.