Quick overview This workflow collects a single sound-effect brief via an n8n form, generates multiple variation takes with the ElevenLabs sound-generation API, and uploads each MP3 into a timestamped Google Drive folder, then returns a results page with links and per-take status. How it works Receives a sound-effect brief (plus optional take count, duration, and prompt influence) from an n8n form submission. Validates and clamps the inputs, plans the requested number of takes with slightly varied prompt influence values, and generates a timestamped subfolder name. Creates a new subfolder in Google Drive under the configured parent output folder for this run. Builds one ElevenLabs sound-generation API request per take and calls ElevenLabs to generate an MP3 for each variation. Uploads each generated MP3 to the run’s Google Drive subfolder and records whether each take succeeded or failed. Displays an HTML completion page that links to the Google Drive folder and lists each take with a file link or error message. Setup Create an ElevenLabs HTTP Header Auth credential that sends your API key as the xi-api-key header and select it in the ElevenLabs request step.
Tags
Google DriveWHTTP RequestRelated workflows
See all Google Drive→WCreate studio-quality car listing photos using Google Drive and Gemini 2.5
Quick overview This workflow manually processes car photos from Google Drive, sends each image plus a studio backdrop and logo to the Google Gemini Image API for background replacement and license-plate branding, and uploads the generated studio-style images back to an output Google Drive folder. How it works Runs when you manually execute the workflow. Lists all image files in a specified Google Drive input folder and processes them one at a time. Downloads the current car photo and also lists and downloads the studio asset images (virtual backdrop and logo) from a separate Google Drive folder. Builds a multimodal request that instructs Google Gemini to classify the shot (exterior vs interior/engine), replace the background accordingly, and swap any visible license plate with the provided logo. Sends the request to the Google Gemini image generation endpoint and receives a generated image in the response. Extracts the generated image, names it using the original filename with a “_studio.jpg” suffix, and uploads it to a specified Google Drive output folder. Setup Add Google Drive OAuth2 credentials and set the input, studio assets, and output folder IDs in the Google Drive nodes’ q
WRecognize invoices / receipts from Google Drive and put them into Google Sheets
This workflow allows you to recognize a folder with receipts or invoices (make sure your files are in .pdf, .png, or .jpg format). The workflow can be triggered via the "Test workflow" button, and it also monitors the folder for new files, automatically recognizing them. Video Demo https://youtu.be/mGPt7fqGQD8 1. n8n import glitch After import, the trigger node "When clicking 'Test workflow'" might be disconnected. You need to connect it via 2 arrows to "Google Sheets1" and "Google Drive" nodes. So, the workflow has 2 triggers - via button, and via Google Sheets "new file" event - both of these triggers should be connected to 2 nodes. Here is how it should look like: https://ocr.oakpdf.com/n8n_fix.png 2. Set up RapidAPI HTTP auth key Create new "HTTP header" n8n credential and paste your RapidAPI key from https://rapidapi.com/restyler/api/receipt-and-invoice-ocr-api into it. https://ocr.oakpdf.com/n8n_api_key.png Make sure "HTTP Request" node uses this credential. 3. Set up your Google Auth You need a Google connection to work with your Google Sheets and Google Drive accounts: https://docs.n8n.io/integrations/builtin/credentials/google/oauth-generic/#finish-your-n8n-credential 4. S
Send specific PDF attachments from Gmail to Google Drive using OpenAI
This workflow reads PDF textual content and sends the text to OpenAI. Attachments of interest will then be uploaded to a specified Google Drive folder. For example, you may wish to send invoices received from an email to an inbox folder in Google Drive for later processing. This workflow has been designed to easily change the search term to match your needs. See the workflow for more details. Prerequisites OpenAI credentials. Google credentials. How it works Triggers off on the On email received node. Iterates over the attachments in the email. Uses the OpenAI node to filter out the attachments that do not match the search term set in the Configure node. You could match on various PDF files (i.e. invoice, receipt, or contract). If the PDF attachment matches the search term, the workflow uses the Google Drive node to upload the PDF attachment to a specific Google Drive folder.