HumationHuman + Automation
Back to Catalog

Business AI command center: Modular agents for Google Workspace, vector search & multi-channel reports

PaulPaul
317 views
2/3/2026
Task ManagementBirthdayGoogle ContactsAutomationClickUp
Official Page

🚀 AI OPS Agent for n8n — Stop Doing Busy Work. Start Leading.

Your AI workforce is ready. Are you?

💰 What You Get: Your ROI in 30 Days

Replace 10-15 hours/week of manual work with intelligent automation that actually understands your business. While your competitors copy-paste data between tools, you'll be making strategic decisions.

🧠 The Powerhouse Stack That Does Everything

| Module | Core Job | Your Competitive Edge | |------------|-------------|--------------------------| | MAIN AGENT (Grok 4) | Orchestrator & brain | • Reads your message → builds execution plan<br />• Delegates to specialized agents<br />• Delivers results through your preferred channel | | Knowledge Agent | Company-wide research assistant | • Vector-searches your Supabase docs instantly<br />• Runs live SQL queries for real-time numbers<br />• Hunts & parses Drive files automatically<br />• Pulls fresh web intelligence via Perplexity | | Google Sheets MCP Toolkit | Spreadsheet automation | Natural-language control over read/append/update/clear/create/delete operations on any tab or range | | Google Drive MCP Toolkit | File intelligence pipeline | • Auto-detects file types & extracts text from PDFs/CSVs<br />• Transcribes audio/video content<br />• Describes images with GPT-4o Mini | | Vector Store Loader | Long-term memory system | • Auto-chunks new files<br />• Creates OpenAI embeddings<br />• Stores in Supabase for instant semantic search | | Postgres Chat Memory | Conversation context | Never repeat yourself—every follow-up question builds on previous context | | Report Agent | Executive briefing machine | • Converts raw outputs → clean Markdown → HTML<br />• Auto-emails/Slacks/Telegrams polished reports | | LinkedIn Scraper | Talent & market intelligence | Scrapes full LinkedIn profiles via Apify, delivers structured JSON for analysis | | Multi-Channel Triggers | Meet users where they work | Slack • Gmail • Telegram • WhatsApp • HTTP Webhooks | | LLM Layer | Right model, right job | Grok 4 (reasoning) • Claude Sonnet 4 (analysis) • GPT-4o Mini (speed) • Perplexity (live web) |

⚡ How It Works (The Magic in 5 Steps)

  1. Message arrives (Slack mention, email, webhook)
  2. MAIN AGENT analyzes → selects optimal tool chain
  3. Specialized toolkits execute (Sheets, Drive, SQL, Scraper...)
  4. Knowledge Agent synthesizes everything using the perfect LLM
  5. Report Agent packages & delivers results to your chosen channel

🎯 Real Commands That Save Hours Daily

> "Update the Marketing-Spend sheet with last week's totals, then email me a chart." > > "Find the product-launch PDF from Drive, summarize key risks, post to Slack." > > "Scrape this LinkedIn URL, rank the candidate's skills, add them to our CRM sheet." > > "Create a new Sprint 11 tab, copy headers from Sprint 10, and ping the team."

One command. Multiple systems. Zero manual work.

Why Choose This Over Other Products:

✅ All Your Data, One Brain

No more jumping between 12 different tools. Your AI agent connects everything.

You can go further

If you want to increase the Agent capabilities or make the more powerfull you can reach the dev.

✅ Vector Search Built-In

Upload a 100-page document once. Search it forever with natural language.

✅ Executive-Ready Reports

Your C-suite gets clean HTML briefs, not raw data dumps that waste their time.

✅ Deploy in Minutes

Plug into your existing n8n setup, add credentials, watch routine ops handle themselves.

n8n Business AI Command Center: Modular Agents for Google Workspace, Vector Search & Multi-Channel Reports

This n8n workflow serves as a robust AI command center, designed to integrate with Google Workspace (Gmail, Google Drive) and various communication platforms (Slack, Telegram, WhatsApp). It leverages advanced AI capabilities, including language models, embeddings, vector stores, and specialized tools, to process information, generate insights, and deliver multi-channel reports or responses. The modular agent architecture allows for flexible and intelligent automation of business tasks.

What it does

This workflow is a comprehensive AI-powered system that can:

  1. Receive Inputs from Multiple Channels: Triggered by new messages/emails from Gmail, Telegram, WhatsApp, Slack, or manually. It can also be executed by another workflow (MCP Server Trigger) or manually.
  2. Process and Transform Data:
    • Edit Fields (Set): Allows for modification or creation of data fields within the workflow.
    • Extract from File: Can extract content from various file types, likely for processing with AI.
    • Default Data Loader: Loads documents, potentially for vectorization.
    • Recursive Character Text Splitter: Splits large text into smaller, manageable chunks for efficient processing by AI models.
  3. Leverage AI Agents and Language Models:
    • AI Agent: Acts as the core intelligent decision-maker, using various tools to fulfill requests.
    • OpenAI Chat Model / Anthropic Chat Model / OpenRouter Chat Model: Provides powerful large language model capabilities for understanding, generating, and summarizing text.
    • Embeddings OpenAI: Generates numerical representations (embeddings) of text for semantic search and similarity comparisons.
  4. Utilize Advanced AI Tools:
    • Supabase Vector Store: Stores and retrieves vectorized data, enabling efficient semantic search and retrieval-augmented generation (RAG).
    • Calculator: Performs mathematical operations, allowing the AI agent to handle quantitative tasks.
    • Call n8n Workflow Tool: Enables the AI agent to trigger and interact with other n8n workflows, extending its capabilities.
    • Think Tool: Provides a mechanism for the AI agent to reason and plan its actions.
    • MCP Client Tool: Interacts with other Model Context Protocol (MCP) servers, enabling distributed AI agent communication.
  5. Manage Conversational Memory:
    • Postgres Chat Memory: Stores chat history, allowing the AI agent to maintain context across conversations.
  6. Rerank Search Results:
    • Reranker Cohere: Improves the relevance of search results by re-ordering them based on semantic similarity.
  7. Deliver Multi-Channel Outputs:
    • Slack: Posts messages or reports to Slack channels.
    • Telegram: Sends messages or reports via Telegram.
    • WhatsApp Business Cloud: Sends messages or reports via WhatsApp.
    • Gmail: Sends emails.
    • Google Drive: Interacts with Google Drive, possibly for storing generated documents or retrieving files.
    • Markdown: Formats output as Markdown, suitable for various platforms.
  8. Conditional Logic: Uses a Switch node to route data based on specific conditions, enabling dynamic workflow paths.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • OpenAI Account & API Key: For OpenAI Chat Model and Embeddings OpenAI.
  • Anthropic Account & API Key: For Anthropic Chat Model (optional, if using Anthropic models).
  • OpenRouter Account & API Key: For OpenRouter Chat Model (optional, if using OpenRouter models).
  • Google Account Credentials: For Gmail Trigger, Gmail, and Google Drive nodes.
  • Telegram Bot Token: For Telegram Trigger and Telegram nodes.
  • Slack App & Bot Token: For Slack Trigger and Slack nodes.
  • WhatsApp Business Cloud Account & API Key: For WhatsApp Trigger and WhatsApp Business Cloud nodes.
  • Supabase Project: For Supabase Vector Store (database credentials and project URL).
  • PostgreSQL Database: For Postgres Chat Memory (database connection details).
  • Other n8n Workflows: If utilizing the "Call n8n Workflow Tool," you will need the target workflows configured and active.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Credentials:
    • For each node requiring credentials (e.g., OpenAI, Google, Telegram, Slack, WhatsApp, Supabase, PostgreSQL), set up the corresponding n8n credentials. Refer to the n8n documentation for each service's credential setup.
  3. Configure Trigger Nodes:
    • Telegram Trigger, Slack Trigger, WhatsApp Trigger, Gmail Trigger: Configure these nodes to listen for incoming messages/emails on your desired channels. This often involves setting up webhooks or polling intervals.
    • MCP Server Trigger: If this workflow is intended to be called by another AI agent, ensure the MCP server is correctly configured.
    • Manual Trigger / Execute Workflow Trigger: These are for manual testing or internal workflow calls.
  4. Customize AI Agent and Tools:
    • AI Agent: Define the agent's instructions, models to use (OpenAI, Anthropic, OpenRouter), and which tools it should have access to (Calculator, Call n8n Workflow Tool, Think Tool, MCP Client Tool, Supabase Vector Store).
    • Language Models: Select your preferred chat model (OpenAI, Anthropic, OpenRouter) and configure its parameters (e.g., model name, temperature).
    • Embeddings OpenAI: Configure the embedding model.
    • Supabase Vector Store: Connect to your Supabase instance and specify the table for vector storage.
    • Postgres Chat Memory: Connect to your PostgreSQL database and specify the table for chat history.
  5. Define Logic with Switch Node: Customize the conditions in the "Switch" node to route different types of inputs or AI agent outputs to specific reporting or action channels.
  6. Configure Output Nodes:
    • Slack, Telegram, WhatsApp Business Cloud, Gmail: Configure these nodes to send messages, emails, or reports with the content generated by the AI agent or other workflow steps.
    • Google Drive: Configure for file operations if needed.
    • Markdown: Use this node to format the final output before sending it to communication channels.
  7. Activate the Workflow: Once configured, activate the workflow to start processing incoming data and automating tasks.

This workflow provides a powerful foundation for building sophisticated AI-driven business automation. Adjust the node configurations and logic to fit your specific use cases and integrate seamlessly with your Google Workspace and communication platforms.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://&lt;your-instance&gt;.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942