4 templates found
Category:
Author:
Sort:

🧑‍🎓 Test your data access techniques with progressive expression challenges

How it works This template is a hands-on, practical exam designed to help you master n8n Expressions—the key to accessing and manipulating data in your workflows. If the 🎓 Expressions Tutorial Template was the theory lesson, this is the practical driving test. You'll learn how to navigate through complex data structures to get the exact piece of information you need. All challenges will reference a single "Source Data" node, which acts as our data "map". The test is a series of six sequential challenges that build in complexity: Basic Access: Getting a simple value from an object. Array Access: Targeting a specific item in a list. Nested Object Access: Reaching data inside another object. Array of Objects: Combining array and object skills to get a specific value from a list of objects. Using JavaScript: Applying simple JavaScript functions (like .toUpperCase()) to your data. Combining Text & Expressions: Creating dynamic strings that mix static text with data from previous nodes. For each challenge, you'll write an expression in a "Test" node. When you execute the workflow, an IF node will instantly validate your answer, giving you a green path for success or a red path with a hint if you need to try again. Set up steps Setup time: < 1 minute This workflow is a self-contained test and requires no setup or credentials. Read the instructions on the main sticky note to understand the goal. Start with the first challenge, "Test - Basic Access". Modify the node by writing the correct expression in the value field, according to the instructions on the purple sticky note. Click "Execute Workflow". If the execution path is green, you've passed! The next "Test" node in the sequence will automatically be enabled for you to continue. If the path is red, read the hint in the error message and try again. Repeat the process until you reach the final success message and become an expressions pro. Good Luck!

Lucas PeyrinBy Lucas Peyrin
1991

Export Amazon product reviews in bulk to Google Sheets via RapidAPI

What it does Pulls up to 700 Amazon reviews per product (recent and top-rated) and writes them straight into a Google Sheet tab you choose. Perfect for • Brand and product managers tracking sentiment • Marketplace sellers analysing competitor feedback • Agencies building product-review dashboards Apps used RapidAPI Real-Time Amazon Data, Google Sheets, n8n Form Trigger How it works Form Trigger collects brand, product and sheet info. Code node extracts the ASIN and builds 70 API requests (10 pages × star ratings). Split-in-batches loops through the request list, throttled by two Wait nodes. HTTP Request fetches reviews from RapidAPI. IF node drops empty or error responses. Split Out breaks arrays into single reviews. Google Sheets appends every review to the target tab. Loop continues until all pages finish. Setup Fill in Brand name, Product / Model Name, Amazon Product URL, Tab URL to insert reviews in the form. Grab your X-RapidAPI-Key from RapidAPI → Add as httpHeaderAuth credential. Connect Google Sheets OAuth2 and make the spreadsheet Anyone with the link can edit. Open Workflow Settings → set timezone if you plan to schedule runs. Hit Execute workflow or share the form link. Credentials • Real-Time Amazon Data (RapidAPI HTTP Header Auth) • Google Sheets OAuth2 Limits and notes • \~100 RapidAPI calls for the free plan. Plan quota accordingly. • Assumes Amazon returns 10 pages per star rating; fewer pages skip silently. • Large sheets may hit Google API write quotas. If you have any questions in running the workflow, feel free to reach out to me at my youtube channel: https://www.youtube.com/@hunyaochong

HunyaoBy Hunyao
1889

Search Outlook emails with natural language queries using GPT-4o

This workflow allows you to search your Outlook mailbox with natural language. You type what you’re looking for (e.g., “invoice from last week”), and the workflow: Uses OpenAI to generate a search query. Searches Outlook emails and ranks them by relevance. Outputs results in a simple table with score + link to each email. 👉 The number of results can be changed (default: 5). --- ⚙️ Setup Instructions 1️⃣ Set Up OpenAI Connection Go to OpenAI Platform Navigate to OpenAI Billing Add funds to your billing account Copy your API key into the OpenAI credentials in n8n 2️⃣ Set Up Outlook Connection In n8n → Credentials → New → Microsoft Outlook OAuth2 API Log in with your Outlook account & approve access Attach this credential to the Search Outlook node in the workflow (Optional) Change the limit parameter in the node if you want more/less than 5 results --- 📬 Contact Information Need help customizing this workflow or building similar automations? 📧 robert@ynteractive.com 🔗 Robert Breen 🌐 ynteractive.com

Robert BreenBy Robert Breen
835

Automated customer support system with Gemini AI, RAG & security guardrails

Description This workflow acts as an autonomous Tier 2 Customer Support Agent. It doesn't just answer questions; it manages the entire lifecycle of a support ticket—from triage to resolution with Guardrails to deal with prompt injections, PII information blocking, etc. enabling such threats are blocked and logged in Airtable. Unlike standard auto-responders, this system uses a "Master Orchestrator" architecture to coordinate specialized sub-agents. It creates a safe, human-like support experience by combining RAG (Knowledge Base retrieval) with a safety-first state machine. How it works The workflow operates on a strict "Hub and Spoke" model managed by a Master Orchestrator: Security Guardrails (The Gatekeeper) Before the AI even sees the message, a hard-coded security layer scans for Prompt Injection attacks, Profanity, and PII. If a threat is detected, the workflow locks down, logs the incident to Airtable, and stops execution immediately. Orchestration & Triage Once the message passes safety checks, the Master Orchestrator takes over. Its first action is to call the Ticket Analyser Agent. Analysis & Scoring The Ticket Analyser classifies the issue (e.g., "Technical," "Billing") and scores the customer's sentiment. It returns a priority_score to the Master Orchestrator. The Decision Logic (Circuit Breaker) The Master Orchestrator evaluates the score: Escalation: If the customer is "Furious" or the score is high, it bypasses AI drafting and immediately alerts a human manager via Slack. Resolution Path: If the request is standard, it proceeds to the next steps. Knowledge Retrieval (RAG) The Orchestrator calls the Knowledge Worker Agent. This agent searches your Supabase vector store to find specific, verified company policies or troubleshooting steps relevant to the user's issue. Resolution Drafting Armed with the analysis and the retrieved facts, the Orchestrator calls the Resolution Agent. This agent synthesizes a polite, professional email draft. Final Execution The Master Orchestrator reviews the final draft and sends the email via Gmail. Set up This is multi-agent system. Please follow these steps to configure the environment: ⚠️ IMPORTANT: This template contains the Main Orchestrator AND the Sub-Agents in a single view. You must separate them for the system to function: Separate the Agents: Copy the nodes for each sub-agent (Ticket Analyser, Knowledge Worker, Resolution Agent) into their own new workflows. Link the Tools: In the Main Orchestrator workflow, open the "Call [Agent Name]" tool nodes and update the Workflow ID to point to the new workflows you just created. Configure Credentials: You will need credentials for Gmail (or your preferred email provider), Slack, Airtable, Supabase (for the vector store), and Google Gemini (or OpenAI). Initialize the Knowledge Base: Open the "One time Document Loader" section in the workflow. Upload your policy document (PDF/Text) to the "Upload your file here" node. Run this branch once to vectorize your documents into Supabase. Setup Airtable: Create a simple table with columns for Sender Email, Incident Type, and Flagged Content to log security threats caught by the guardrails. Customize the Trigger: Update the Gmail Trigger node to watch for your specific support alias (e.g., support@yourdomain.com) and ensure it only picks up "Unread" emails. Adjust the Escalation Sensitivity: In the Orchestrator Agent node, you can tweak the "Phase 2" logic to change what triggers a human hand-off (currently set to priority_score >= 0.9). Good to go!

RamSBy RamS
237
All templates loaded