Workflow Templates

Description An AI-powered workflow that analyzes any website to identify missing pages that would improve user experience and business performance. Submit a URL, and the system detects existing pages, researches competitors using Perplexity, and generates a professional gap analysis report with prioritized recommendations—saved directly to Google Docs. What this workflow does This automation delivers a complete website page gap analysis: Smart page detection:** Automatically scans website HTML and identifies 15 common page types (About, Contact, Services, Blog, Portfolio, Pricing, FAQ, Testimonials, Team, Careers, Privacy, Terms, etc.) Business type classification:** Determines if the site is ecommerce, portfolio/agency, blog, SaaS, or service-based to tailor recommendations Competitor research:** Uses Perplexity to research 5-7 top competitors in the same industry and identify their page structures AI gap analysis:** GPT-4.1-mini with web search compares the website against industry standards and competitor best practices Prioritized recommendations:** Generates High/Medium/Low priority suggestions with business value explanations and actionable content ideas Google Docs report:** Saves a professional gap analysis report ready to share with clients or stakeholders Setup requirements Tools you'll need: Active n8n instance (self-hosted or n8n Cloud) Google Docs with OAuth access OpenAI API key (GPT-4.1-mini access with web search) Perplexity API key (for competitor research) Estimated setup time: 15–20 minutes Step-by-step setup 1. Connect Google Docs In n8n: Credentials → Add credential → Google Docs OAuth2 API Complete OAuth authentication Create a new Google Doc for storing reports (or use an existing one) Open "Save Report to Google Docs" node Paste the Google Doc URL in the documentURL field 2. Add OpenAI API credentials Get API key: https://platform.openai.com/api-keys In n8n: Credentials → Add credential → OpenAI API Paste your API key Open "OpenAI GPT-4.1 Mini with Web Search" node Select your OpenAI credential Ensure model is set to gpt-4.1-mini Verify Web Search is enabled in the built-in tools section 3. Add Perplexity API credentials Get API key: https://www.perplexity.ai/settings/api In n8n: Credentials → Add credential → Perplexity API Paste your API key Open "Perplexity Competitor Research Tool" node Select your Perplexity credential 4. Share the form URL Open "Submit Website URL for Analysis" node Copy the Form URL from the node settings Share this URL with anyone who needs to run website audits The form accepts a single field: Website URL 5. Test the workflow Open the Form URL in your browser Enter a test website: https://example.com Submit the form Wait 30-60 seconds for the analysis to complete Check your Google Docs—the gap analysis report should appear Verify that: Existing pages are correctly detected Business type is identified Competitor research is included Recommendations are prioritized and actionable 6. Activate the workflow Toggle the workflow to Active at the top The form will now accept submissions 24/7 Each submission generates a new report appended to your Google Doc How it works 1. URL submission via form User opens the form link and submits a website URL they want to analyze. The form triggers the workflow immediately. 2. HTML fetch and extraction The workflow sends an HTTP request to the submitted URL and retrieves the complete HTML source code of the website's homepage. 3. Automated page detection A code node analyzes the HTML to detect 15 common page types: Navigation pages:** Home, About, Contact, Services, Products Content pages:** Blog, Portfolio, Pricing, FAQ Social proof pages:** Testimonials, Team, Careers Legal pages:** Privacy Policy, Terms of Service The detection works by: Scanning all internal links in the HTML Matching URL patterns (e.g., /about, /contact-us, /services) Searching for navigation keywords in anchor text Normalizing URLs (removing query params, anchors, trailing slashes) 4. Business type classification The code also identifies the website's business type based on HTML content patterns: Ecommerce:** Detects shopping cart, checkout, product pages Portfolio/Agency:** Identifies portfolio, case studies, creative work Blog/Content site:** Finds blog posts, articles, news sections SaaS/Software:** Detects subscription, cloud platform, software keywords Service/Agency:** Identifies consulting, marketing, agency services General:** Default if no specific patterns match 5. Deep competitor research with Perplexity The AI Agent instructs Perplexity to: Crawl the target website thoroughly (navigation, footer, hidden menus) Research 5-7 top competitors in the identified business type Document each competitor's page structure Identify industry-standard pages that successful sites consistently have Perplexity focuses only on user-facing pages and ignores technical files (sitemap.xml, robots.txt, admin pages). 6. AI gap analysis and recommendations GPT-4.1-mini with web search: Compares the website's existing pages against competitor structures Identifies genuinely missing pages (cross-references with detected existing pages) Prioritizes recommendations based on business impact (High/Medium/Low) Provides specific business value explanations for each recommendation Suggests actionable content for each missing page Includes competitor examples showing how others use these pages Critical filtering rules: Never recommends pages already detected Excludes technical files and admin pages Only suggests pages with clear business value Each recommendation must be justified 7. Professional report generation The AI Agent outputs a structured report containing: Website Overview:** URL, business type, analysis date Pages Confirmed as Existing:** Formatted list of detected pages Gap Analysis Summary:** Total pages analyzed, existing vs. missing count Recommended Pages to Add:** Detailed recommendations with priority, business value, content suggestions, and competitor examples Implementation Priority Summary:** Quick-reference lists by priority level Next Steps:** 2-3 actionable implementation steps 8. Save to Google Docs The complete report is inserted into your Google Docs document. Each new analysis appends to the same document, creating a running archive of all audits performed. Key features ✅ Automatic page detection: Scans HTML and identifies 15 common page types without manual input—no need to know the site structure beforehand ✅ Business type intelligence: Classifies websites into 6 business categories to provide industry-relevant recommendations ✅ Perplexity-powered research: Deep competitor analysis covering 5-7 top sites in the same niche with complete page inventories ✅ Smart filtering: Never recommends pages that already exist, even if they use different naming conventions or URL structures ✅ Priority-based recommendations: Every suggestion labeled High/Medium/Low with clear business justification—know what to build first ✅ Actionable content ideas: Not just "add a blog"—specific suggestions for what content should go on each recommended page ✅ Competitor examples: See how successful competitors use each recommended page type in their own sites ✅ Google Docs integration: Professional reports saved automatically—no downloads, no formatting, ready to share ✅ Form-based workflow: Single URL submission—anyone can run audits without touching n8n Troubleshooting HTML fetch fails SSL certificate issues:** Some websites block automated requests. Try adding "rejectUnauthorized": false in HTTP Request options. Cloudflare/bot protection:** Sites with aggressive protection may block the request. Test with a simple site first (like your own). Timeout errors:** Increase timeout setting in HTTP Request node to 30-60 seconds for slow-loading sites. Pages not detected correctly Non-standard URL structure:** The workflow detects pages using common patterns (/about, /contact, etc.). If a site uses unusual URLs like /company-info instead of /about, manual review may be needed. Single-page websites:** Sites built as SPAs (single-page applications) with JavaScript routing may not have distinct page URLs in HTML. The workflow works best with traditional multi-page sites. Check detection details:** The code node outputs detection_details showing exactly what was found. Review this to debug false negatives. Perplexity API errors Rate limits:** Perplexity has usage limits. If you hit them, wait or upgrade your plan. API key invalid:** Verify the key is correct at https://www.perplexity.ai/settings/api Quota exceeded:** Check your Perplexity dashboard for remaining credits. OpenAI web search not working Web search disabled:** Ensure "Web Search" is enabled in the OpenAI Chat Model node under "Built-in Tools" Search context size:** Set to "Medium" for balanced performance Model compatibility:** Web search only works with GPT-4 models, not GPT-3.5 Report not saving to Google Docs Re-authenticate OAuth:** Go to Credentials → Google Docs OAuth2 API → Reconnect Document URL format:** Ensure the URL is a valid Google Docs link (not a folder or Sheets link) Permissions:** Verify the connected Google account has edit access to the document Document locked:** Check if the document is open in another tab with unsaved changes AI recommendations are too generic Perplexity research quality:** The AI relies on Perplexity's research. If competitors have similar structures, recommendations may overlap. Try analyzing a more unique website. Business type misclassification:** Check the detected business_type in the code output. If it's wrong, the recommendations will be off-target. Improve prompt:** Edit the AI Agent system prompt to emphasize more specific or creative recommendations for your niche. Use cases Web design agencies: Audit client websites before proposals. Show exactly which pages are missing compared to competitors, with business justification for each recommendation. Win more projects by demonstrating data-driven insights. SEO consultants: Include page gap analysis in site audits. Identify missing pages that competitors rank for (FAQ, pricing, testimonials). Provide clients with actionable roadmaps for site expansion. In-house marketing teams: Analyze competitor websites quarterly to spot new page types or content strategies. Keep your site competitive by identifying gaps before leadership asks about them. Freelance developers: Offer value-add services to existing clients. Run audits on their sites, identify quick wins (missing FAQ, testimonials, pricing pages), and sell additional development work. Startup founders: Before hiring a design agency, understand what pages you actually need. Get a competitor-researched report showing industry standards for your business type—save time and budget. Content strategists: Identify content opportunities beyond blog posts. See which informational pages (FAQ, case studies, resource libraries) competitors have that you're missing. Expected results Time savings:** 2-3 hours saved per website audit (manual competitor research eliminated) Analysis speed:** Complete gap analysis in 30-60 seconds vs. hours of manual work Competitor coverage:** Research 5-7 competitors automatically vs. 1-2 manual comparisons Report quality:** Professional, shareable reports vs. rough notes or spreadsheets Actionability:** Prioritized recommendations with business value vs. generic "add more pages" advice Scalability:** Run 50+ audits per day without additional effort Support Need help or custom development? 📧 Email: info@isawow.com 🌐 Website: https://isawow.com/

Trend2Content This n8n workflow (named Trend2Content) takes a short topic input from a small web form, scrapes recent/top social content for that topic (via an Apify act), aggregates the raw text, passes that aggregated content into a LangChain AI agent (Google Gemini in this flow) which returns a structured content output (topic summary, blog post title ideas, tweet hooks), formats that output, and appends the results into a Google Sheet. It’s a lightweight: Topic → Trending Content → AI Ideas → Sheet pipeline for fast content ideation. How It Works (Step-by-Step) On Form Submission The user fills a single field Topic (webhook/form trigger). X Scraper (HTTP Request) Calls an Apify act run-sync-get-dataset-items with: searchTerms: [{{ $json.Topic }}] maxItems: 20 to fetch social posts for that topic. Edit Fields (Set) Extracts fullText from each scraped item and stores it in a Content field. Aggregate Aggregates the Content field so the AI agent receives one combined input rather than many separate items. Google Gemini Chat Model (LM) + AI Agent (LangChain Agent Node) The agent uses a templated system prompt + the aggregated content to generate a structured response with: Topic summary Blog title ideas Tweet hooks The agent is connected to a Structured Output Parser node to force a predictable JSON schema. Code in JavaScript Transforms the structured JSON into sheet-friendly strings (joins arrays with bullets). Append Row in Sheet (Google Sheets) Appends the generated blog_post_titles and tweet_hooks to the target Google Sheet. (Optional) Sticky notes and internal meta nodes exist for documentation and board organization. Quick Setup Guide 👉 Demo & Setup Video 👉 Sheet Template 👉 Course Nodes of Interest You Can Edit 1. On Form Submission (formTrigger) Edit form fields (add author, language, region, or filters). Change webhook behaviour or require authentication. 2. X Scraper (HTTP Request) URL:** Change to another Apify act or another scraping API. jsonBody:** Change maxItems, sort (Top/Recent), or modify searchTerms (e.g., topic + hashtag). Headers:** Set the Authorization: Bearer token (Apify). Add pagination or query parameters if switching scraper APIs. 3. Edit Fields (Set) Map additional fields (author, date, source URL). Add filtering logic (remove short posts, retweets, duplicates). 4. Aggregate Customize aggregation strategy: Concatenate Sample top N Deduplicate before combining 5. Google Gemini Chat Model / AI Agent / Structured Output Parser Edit systemMessage and prompt template (tone, format, extra outputs). Tune LM parameters (temperature, max tokens). Update schema to request: Sentiment Key quotes Additional formats 6. Code in JavaScript Modify formatting (CSV-ready, add timestamp). Add metadata columns. Add deduplication or length checks before write. 7. Append Row in Sheet (Google Sheets) Change spreadsheet ID or sheet name. Add more columns. Switch from Append to Upsert. Configure batch appends. What You’ll Need (Credentials) 1. Apify API Token Used in the HTTP Request node. Set in header: Authorization: Bearer YOUR_APIFY_TOKEN 2. Google Sheets OAuth2 Credentials Must include spreadsheets scope. Required for appending rows. 3. Google / PaLM / Google Gemini API Credentials Used by the LangChain / Google Gemini node. Optional n8n webhook URL (for mounting the form). Monitoring credentials (Slack webhook, Sentry, etc.) for alerts. Recommended Settings & Best Practices Enable workflow only after testing (active: true). Limit maxItems (20–50 recommended). Sanitize & dedupe content before sending to the AI. Always use a Structured Output Parser for reliable JSON. Set low temperature (0.0–0.6) for consistent results. Add retries and exponential backoff for external APIs. Add logging or Slack alerts for failures. Keep execution log columns in the sheet (status, error_message, run_time). Store workflow JSON in version control. Monitor API rate limits (Apify + Google). Avoid writing scraped PII into public sheets. Customization Ideas Add output types: Instagram captions LinkedIn posts Video scripts Email subject lines Add sentiment / trend scoring. Add language detection & translation. Store aggregated content in a vector database (Pinecone / Chroma). Schedule runs using Cron trigger. Add multiple data sources (Reddit, RSS, HackerNews). Add approval workflow (Slack / Notion). Add metadata columns: source_urls top_authors most_shared Tags #content-ideation' #social #ai #google-gemini #apify #google-sheets #n8n

How it works This workflow automatically publishes Instagram and Facebook posts using Google Sheets as a content calendar. Users add post details to a sheet, and the workflow handles scheduling, image processing, posting, and status updates without manual intervention. Step-by-step Scheduled Trigger The workflow runs automatically at a fixed interval (for example, every 15 minutes) to check for posts that are ready to be published. Configuration & Credentials A configuration step stores reusable values such as spreadsheet ID, sheet name, and platform settings, keeping the workflow easy to customize and secure. Data Retrieval & Filtering Posts are read from Google Sheets and filtered to include only rows marked as “Pending” and scheduled for the current time or earlier. Image Handling If an image link is provided, the workflow downloads the image from Google Drive. If no image is present, the post continues as text-only. Platform Routing Based on the selected platform (Instagram, Facebook, or both), the workflow routes the post to the appropriate publishing path. Social Media Publishing The post is published to Instagram and/or Facebook using the connected business account credentials. Status Update After publishing, the workflow updates the original Google Sheet with the post status (Success or Failed), published timestamp, and error message if applicable.

B2B Lead Enrichment | Attio CRM This n8n template automates B2B lead research and enrichment for Attio CRM. It combines data from Apollo.io, LinkedIn scraping, and news sources with AI-powered analysis to generate actionable sales intelligence - turning hours of manual BDR research into minutes. Who is this for? Sales teams using Attio CRM who want to reduce time spent on lead research BDRs/SDRs who need rich prospect context before outreach Revenue operations teams looking to automate CRM enrichment at scale What problem does this workflow solve? Before reaching out to a prospect, sales reps typically spend 15-30 minutes researching company background, recent news, leadership team, and LinkedIn activity. This workflow automates that entire research process, freeing BDRs to focus on relationship building instead of data gathering. How it works Trigger: Manually execute (adapt to webhook or form trigger for automation) Apollo Enrichment: Fetches comprehensive company data by domain Parallel Processing: Three branches run simultaneously: News articles → Tavily extraction → AI summary LinkedIn company page → Scrape Creators → AI summary Leadership search (with web search) → Apollo person lookup → LinkedIn profiles → AI summary Validation: An LLM Critic agent verifies all claims using web search Final Output: Lead Enrichment Agent generates a structured dossier CRM Sync: Updates Attio company and people records Good to Know Estimated API Costs (per enrichment): Apollo.io: Varies by plan (credits-based) Scrape Creators: ~$0.01-0.05 per profile Tavily: ~$0.01 per extraction OpenAI GPT-4o: ~$0.10-0.30 depending on content length Rate Limits: Leadership profiles are processed sequentially to respect API limits. For bulk enrichment, consider adding delays between executions. Requirements Apollo.io account with API access Scrape Creators API key (for LinkedIn scraping) Tavily API key (for article extraction) OpenAI API key (GPT-4o model access) Attio CRM account with API access Setup Import the workflow into n8n Configure credentials for each service: Apollo API (HTTP Header Auth with x-api-key) Scrape Creators API Tavily API OpenAI API Attio API Add these custom fields to your Attio Companies object: positioning (text) conversation_points (text) leadership_conversations (text) enrichment_status (select with "complete" option) Test with a single domain before running at scale Customizing this workflow Trigger: Replace manual trigger with a webhook (real-time enrichment on new leads) or schedule node (batch processing) AI Prompts: Adjust the system prompts in AI agents to match your industry or ideal customer profile Output Fields: Modify the final Code node to map to your specific Attio field structure News Timeframe: Change the 6-month lookback in Apollo:LatestNews to your preferred range Leadership Depth: Adjust the number of leadership profiles to enrich based on your needs Made by www.fenrirlabs.nl

Cloudflare Incident Monitoring & Escalation Workflow 🚀 Try Decodo — Web Scraping & Data API (Coupon: TRUNG) Decodo is a powerful public data access platform offering managed web scraping APIs and proxy infrastructure to collect structured web data at scale. It handles proxies, anti-bot protection, JavaScript rendering, retries, and global IP rotation—so you can focus on data, not scraping complexity. Why Decodo Managed Web Scraping API with anti-bot bypass & high success rates Works with JS-heavy sites; outputs JSON/HTML/CSV Easy integration (Python, Node.js, cURL) for eCommerce, SERP, social & general web data 🎟️ Special Discount Use coupon TRUNG to get the Advanced Scraping API plan — 23,000 requests for $5. Who this workflow is for For DevOps, SRE, IT Ops, and Platform teams running production traffic behind Cloudflare who need reliable incident awareness without alert fatigue. Use it if you want: Continuous Cloudflare incident monitoring Clear severity-based routing Automatic escalation into JIRA Clean Slack & Telegram notifications Deduplicated, noise-controlled alerts What this workflow does This workflow polls the Cloudflare Status API, detects unresolved incidents, scores their impact, and routes them to the right channels. High-impact incidents are escalated to JIRA. Lower-impact updates are notified (or skipped) to reduce noise. How it works (high level) Runs on a fixed schedule (e.g. every 5 minutes) Fetches current Cloudflare incidents Stops early if no active issues exist Normalizes and scores incidents (severity, impact, affected service) Deduplicates previously-alerted incidents Builds human-readable notification payloads Routes by impact: High → create JIRA incident + notify Low → notify or suppress Sends alerts to Slack and Telegram Requirements Decoco Scrapper API credential n8n (self-hosted or Cloud) Cloudflare Status API (public) Slack bot (chat:write) Telegram bot + chat ID JIRA project with issue-create permission Optional LLM credentials (summarization/classification) Notes All secrets are stored in n8n Credentials Workflow is idempotent and safe to rerun No assumptions about root cause or remediation Built for production-grade incident visibility with n8n.

⏺ 🚀 How it works Fully automates your inbound and outbound voice sales pipeline — from live call qualification to CRM pipeline management — with multi-agent AI and automatic lead nurturing if a prospect doesn't book. 📞 Receives end-of-call reports from Vapi or Retell AI via webhook — works with both providers out of the box 🧠 Qualifies every inbound lead using BANT scoring (Budget · Authority · Need · Timeline) powered by Claude Haiku 📅 Detects appointment intent and preferred meeting time using GPT-4o before touching your CRM 🗂️ Upserts the contact and creates a pipeline opportunity in GoHighLevel automatically — no duplicates 💬 Analyses objections and generates a rebuttal script using Claude Sonnet (feel-felt-found + Challenger Sale) 📝 Writes a professional CRM note from the call summary using Gemini 2.0 Flash — ready to sync 🔁 Enrols unqualified leads into a GoHighLevel nurture workflow automatically for long-term follow-up 📤 Fires prioritised outbound calls every morning at 9 AM via Vapi — GPT-4o Mini ranks leads by conversion probability 📊 Logs every call (inbound + outbound) to Supabase and Google Sheets for full pipeline reporting 🛠️ Set up steps Estimated setup time: ~45 minutes Webhook — copy the webhook URL and paste it into your Vapi or Retell dashboard as the end-of-call report URL GoHighLevel — connect your HighLevel OAuth2 credential; set your Pipeline ID, Hot Stage ID, and Nurturing Stage ID in the opportunity nodes (Opportunities → Settings → Pipelines) Anthropic — connect your Anthropic API credential; used for Claude Haiku (BANT qualification) and Claude Sonnet (objection handling) OpenAI — connect your OpenAI API credential; used for GPT-4o (booking intent detection) and GPT-4o Mini (outbound lead ranking) Google Gemini — connect your Google Gemini API credential; used for CRM note writing with gemini-2.0-flash Vapi — add your Vapi API key to the HTTP Request node header; set your Phone Number ID and Assistant ID in the outbound call node (Vapi Dashboard → Phone Numbers / Assistants) Supabase — connect your Supabase API credential; create the voice_call_logs table using the SQL in the setup sticky note inside the workflow Google Sheets — connect Google Sheets OAuth2; set your Spreadsheet ID and ensure a sheet named Voice Call Log exists with the columns listed in the setup sticky note Follow the sticky notes inside the workflow — each section has a one-liner setup guide 📋 Prerequisites Vapi or Retell AI account with an active phone number and assistant configured Anthropic API key (Claude API access) OpenAI API key (GPT-4o and GPT-4o Mini access) Google Gemini API key GoHighLevel account with at least one pipeline and automation workflow set up Supabase project with the voice_call_logs table created Google Sheets spreadsheet set up as your call log --- Custom Workflow Request with Personal Dashboard kumar@smartflowcraft.com https://www.smartflowcraft.com/contact More free templates https://www.smartflowcraft.com/n8n-templates

Description This n8n workflow automatically publishes posts to Instagram Business accounts and Facebook Pages using Google Sheets as your content calendar. You schedule posts in the sheet, and n8n processes them, uploads media (if any), posts via Meta’s Graph API, and updates the sheet with success/failure. n8n How it Works Google Sheets rows marked “Pending” and due for publishing are picked up by a scheduled trigger. Posts are then routed to the proper social platforms and published via Meta’s Graph API. Finally, n8n writes back the publish status and timestamp to the sheet. n8n 🧠 Step-by-Step 1️⃣ Scheduled Trigger The workflow automatically checks Google Sheets at fixed intervals (e.g., every 15 min) for posts that are ready (status = Pending, publish time reached). 2️⃣ Config & Credentials Store reusable settings including: Google Sheets ID & Sheet name Meta App credentials (App ID, App Secret) Access token for Meta Graph API Instagram Business Account ID Facebook Page ID These configs make the workflow modular and secure. 3️⃣ Setup: Create a Meta (Facebook) App To post via the Graph API, you must first set up a Meta developer app: 🔗 Create App (Meta for Developers): Go here to start: https://developers.facebook.com/docs/development/create-an-app/ Steps: Log in at Meta for Developers. Click Create App and choose Business as the app type. Facebook Developers Add a name and contact email. In the app dashboard, Add Product → choose Instagram Graph API and Facebook Login. 📌 After creation, your app will have an App ID and App Secret in Settings → Basic — save both for n8n. 4️⃣ Link Accounts & Get IDs Before publishing you need: Instagram Business account (not a personal account) Facebook Page linked to that Instagram account Link them in Facebook Page settings → Linked Accounts. Then, generate an access token with permissions (instagram_basic, pages_show_list, etc.) using the Graph API Explorer and your new Meta app. From the token response or via Graph API calls, extract: Facebook Page ID Instagram Business Account ID These go into your n8n nodes for publishing. 5️⃣ Fetch & Filter Posts Read rows from Google Sheets and filter those ready to publish (status = Pending, scheduled time reached). 6️⃣ Image Handling If an image link is present, download or retrieve it (Google Drive or external URL). If not, continue with a text-only post. 7️⃣ Platform Routing Route the post to: Instagram publishing branch Facebook publishing branch (or both depending on the sheet’s platform column) 8️⃣ Posting via Meta Graph API Instagram Use Graph API endpoints to create and publish media containers and then make the publish call. Facebook Use Graph API to post to the Facebook Page feed (via /feed or /photos endpoint). 9️⃣ Update Sheet Status After each attempt, update Google Sheets with: Status (Success/Fail) Published timestamp

This template demonstrates how to provide an interactive chatbot for your work history based off your CV. Unanswered questions and follow-up email contacts are sent to you via Telegram. Use case: link on your profile to not only show off you AI workflow skills but also to provide an interactive chatbot about your work history for prospective employers. Good to Know It will require access to an OpenAI API Key (free for low usage) and setting up a bot in Telegram (free). How it Works The n8n inbuilt chat node will be hosted on n8n services to provide the chat interface. You will upload your CV either exported from LinkedIn or exported yourself to Microsoft OneDrive along with a simple text file explaining some other information about you. On each chat interaction the PDF and text file are used as tools to get context information for the chatbot to respond. If a question cannot be answered reliably, a subworkflow will be called to capture that question and send it to you as a telegram message. If the person chatting supplies their email address, this will be sent to you via a Telegram message along with other information the user provides. How to use After importing the template, create the subworkflows so that they can be used a Tools by the AI Node. Don't forget to add the Execute sub-workflow trigger. Setup credentials for Open AI, OneDrive and telegram. Upload your CV & text file summary to OneDrive and replace the document IDs in the get_documents sub-workflow. Activate the workflow so that publicly available chat will get generated on n8n.

Who is this template for? This template is ideal for small businesses, agencies, and solo professionals who want to automate appointment scheduling and caller follow-up through a voice-based AI receptionist. If you’re using tools like Google Calendar, Airtable, and Vapi (Twilio), this setup is for you. What problem does this workflow solve? Manual call handling, appointment booking, and email coordination can be time-consuming and prone to errors. This workflow solves that by automating the receptionist role: answering calls, checking calendar availability, managing appointments, and storing call summaries—all without human intervention. What this workflow does This Agent Receptionist manages inbound voice calls and scheduling tasks using Vapi and Google Calendar. It checks availability, books or updates calendar events, sends email confirmations, and logs call details into Airtable. The workflow includes built-in logic for slot management, email triggers, and storing call transcripts. Setup Instructions Duplicate Airtable Base: Use this Airtable base templateBASE LINK Import Workflow: Load provided JSON into your n8n instance. Credentials: Connect your Google Calendar and Airtable credentials in n8n. Activate Workflow: Enable workflow to get live webhook URLs. Vapi Configuration: Paste provided system prompt into Vapi Assistant. Link the appropriate webhook URLs from n8n (GetSlots, BookSlots, UpdateSlots, CancelSlots, and end-of-call report). Disclaimer Optimized for cloud-hosted n8n instances. Self-hosted users should verify webhook and credential setups.

🎶 Add liked songs to a monthly playlist > This Workflow is a port of Add saved songs to a monthly playlist from IFTTT. When you like a song, the workflow will save this song in a monthly playlist. E.g.: It's June 2024, I liked a song. The workflow will save this song in a playlist called June '24. If this playlist does not exist, the workflow will create it for me. ⚙ How it works Each 5 minutes, the workflow will start automatically. He will do 3 things : Get the last 10 songs you saved in the "Liked song" playlist (by clicking on the heart in the app) and save them in a NocoDB table (of course, the workflow avoid to create duplicates). Check if the monthly playlist is already created. Otherwise, the playlist is created. The created playlist is also saved in NocoDB to avoid any problems. Check if the monthly playlist contains all the song liked this month by getting them from NocoDB. If they are not present, add them one by one in the playlist. You may have a question regarding the need of NocoDB. Over the last few weeks/months, I've had duplication problems in my playlists and some playlists have been created twice because Spotify wasn't returning all the information but only partial information. Having the database means I don't have to rely on Spotify's data but on my own, which is accurate and represents reality. 📝 Prerequisites You need to have : Spotify API keys, which you can obtain by creating a Spotify application here: https://developer.spotify.com/dashboard. Create a NocoDB API token 📚 Instructions Follow the instructions below Create your Spotify API credential Create your NocoDB credential Populate all Spotify nodes with your credentials Populate all Spotify nodes with your credentials Enjoy ! If you need help, feel free to ping me on the N8N Discord server or send me a DM at "LucasAlt" Show your support Share your workflow on X and mention @LucasCtrlAlt Consider buying me a coffee 😉

Submission Overview for Voiceflow Demo Workflow View the YouTube video for this workflow here. Who is this for? This workflow is ideal for businesses and developers using Voiceflow to power AI voice chatbots. It benefits teams that want to enhance chatbot functionality through integrations with platforms like Zendesk, Google Calendar, and Airtable. What problem is this workflow solving? The workflow addresses the need for seamless integration of chatbot interactions with backend systems. It automates customer service tasks such as ticket creation, meeting scheduling, and data reporting, reducing manual effort and enhancing efficiency. What does this workflow do? Customer Lookup:** Checks the database for existing customers and returns relevant details or a "NOT_FOUND" status. Zendesk Ticket Creation:** Automates the creation of support tickets for customer issues. Meeting Scheduling:** Integrates with Google Calendar to provide availability and schedule meetings. Transcript Reporting:** Aggregates interaction data and sends it to Airtable for analysis by the product team. Setup Configure your Voiceflow chatbot to connect to this workflow via a webhook. Set up the required integrations: Zendesk API: For ticket creation. Google Calendar API: For scheduling. Airtable API: For storing transcripts. Customize the workflow's nodes to match your use case, such as database fields or API endpoints. Deploy the workflow on your n8n instance and test the integrations. How to customize this workflow to your needs Adjust database queries to match your customer data schema. Modify the Zendesk ticket payload to include additional fields or custom formats. Update Google Calendar configurations for different scheduling requirements. Add or remove Airtable fields based on the product team's analysis needs. This template adheres to n8n’s submission guidelines, ensuring clarity, relevance, and broad applicability for users in customer service, product development, and automation.

This n8n template shows how anyone can build a simple newsletter-like subscription service where users can enrol themselves to receive messages/content on a regular basis. It uses n8n forms for data capture, Airtable for database, AI for content generation and Gmail for email sending. How it works An n8n form is setup up to allow users to subscribe with a desired topic and interval of which to recieve messages via n8n forms which is then added to the Airtable. A scheduled trigger is executed every morning and searches for subscribers to send messages for based on their desired intervals. Once found, Subscribers are sent to a subworkflow which performs the text content generation via an AI agent and also uses a vision model to generate an image. Both are attached to an email which is sent to the subscriber. This email also includes an unsubscribe link. The unsubscribe flow works similarly via n8n form interface which when submitted disables further scheduled emails to the user. How to use Make a copy of sample Airtable here: https://airtable.com/appL3dptT6ZTSzY9v/shrLukHafy5bwDRfD Make sure the workflow is "activated" and the forms are available and reachable by your audience. Requirements Airtable for Database OpenAI for LLM (but compatible with others) Gmail for Email (but can be replaced with others) Customising this workflow This simple use can be extended to deliver any types of content such as your company newsletter, promotions, social media posts etc. Doesn't have to be limited to just email - try social messaging, Whatsapp, Telegram and others.