Google Sheets · Google Drive
Create Google Drive text files from new Google Sheets rows
Create one UTF-8 plain-text file in Google Drive for each new row appended to a selected Google Sheets worksheet. Prepare FileName and Content headers in row 1, connect Google Sheets and Google Drive, browse to the source spreadsheet and worksheet, and optionally choose a destination folder; leaving Parent folder empty saves to My Drive. Both FileName and Content are required. Activate and let the first poll establish a baseline before adding rows. Existing rows and later edits are not imported or synchronized. Append complete rows at the bottom and keep the headers stable while active. Only FileName and Content are copied; other columns remain in the sheet. Includes a fictional English project note with German characters and line breaks. Files inherit destination folder access, no public sharing is added, and manual reruns can create duplicate files.
- 1. Google Sheets · New Row Added
- 2. Filter · Only create files with a name
- 3. Google Drive · Create the row as a text file
View template →Use templateGoogle Drive · Discord
Send new Google Drive files to a Discord channel
Post a Discord notification when a new file is created in a selected Google Drive folder. Connect Google Drive and Discord, browse to the folder to watch, then choose a Discord text channel. Leaving the folder empty watches the connected Drive. The folder scope includes direct children only; subfolders are not scanned. Detection uses file creation time, so moving an older file into the folder is not guaranteed to trigger a notification. Activate the workflow and let its first poll establish a baseline before creating a test file; older files and later edits are not sent. Each message includes the file name, type and direct Drive URL. User, role and everyone mentions are disabled, and Drive links are not expanded automatically. File names and URLs become visible to members of the selected Discord channel, while Drive sharing permissions stay unchanged. Includes a fictional German project document example with no customer data.
- 1. Google Drive · New Files
- 2. Discord · Notify the files channel
View template →Use templateGoogle Drive · Gmail
Email new Google Drive files with Gmail
Send an email when a new file is created in a selected Google Drive folder. Each message includes its name, file type, creation timestamp and a direct Drive link. Connect Google Drive, browse to the folder to watch, connect Gmail and enter a fixed recipient address. Leaving the folder empty watches the connected Drive. Only direct children are monitored; subfolders are not scanned. Detection uses creation time, so moving an older file into the folder is not guaranteed to trigger. Polling may include files created roughly one minute before setup; older files and later edits are not imported. Includes its own fictional Leipzig handoff example with German Unicode. Emails are plain text and appear in the connected Gmail account's Sent folder. File contents, descriptions, owners and attachments are not copied. Recipients can see the file name and link, but Drive sharing permissions stay unchanged. Gmail sending limits apply. Manual reruns or retries after ambiguous provider failures can resend a notification. Use your own email address for the first test.
- 1. Google Drive · New Files
- 2. Gmail · Email the new file notification
View template →Use templateGitHub · Google Drive
Save published GitHub release notes in Google Drive
Archive published GitHub release notes as UTF-8 text files in Google Drive. Each file contains the tag, optional release title, full notes, repository, author, publication time, pre-release flag and original GitHub link. Connect GitHub and Google Drive, browse to a repository and optionally select a destination folder. The Actions filter is prefilled with published; stable releases and published pre-releases are included. Leaving Parent folder empty saves to My Drive. Filenames use repository and release IDs, so tags containing slashes or German characters do not become folder paths. Includes its own fictional English Nürnberg release example. Only new publication events received after activation are processed; existing releases are not imported. Drafts, edits and deleted releases do not create or update files. Markdown remains plain source text; release assets, source code and binaries are not downloaded. This is a release-notes snapshot, not a deployment check or synchronized backup. Files inherit destination folder access; no public sharing is added. Manual reruns or unpublishing and republishing a release can create duplicates.
- 1. GitHub · Release
- 2. Google Drive · Archive GitHub release notes
View template →Use templateGitHub · Google Drive
Save new GitHub pull requests as Google Drive text files
Create a UTF-8 text file in Google Drive whenever a GitHub pull request is opened. Files include the PR title, full description, repository, author, creation time, draft status, source and target branches, and original PR link. Connect GitHub and Google Drive, browse to a repository and optionally select a destination folder. The Actions filter is prefilled with opened; draft PRs are included. Leaving Parent folder empty saves to My Drive. Filenames use the repository ID and PR number. Includes its own fictional English Freiburg example with German characters. Only new opened events received after activation are processed; existing PRs are not imported. Edits, new commits, reviews, closed and reopened PRs do not create or update files. Markdown remains plain source text; code changes, comments and linked attachments are not downloaded. This is a one-time snapshot, not a code backup, reviewer assignment or two-way synchronization. Files inherit destination folder access; no public sharing is added. Manual reruns can create duplicate files.
- 1. GitHub · Pull Request
- 2. Google Drive · Save GitHub pull request as a text file
View template →Use templateGoogle Calendar · Google Drive
Create Google Drive meeting notes for new Calendar events
Create a UTF-8 meeting-notes text file in Google Drive whenever a new Google Calendar event is created. Each file includes the event title, a link to the current calendar schedule, and Agenda, Notes and Action items sections. Connect Google Calendar and Google Drive, browse to a calendar and optionally select a destination folder. The primary calendar is preselected; leaving Parent folder empty saves to My Drive. Activate and let the first poll establish a baseline before creating events. Existing events are not imported; later edits and cancellations are not synchronized. Timed and all-day events are supported. Dates are not copied, so the calendar link remains the source for the current schedule. Includes a fictional English Bremen workshop example with German characters. Descriptions, attendees, locations and attachments are not copied. Files inherit the destination folder access; no public sharing is added. Creates plain-text files, not Google Docs documents. Manual reruns can create duplicate files.
- 1. Google Calendar · New Event
- 2. Google Drive · Create meeting-notes text file
View template →Use templateGitHub · Google Drive
Save new GitHub issues as Google Drive text files
Create a UTF-8 text file in Google Drive whenever a GitHub issue is opened. Files include the issue title, full description, repository, author, creation time and original issue link. Connect GitHub and Google Drive, browse to a repository and optionally select a destination folder. The Actions filter is prefilled with opened. Leaving Parent folder empty saves to My Drive. Each filename uses the repository ID and issue number to distinguish issues across repositories. Includes its own fictional English Leipzig example. Only new opened events received after activation are processed; existing issues are not imported. Edits, comments, closed and reopened issues do not create or update files. Markdown remains plain source text; linked attachments are not downloaded. This is a one-time snapshot, not an issue backup or two-way synchronization. Files inherit destination folder access; no public sharing is added. Manual reruns can create duplicate files.
- 1. GitHub · Issues
- 2. Google Drive · Save GitHub issue as a text file
View template →Use templateSlack · Google Drive
Archive Slack messages as Google Drive text files
Save Slack messages containing [Archive] as UTF-8 text files in Google Drive. Connect Slack and Google Drive, choose source channels and optionally browse to a destination folder. The [Archive] keyword is prefilled and matched anywhere without case sensitivity; bot messages are ignored. Each file contains the original message text, author ID, channel ID, message timestamp and a source channel URL. The filename uses the workspace, channel and message timestamp with a .txt extension. Leaving Parent folder empty saves to My Drive. Includes its own fictional English Bremen handoff example. Add FastHook to the source Slack channel before activation. Leaving Channels empty watches every channel accessible to the connection. Matching human thread replies also create files. Existing messages, edits and deletions are not synchronized; attached files and thread history are not copied. Slack formatting and mentions remain source text. This is a message capture, not a full workspace backup. Files inherit the destination folder access; no public sharing action is added. Manual reruns can create duplicate files.
- 1. Slack · New Keyword Mention
- 2. Google Drive · Save Slack message as a text file
View template →Use templateStripe · Google Drive
Create Google Drive folders for new Stripe customers
Prepare a document folder when a new customer is created in Stripe. Connect Stripe and Google Drive, optionally choose a writable parent folder, then publish. Without a parent, folders are created in My Drive. The folder name includes the Stripe Customer ID and customer name; the ID remains even when the name is blank. Includes its own fictional sandbox customer with German characters. Only customer.created events received after activation are processed. Creating a customer does not confirm payment or a subscription. Existing customers and later edits are not imported or synchronized. This creates an empty folder; it does not copy invoices, payment details, email addresses, tax IDs or metadata, or attach the folder to Stripe. Folder access follows its destination; sharing permissions are not changed. Test with a fictional sandbox customer first. Manually rerunning an event can create another folder with the same name.
- 1. Stripe · Customer Created
- 2. Google Drive · Create customer document folder
View template →Use templateHubSpot · Google Drive
Create Google Drive folders for new HubSpot contacts
Prepare an empty document folder whenever a new contact is created in HubSpot. Connect HubSpot and Google Drive, optionally browse to a writable parent folder, then publish. Without a parent folder, the folder is created in My Drive. Names follow HubSpot {portal ID} - Contact {contact ID}, so contacts from different accounts remain distinguishable. HubSpot creation webhooks provide IDs, not contact names or email addresses. Includes its own fictional contact-created example. Only contact.creation events received after activation are processed; existing contacts and later edits, merges or deletions are not synchronized. This creates folders only: it does not copy documents, attach the folder to the CRM record, invite the contact or change sharing permissions. Access follows the destination folder. Test with one fictional contact first. Manually rerunning an event can create another folder with the same name.
- 1. HubSpot · Contact Creation
- 2. Google Drive · Create contact document folder
View template →Use templateGoogle Drive · Notion
Create Notion review pages for new Google Drive files
Build a document review library in Notion whenever a new file is created in Google Drive. Each child page includes the file name, a clickable Drive link and Review, Notes and Action items sections. Connect Google Drive and Notion, browse to the folder to watch, then select an accessible parent Notion page. Leaving the folder empty watches the connected Drive. Only direct children of the selected folder are monitored; subfolders are not scanned. Detection uses creation time: moving an older file into the folder is not guaranteed to create a page. Polling may include files created roughly one minute before setup; older files, later edits and deletions are not synchronized. Includes its own fictional English document example with German characters. File contents, descriptions and permissions are not copied or changed. The Drive link still requires existing file access. Page access follows the selected Notion parent. This creates child pages, not database rows.
- 1. Google Drive · New Files
- 2. Notion · Create document review page
View template →Use templateGoogle Drive · Slack
Send Slack notifications for new Google Drive files
Notify your Slack channel when a new file is created in a Google Drive folder. Each message includes the file name, type and a direct Drive URL. Connect Google Drive and Slack, browse to the folder to watch, and choose a channel where the FastHook bot can post. Leaving the folder empty watches the connected Drive. The folder scope includes direct children only; subfolders are not scanned. Detection uses file creation time, so moving an older file into the folder is not guaranteed to trigger a notification. Polling may include files created roughly one minute before setup; older files and later edits are not imported. Includes its own fictional English project document example with German characters. Messages preserve literal text and disable link previews. File names and URLs become visible to channel members, but Drive sharing permissions stay unchanged.
- 1. Google Drive · New Files
- 2. Slack · Announce the new Drive file
View template →Use templateGoogle Sheets · Google Drive
Create Google Drive project folders from new Google Sheets rows
Prepare a project workspace automatically from your Google Sheets intake list. Add the header Project in row 1 and enter a project name in each new row. FastHook creates one empty Google Drive folder with that name inside the parent folder you select. Connect Google Sheets and Google Drive, choose the source spreadsheet and worksheet, and optionally choose a writable parent folder; without a parent, folders are created in My Drive. Includes its own fictional English project example. Activate and allow the first poll to establish a baseline before adding rows. Append complete rows at the bottom: existing rows and later edits are not imported. Keep the header unchanged and avoid deleting or reordering rows while active. A Project value is required. Separate rows create separate folders even when their names match. This template does not copy files, change permissions or write a folder link back to the sheet. Access follows the destination folder.
- 1. Google Sheets · New Row Added
- 2. Google Drive · Create project folder
View template →Use templateGoogle Drive · Google Sheets
Log new Google Drive files in Google Sheets
Keep a searchable file register in Google Sheets when new files are created in Google Drive. Each file adds one row with File ID, File name, MIME type, Created and Drive URL. Uses Append Values to write these five values in columns A-E in that order. Column headers are optional: an empty worksheet works immediately, or you can add your own header row. Connect Google Drive and Google Sheets, choose a folder to watch, and select the destination spreadsheet and worksheet. Leaving the folder empty watches the connected Drive. Includes its own fictional English file example. Values are written as plain text; file contents and permissions are never copied or changed. A Drive link still requires existing access. Folder monitoring covers direct children only and uses creation time: moving an older file into the folder may not trigger a row. Polling can include files from roughly the minute before setup; older files, later edits and deletions are not synchronized. Use a private worksheet for the file metadata. This is an append-only register, not a live inventory mirror.
- 1. Google Drive · New Files
- 2. Google Sheets · Append Values
View template →Use templateTrello · Google Drive
Create Google Drive project folders for new Trello cards
Prepare a project workspace in Google Drive whenever a new card is created on your Trello board. The folder takes the card name and is created inside the parent folder you choose. Connect Trello and Google Drive, select a board and optionally a writable destination folder, then publish. With no parent folder selected, folders are created in My Drive. Includes its own fictional English project example. Wait for the Trello trigger to show Connected before creating a card; initial webhook registration can take up to 15 minutes. Only new card creation after activation is processed. Existing cards, copies and later renames are not synchronized. Each distinct card creates a separate folder, even when card names match. This template creates an empty folder and does not copy files, add card attachments or change sharing permissions. Folder access follows its destination in Drive.
- 1. Trello · Create Card
- 2. Google Drive · Create project folder
View template →Use templateGoogle Drive · Trello
Create Trello review cards for new Google Drive files
Build a document review queue in Trello when new files are created in Google Drive. Each card uses the file name and includes a direct Drive link plus review instructions. Connect Google Drive and Trello, choose the folder to watch, then select a board and list. Leaving the folder empty watches the connected Drive. Includes a separate fictional English design-brief example. Only direct children of the selected folder are watched. Detection uses creation time: moving older files into the folder is not guaranteed to create a card. Polling can include files from roughly the minute before setup; older files and later edits are not synchronized. Cards have no automatic assignee or due date. The Drive link does not grant access; reviewers need existing file permissions.
- 1. Google Drive · New Files
- 2. Trello · Create document review card
View template →Use templateGoogle Drive · Telegram Bot
Send Telegram alerts for new Google Drive files
Notify your Telegram chat when new files are created in Google Drive. Each message includes the file name and a direct Drive link. Connect Google Drive and Telegram, choose the folder to watch, and select your chat. Leaving the folder empty watches the connected Drive. Includes its own English document example. The folder scope is direct children only, and detection uses file creation time: moving an older file into the folder is not guaranteed to trigger an alert. Polling can include files from roughly the minute before setup; older files and later edits are not imported. A link does not grant access: recipients still need existing Drive permissions. The Telegram bot needs permission to post in the selected chat.
- 1. Google Drive · New Files
- 2. Telegram Bot · Announce new Drive file
View template →Use templateGmail · Google Drive
Save Gmail attachments to Google Drive
Save each new Gmail attachment in Google Drive, organized by sender and received date, then make the uploaded file readable by anyone with its link. Connect Gmail and Google Drive, review sharing settings, and activate the workflow.
- 1. Gmail · New Attachment Received
- 2. Google Drive · Create sender/date folder
- 3. Google Drive · Upload attachment
- 4. Google Drive · Share uploaded file
View template →Use templateGmail · Google Drive · Telegram Bot
Gmail attachments to Drive and Telegram
Save every new Gmail attachment in a sender/date folder, make the uploaded file public, and send its link to Telegram.
- 1. Gmail · New Attachment Received
- 2. Google Drive · Create sender/date folder
- 3. Google Drive · Upload attachment
- 4. Google Drive · Make attachment public
- 5. Telegram Bot · Send public link to Telegram
View template →Use template
