Templates by Daiki Takayama
Translate documents to multiple languages with Google Drive and DeepL
Who's it for This workflow is perfect for content creators, international teams, and businesses that need to translate documents into multiple languages automatically. Whether you're localizing documentation, translating marketing materials, or creating multilingual content, this workflow saves hours of manual work. What it does Automatically monitors a Google Drive folder for new documents (PDF, DOCX, TXT, or Markdown) and translates them into multiple languages using DeepL API. Each translated document is saved with a language-specific filename (e.g., documenten.pdf, documentzh.pdf) in a designated folder. You receive an email notification when all translations are complete. How it works Monitors a Google Drive folder for new files Detects file format (PDF/DOCX/TXT/Markdown) and extracts text Translates the content into your chosen languages (default: English, Chinese, Korean, Spanish, French, German) Saves translated files with language codes in the filename Sends an email notification with translation summary Optional: Records translation history in Notion database Set up instructions Requirements Google Drive account (for file storage) DeepL API key (free tier: 500,000 characters/month) Gmail account (for notifications) Notion account (optional, for tracking translation history) Setup steps Create Google Drive folders: Create a "Source" folder for original files Create a "Translated" folder for output Copy the folder IDs from the URLs Get DeepL API key: Sign up at DeepL API Copy your API key Configure the workflow: Open the "Configuration (Edit Here)" node (yellow node) Replace folder IDs with your own Set your notification email Choose target languages Set up credentials: Add Google Drive OAuth2 credentials Add DeepL API credentials Add Gmail OAuth2 credentials Activate the workflow and upload a test file! Customization options Change target languages: Edit the targetLanguages array in the Configuration node (supports 30+ languages) Adjust polling frequency: Change trigger from "every minute" to hourly or daily for batch processing Enable Notion tracking: Set enableNotion to true and provide your database ID Add more file formats: Extend the Switch node to handle additional file types Filter by file size: Add conditions to skip files larger than a certain size Supported languages EN (English), ZH (Chinese), KO (Korean), JA (Japanese), ES (Spanish), FR (French), DE (German), IT (Italian), PT (Portuguese), RU (Russian), and 20+ more. Performance Short files (1 page): ~30 seconds for 6 languages Medium files (10 pages): ~2 minutes for 6 languages Large files (100 pages): ~15 minutes for 6 languages Technical Details Trigger: Google Drive folder monitoring (1-minute polling) Translation: DeepL API with automatic source language detection Loop implementation: Split Out + Aggregate pattern for parallel translation Error handling: Catches API failures and sends email alerts Storage: Original file format preserved in translated outputs Notes DeepL free tier provides 500,000 characters/month (approximately 250 pages) For high-volume translation, consider upgrading to DeepL Pro The workflow creates new files instead of overwriting, preserving translation history Google Docs are automatically converted to the appropriate format before translation What You'll Learn This workflow demonstrates several n8n patterns: File format detection and routing (Switch node) Loop implementation with Split Out + Aggregate Binary data handling for file operations Conditional logic with IF nodes (optional features) Cross-node data references Error handling and user notifications Perfect for learning automation best practices while solving a real business problem!
By Daiki TakayamaTransform RSS feeds into blog articles with GPT-4, human review & Google Docs
[Workflow Overview] ⚠️ Self-Hosted Only: This workflow uses the gotoHuman community node and requires a self-hosted n8n instance. Who's It For Content teams, bloggers, news websites, and marketing agencies who want to automate content creation from RSS feeds while maintaining editorial quality control. Perfect for anyone who needs to transform news articles into detailed blog posts at scale. What It Does This workflow automatically converts RSS feed articles into comprehensive, SEO-optimized blog posts using AI. It fetches articles from your RSS source, generates detailed content with GPT-4, sends drafts for human review via gotoHuman, and publishes approved articles to Google Docs with automatic Slack notifications to your team. How It Works Schedule Trigger runs every 6 hours to check for new RSS articles RSS Read node fetches the latest articles from your feed Format RSS Data extracts key information (title, keywords, description) Generate Article with AI creates a structured blog post using OpenAI GPT-4 Structure Article Data formats the content with metadata Request Human Review sends the article for approval via gotoHuman Check Approval Status routes the workflow based on review decision Create Google Doc and Add Article Content publish approved articles Send Slack Notification alerts your team with article details Requirements OpenAI API key with GPT-4 access Google account for Google Docs integration gotoHuman account for human-in-the-loop approval workflow Slack workspace for team notifications RSS feed URL from your preferred source How to Set Up Configure RSS Feed: In the "RSS Read" node, replace the example URL with your RSS feed source Connect OpenAI: Add your OpenAI API credentials to the "OpenAI Chat Model" node Set Up Google Docs: Connect your Google account and optionally specify a folder ID for organized storage Configure gotoHuman: Add your gotoHuman credentials and create a review template for article approval Connect Slack: Authenticate with Slack and select the channel for notifications Customize Content: Modify the AI prompt in "Generate Article with AI" to match your brand voice and article structure Adjust Schedule: Change the trigger frequency in "Schedule Trigger" based on your content needs How to Customize Article Style: Edit the AI prompt to change tone, length, or structure Keywords & SEO: Modify the "Format RSS Data" node to adjust keyword extraction logic Publishing Destination: Change from Google Docs to other platforms (WordPress, Notion, etc.) Approval Workflow: Customize the gotoHuman template to include specific review criteria Notification Format: Adjust the Slack message template to include additional metadata Processing Volume: Modify the Code node to process multiple RSS articles instead of just one
By Daiki TakayamaAutomated customer support with GPT-4o-mini AI triage for Google Forms & Gmail
Transform your Google Form into an intelligent customer support system that automatically analyzes, prioritizes, and responds to every inquiry with AI-powered personalization. Who's it for This workflow is perfect for: Customer support teams handling high volumes of form submissions Small businesses looking to provide instant, professional responses 24/7 E-commerce stores managing product inquiries, complaints, and refunds Service providers triaging appointment requests and support tickets Event organizers responding to registration questions How it works When someone submits your Google Form, this workflow: Triggers instantly from new Google Sheets row Analyzes with AI to determine urgency (low/medium/high), category (technical/sales/support/billing), and sentiment (positive/neutral/negative) Routes intelligently based on priority level to appropriate response template Generates personalized reply using OpenAI, tailored to urgency and sentiment Sends auto-reply via Gmail with professional formatting Alerts your team on Slack for high-priority cases requiring human follow-up Logs everything to tracking sheet for analytics and audit trail Set up steps Time to set up: approximately 15-20 minutes Prerequisites Google Form connected to Google Sheets OpenAI API key (get one at platform.openai.com) Gmail account for sending emails Slack workspace (optional, for team alerts) Configuration steps Connect Google Sheets Trigger to your form response sheet Update column names in "Map Form Column Names" node (default: Name, Email Address, Inquiry) Add OpenAI credentials - uses GPT-4o-mini for cost efficiency (approximately $0.001 per inquiry) Connect Gmail via OAuth2 for sending auto-replies Create tracking sheet with columns: timestamp, name, email, urgency, category, sentiment, summary, keywords, subject, inquiry (Optional) Connect Slack for high-priority notifications Test with sample data before activating Requirements Google Form (free) Google Sheets (free) OpenAI API account (approximately $0.001-0.002 per inquiry with GPT-4o-mini) Gmail account (free) Slack workspace (optional, free tier available) n8n Cloud or self-hosted instance How to customize Adjust triage criteria: Edit the "Analyze with AI Triage" prompt to define what qualifies as high/medium/low urgency for your business. Add custom categories beyond the default five (technical/sales/support/billing/general). Modify response templates: Customize the three response generation nodes to match your brand voice. Add company-specific information, policies, or FAQ links. Adjust tone from formal to casual based on your audience. Add advanced features: Insert CRM integration to check customer history before responding Add condition nodes to route specific categories to different team members Include file attachments (brochures, manuals) based on inquiry type Implement follow-up sequences with Wait nodes Connect multiple notification channels (Discord, email, SMS) Multi-language support: The AI automatically detects and responds in the inquiry's language. Customize prompts with language-specific instructions if needed. Use cases Product support: Auto-respond to "how to use" questions with relevant documentation Complaint management: Immediately acknowledge issues and alert team for urgent follow-up Lead qualification: Instantly engage sales inquiries while routing to appropriate sales rep Appointment requests: Confirm booking inquiries and provide next steps Feedback collection: Thank customers and categorize feedback for analysis
By Daiki TakayamaAutomate cancellation feedback collection with Stripe and Google Sheets
Who's it for This template is perfect for any SaaS business or subscription service using Stripe. Product managers, customer success teams, and founders can use this to automatically collect cancellation feedback without manual follow-up. Ideal for companies looking to reduce churn by understanding why customers leave. What it does When a customer cancels their Stripe subscription, this workflow instantly: Detects the cancellation via Stripe webhook Fetches customer details from Stripe API Sends a personalized feedback survey email with embedded customer information Logs all cancellations to Google Sheets for tracking Receives survey responses via webhook Automatically routes feedback to different Google Sheets based on reason (pricing concerns, feature requests, or other feedback) This organized approach helps you identify patterns in cancellations and prioritize improvements that matter most. How it works Stripe triggers the workflow when a subscription is canceled Customer data is fetched from the Stripe API (email, name, plan details) Personalized email is sent with a survey link containing customer data as URL parameters Cancellation is logged to a Google Sheets "Cancellations" tab When the customer submits the survey, a webhook receives the response Feedback is routed to dedicated sheets based on cancellation reason: Price Concerns → for pricing-related issues Feature Requests → for missing functionality Other Feedback → for everything else Set up steps Setup time: ~20 minutes Prerequisites Stripe account (test mode recommended for initial setup) Google account with Google Sheets Email service (Gmail, Outlook, or SMTP) Survey tool with webhook support (Tally or Typeform recommended) Configuration Stripe webhook: Copy the webhook URL from the "Stripe Subscription Canceled" node and add it to your Stripe Dashboard → Webhooks. Select the customer.subscription.deleted event. Email credentials: Configure Gmail, Outlook, or SMTP credentials in the "Send Feedback Survey Email" node. Update the fromEmail parameter. Survey form: Create a survey form with these fields: Hidden fields (auto-populated from URL): email, customer_id, name, plan Visible fields: reason dropdown ("Too Expensive", "Missing Features", "Other"), comments textarea Configure webhook to POST responses to the "Survey Response Webhook" URL Google Sheets: Create a spreadsheet with 4 sheets: "Cancellations", "Price Concerns", "Feature Requests", and "Other Feedback". Connect your Google account in the Google Sheets nodes. Survey URL: Replace [SURVEY_URL] in the email template with your actual survey form URL. Test: Use Stripe test mode to trigger a test cancellation and verify the workflow executes correctly. Requirements Stripe account with API access Google Sheets (free) Email service: Gmail, Outlook, or SMTP server Survey tool: Tally (free), Typeform (paid), or custom form with webhook capability n8n instance: Cloud or self-hosted How to customize Different surveys by plan: Add an IF node after getting customer details to send different survey links based on subscription tier Slack notifications: Add a Slack node after "Route by Feedback Type" to alert your team about price concerns in real-time Delayed email: Insert a Wait node before sending the email to give customers a 24-hour cooldown period CRM integration: Add nodes to sync cancellation data with your CRM (HubSpot, Salesforce, etc.) Follow-up workflow: Create a separate workflow that triggers when feedback is received to send personalized follow-up offers Custom routing logic: Modify the Switch node conditions to match your specific survey options or add more categories Tips for success Use Stripe test mode initially to avoid sending emails to real customers during setup Customize the email tone to match your brand voice Keep the survey short (2-3 questions max) for higher response rates Review feedback weekly to identify patterns and prioritize improvements Consider offering a discount or incentive for completing the survey
By Daiki Takayama