Advanced AI demo (presented at AI Developers #14 meetup)
This workflow was presented at the AI Developers meet up in San Fransico on 24 July, 2024. AI workflows Categorize incoming Gmail emails and assign custom Gmail labels. This example uses the Text Classifier node, simplifying this usecase. Ingest a PDF into a Pinecone vector store and chat with it (RAG example) AI Agent example showcasing the HTTP Request tool. We teach the agent how to check availability on a Google Calendar and book an appointment.
By Max TkaczQualify & reach out to B2B leads with Groq AI, Apollo, Gmail & Sheets
This workflow contains community nodes that are only compatible with the self-hosted version of n8n. 🎯 How it works This workflow captures new lead information from a web form, enriches it with Apollo.io data, qualifies the lead using AI, and—if the lead is strong—automatically sends a personalized outreach email via Gmail and logs the result in Google Sheets. 🛠️ Key Features 📩 Lead form capture with validation 🔍 Enrichment via Apollo API 🤖 Lead scoring using AI (LangChain + Groq) 📧 Dynamic email generation & sending via Gmail 📊 Logging leads with job title & org into Google Sheets ✅ Conditional email sending (score ≥ 6 only) 🧪 Set up steps Estimated time: 15–20 minutes Add your Apollo API Key to the HTTP Header credential (never hardcode!) Connect your Gmail account for sending emails Connect your Google Sheets account and set up the correct spreadsheet & sheet name Enable LangChain/Groq credentials for lead scoring and AI-generated emails Update the form endpoint to your live webhook if needed 📌 Sticky Notes Add the following mandatory sticky notes inside your workflow: FormTrigger Node: "Collects lead info via form. Ensure your form is connected to this endpoint." HTTP Request Node: "Enrich lead using Apollo.io API. Add your API key via header-based authentication." AI Agent (Lead Score): "Scores lead from 1-10 based on job title and industry match. Only leads with score ≥ 6 proceed." AI Agent (Email Composer): "Generates a concise, polite email using lead’s job title & company. Modify tone if needed." Google Sheets Append: "Logs enriched lead with job title, org, and LinkedIn URL. Customize sheet structure if needed." Gmail Node: "Sends personalized outreach email if lead passes score threshold. Uses AI-generated content." 💸 Free or Paid? Free – No paid API services are required (Apollo has a free tier).
By VKAPS ITNewsletter summarization & briefing with Gmail, AI, Google Sheets & Email
Your inbox is overflowing with daily newsletters: Public Affairs, ESG, Legal, Finance, you name it. You want to stay informed, but reading 10 emails every morning? Impossible. What if you could get one single digest summarizing everything that matters, automatically? ❌ No more copy-pasting text into ChatGPT ❌ No more scrolling through endless email threads ✅ Just one smart, structured daily briefing in your inbox Who Is This For Public Affairs Teams: Stay ahead of political and regulatory updates—without drowning in emails. Executives & Analysts: Get daily summaries of key insights from multiple newsletters. Marketing, Legal, or ESG Departments: Repurpose this workflow for your own content sources. How It Works Gmail collects all newsletters from the day (based on sender or label). HTML noise and formatting are stripped automatically. Long texts are split into chunks and logged in Google Sheets. An AI Agent (Gemini or OpenAI) summarizes all content into one clean daily digest. The workflow structures the summary into an HTML email and sends it to your chosen recipients. Setup Guide • You’ll need Gmail and Google Sheets credentials. • Add your own AI Model (e.g., Gemini or OpenAI) with an API key. • Adjust the prompt inside the “Public Affairs Consultant” node to fit your topic (e.g., Legal, Finance, ESG, Marketing). • Customize the email subject and design inside the “Structure HTML-Mail” node. • Optional: Use Memory3 to let the AI learn your preferred tone and style over time. Cost & Runtime Runs once per day. Typical cost: ~$0.10–0.30 per run (depending on model and input length). Average runtime: <2 minutes.
By Jan ZaiserFetch scriptures dynamically from get Bible API
Overview The Get Bible Query Workflow is a modular and self-standing workflow designed to retrieve scriptures dynamically based on structured input. It serves as an intermediary layer that extracts references, queries the GetBible API, and returns scriptures in a standardized JSON format. This workflow is fully prepared for integration—simply call it from another workflow with the required JSON input, and it will return the requested scripture data. --- Who Is This For? This workflow is ideal for developers, Bible study apps, research tools, and dynamic scripture-based projects that need seamless access to scriptural content without direct API interaction. ✅ Use Cases: Bible Study Apps → Embed scripture retrieval functionality. Research & Theology Tools → Fetch structured verse data. Dynamic Content Generation → Integrate real-time scripture references. Sermon Preparation → Automate scripture lookups. --- How It Works Trigger Workflow → This workflow is designed to be called from another workflow with a structured JSON input. Receive Input → Accepts a JSON object containing references, translation, and API version. Extract References → Parses single verses, comma-separated lists, and ranged passages. Query API → Sends structured requests to the GetBible API. Format Response → Returns structured JSON output, maintaining API response consistency. --- JSON Input Structure References → Should include the book name, chapter, and verse(s). Multiple Verses → Separated by commas (e.g., John 3:16,18). Verse Ranges → Defined with a dash (e.g., John 3:16-18). Translation → Choose from the supported translations. API Version → Currently supports v2. Example JSON Input json { "references": [ "1 John 3:16", "Jn 3:16", "James 3:16", "Rom 3:16" ], "translation": "kjv", "version": "v2" } --- Example API Response json { "result": { "kjv623": { "translation": "King James Version", "abbreviation": "kjv", "book_name": "1 John", "chapter": 3, "ref": ["1 John 3:16"], "verses": [ { "chapter": 3, "verse": 16, "name": "1 John 3:16", "text": "Hereby perceive we the love of God, because he laid down his life for us: and we ought to lay down our lives for the brethren." } ] } } } 💡 Fully structured and formatted response – ready for seamless integration. --- Integration and Usage The GetBible Query Workflow is designed for immediate use. Simply call it from another workflow and pass the appropriate JSON object as input, and it will return the requested scripture passages. ✔️ No additional configuration is required. ✔️ Designed for fast, reliable, and structured scripture retrieval. ✔️ Fully compatible with GetBible API responses. --- Why Use This Workflow? ✔️ Fast & Reliable → Direct API integration for efficient queries. ✔️ Flexible Queries → Supports single, multi-verse, and ranged requests. ✔️ Agent-Compatible → Easily integrates into automated workflows. ✔️ No Code Needed → Just configure the JSON input and run the workflow. --- Next Steps 🔗 API Support 📖 API Documentation 💬 Need help? Join the community for support! 🚀
By getBibleLINE BOT - Google Sheets file lookup with AI agent
This workflow integrates LINE BOT, AI Agent (GPT), Google Sheets, and Google Drive to enable users to search for file URLs using natural language. The AI Agent extracts the filename from the message, searches for the file in Google Sheets, and returns the corresponding Google Drive URL via LINE BOT. Supports natural language queries (e.g., "Find file 1.pdf for me") AI-powered filename extraction Google Sheets Lookup for file URLs Auto-response via LINE BOT How to Use This Template Download & Import Copy and save the Template Code as a .json file. Go to n8n Editor → Click Import → Upload the file. Update Required Fields Replace YOURGOOGLESHEET_ID with your actual Google Sheet ID. Replace YOURLINEACCESS_TOKEN with your LINE BOT Channel Access Token. Activate & Test Click Execute Workflow to test manually. Set Webhook URL in LINE Developer Console. Features of This Template Supports Natural Language Queries (e.g., “Find file 1.pdf for me”) AI-powered filename extraction using OpenAI (GPT-4/3.5) Real-time file lookup in Google Sheets Automatic LINE BOT Response Fully Automated Workflow
By Jaruphat J.Research-to-social post generator with Perplexity AI and Facebook Graph API
Who’s it for Teams that want to turn a chat prompt into a researched, ready-to-post social update—optionally published to Facebook. What it does / How it works Chat Trigger receives the user prompt Topic Agent optionally calls a research sub-workflow for fresh sources Outputs are validated into a structured JSON Post Writing Agent crafts a concise Vietnamese post (Optional) Facebook Graph API publishes to your Page How to set up Connect OpenAI & Facebook in Credentials (no API key inside nodes). In Tool: Call Perplexity Researcher, set your research workflowId. In Publish: Facebook Graph API, set your Page ID and edge. Adjust prompts/tone and the LANGUAGE in CONFIG. Test the flow with sample prompts in the chat. Requirements n8n (Cloud or self-hosted) OpenAI API key (stored in Credentials) Facebook Page publish permissions (Optional) a research workflow for Perplexity How to customize the workflow Add moderation/review gates before publishing. Duplicate the publish path for other platforms. Store outputs in Sheets/Notion/DB for auditing. Tune model choice & temperature for your brand voice. Security Avoid hardcoding secrets in HTTP or Code nodes. Keep identifiers (Page IDs, workflowIds) configurable in CONFIG.
By HoangSP