Back to Catalog

Automate HighLevel CRM with GPT-5, knowledge retrieval & document context

PaulPaul
286 views
2/3/2026
Official Page

Supercharge Your HighLevel CRM with the Power of GPT-5

Unleash the full potential of your HighLevel CRM by adding an intelligent GPT-5 Agent that does more than just follow commands — it understands context, retrieves the right data, and executes actions instantly.

This marketplace solution transforms how you work:

  • Act Instantly – Create, update, and manage contacts, opportunities, tasks, and calendars with natural language commands.
  • Work Smarter, Not Harder – The agent pulls context from your internal documents, spreadsheets, and even the web before acting, ensuring every move is informed and precise.
  • Never Miss a Detail – It searches your knowledge base, Google Drive, and Supabase vectors to fill in missing info so you don’t have to.
  • Boost Team Productivity – Automate repetitive CRM work, cut manual data entry, and free up hours every week.
  • Close Deals Faster – Instantly update opportunities, schedule meetings, and follow up on leads without switching tabs.
  • Stay Organized Effortlessly – One AI agent orchestrates it all — from booking appointments to updating deal stages — directly inside HighLevel.

Why This Is a Game-Changer

Other tools require constant babysitting. This agent thinks ahead, checks context, and ensures every action in your CRM is accurate, complete, and ready to move your business forward.

Stop clicking through endless menus. Let GPT-5 + HighLevel automation work for you.


Boost conversions
Automate admin work
Keep your CRM data flawless

Get it now and watch your CRM become your smartest sales assistant.

n8n AI-Powered Communication and Document Context Workflow

This n8n workflow demonstrates a versatile AI agent that can interact with users across multiple communication platforms (Telegram, WhatsApp, Slack, Gmail) and leverage document context from Google Drive to provide informed responses. It acts as a central hub for intelligent communication and knowledge retrieval.

Description

This workflow simplifies and automates intelligent interactions by routing incoming messages from various channels to an AI agent. The AI agent, powered by OpenAI, can retrieve relevant information from documents stored in Google Drive and respond appropriately. It also includes a mechanism for human-in-the-loop (HITL) scenarios where the AI might call another n8n workflow as a tool.

What it does

  1. Listens for Incoming Messages: The workflow can be triggered by new messages received on:
    • Telegram
    • WhatsApp Business Cloud
    • Slack
    • Gmail
    • A generic Chat Trigger (likely for internal or custom chat interfaces)
    • An MCP Server Trigger (Model Context Protocol, for advanced AI integration)
  2. Processes Messages with an AI Agent: All incoming messages are fed into an "AI Agent" node (LangChain Agent).
  3. Utilizes Document Context: The AI agent is configured to use a "Supabase Vector Store" for knowledge retrieval, which is populated by "Embeddings OpenAI" based on documents from "Google Drive". This allows the AI to answer questions or provide information based on your stored documents.
  4. Leverages OpenAI Chat Model: The core of the AI's conversational ability is an "OpenAI Chat Model".
  5. Optionally Calls Other Workflows as Tools: The AI agent can use a "Call n8n Workflow Tool" to trigger other n8n workflows, enabling complex multi-step automations based on user requests.
  6. Reranks Search Results (Cohere): A "Reranker Cohere" node is included, suggesting that search results from the vector store are optimized for relevance before being presented to the AI agent.
  7. Sends Responses: The AI's generated responses can be sent back to the originating platform via:
    • Slack
    • Telegram
    • WhatsApp Business Cloud
    • Gmail
    • An MCP Client Tool (for advanced AI integration)
  8. Data Transformation: An "Edit Fields (Set)" node is present, likely for manipulating data before or after AI processing.
  9. File Extraction: An "Extract from File" node suggests the ability to process and extract content from various file types, potentially for populating the vector store or for direct use by the AI.
  10. Conditional Logic: A "Switch" node allows for routing the workflow based on certain conditions, enabling different actions depending on the message content or source.
  11. Chat Memory: A "Postgres Chat Memory" node is included, indicating that the AI agent maintains conversational context across interactions.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance.
  • OpenAI API Key: For the "OpenAI Chat Model" and "Embeddings OpenAI" nodes.
  • Supabase Account: For the "Supabase Vector Store" (requires a Supabase project and database).
  • Google Drive Account: For the "Google Drive" node to access documents.
  • Telegram Bot Token: For "Telegram Trigger" and "Telegram" nodes.
  • WhatsApp Business Cloud Account: For "WhatsApp Trigger" and "WhatsApp Business Cloud" nodes.
  • Slack Workspace/App: For "Slack Trigger" and "Slack" nodes.
  • Gmail Account: For "Gmail Trigger" and "Gmail" nodes.
  • Cohere API Key (Optional): If using the "Reranker Cohere" node.
  • PostgreSQL Database (Optional): If using the "Postgres Chat Memory" node to store chat history.

Setup/Usage

  1. Import the Workflow: Download the JSON provided and import it into your n8n instance.
  2. Configure Credentials:
    • Set up credentials for OpenAI.
    • Set up credentials for Supabase.
    • Set up credentials for Google Drive.
    • Set up credentials for Telegram, WhatsApp Business Cloud, Slack, and Gmail as needed for the communication channels you intend to use.
    • (Optional) Configure Cohere credentials if using the reranker.
    • (Optional) Configure PostgreSQL credentials if using chat memory.
  3. Configure Nodes:
    • Trigger Nodes: Configure the "Telegram Trigger", "WhatsApp Trigger", "Slack Trigger", "Gmail Trigger", "Chat Trigger", and "MCP Server Trigger" nodes to listen for events from your desired platforms.
    • Google Drive: Specify the files or folders the AI should use as context.
    • Embeddings OpenAI: Ensure this node is correctly configured to create embeddings from your Google Drive documents.
    • Supabase Vector Store: Connect this to your Supabase project and specify the table for vector storage.
    • OpenAI Chat Model: Select your preferred OpenAI model and any other parameters.
    • AI Agent: Configure the agent to use the OpenAI Chat Model, Supabase Vector Store, and any other tools (like "Call n8n Workflow Tool").
    • Communication Nodes: Configure the "Slack", "Telegram", "WhatsApp Business Cloud", and "Gmail" nodes to send messages to the correct channels/recipients.
    • Call n8n Workflow Tool: If used, specify the n8n workflow ID to be called.
    • Edit Fields (Set) and Switch: Adjust these nodes based on your specific data transformation and routing logic.
  4. Activate the Workflow: Once configured, activate the workflow to start processing messages and providing AI-powered responses.

This workflow provides a robust foundation for building intelligent, context-aware communication systems.

Related Templates

Automate Dutch Public Procurement Data Collection with TenderNed

TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte

Wessel BulteBy Wessel Bulte
247

🎓 How to transform unstructured email data into structured format with AI agent

This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From – sender’s email address To – recipient’s email address Subject – email subject line Summary – short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits ✅ Full Automation: Eliminates manual reading and data entry from incoming emails. ✅ Multi-Source Integration: Handles data from different email providers seamlessly. ✅ AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. ✅ Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. ✅ Time Efficiency: Processes emails in real time, improving productivity and response speed. *✅ Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.

DavideBy Davide
1616

Tax deadline management & compliance alerts with GPT-4, Google Sheets & Slack

AI-Driven Tax Compliance & Deadline Management System Description Automate tax deadline monitoring with AI-powered insights. This workflow checks your tax calendar daily at 8 AM, uses GPT-4 to analyze upcoming deadlines across multiple jurisdictions, detects overdue and critical items, and sends intelligent alerts via email and Slack only when immediate action is required. Perfect for finance teams and accounting firms who need proactive compliance management without manual tracking. 🏛️🤖📊 Good to Know AI-Powered: GPT-4 provides risk assessment and strategic recommendations Multi-Jurisdiction: Handles Federal, State, and Local tax requirements automatically Smart Alerts: Only notifies executives when deadlines are overdue or critical (≤3 days) Priority Classification: Categorizes deadlines as Overdue, Critical, High, or Medium priority Dual Notifications: Critical alerts to leadership + daily summaries to team channel Complete Audit Trail: Logs all checks and deadlines to Google Sheets for compliance records How It Works Daily Trigger - Runs at 8:00 AM every morning Fetch Data - Pulls tax calendar and company configuration from Google Sheets Analyze Deadlines - Calculates days remaining, filters by jurisdiction/entity type, categorizes by priority AI Analysis - GPT-4 provides strategic insights and risk assessment on upcoming deadlines Smart Routing - Only sends alerts if overdue or critical deadlines exist Critical Alerts - HTML email to executives + Slack alert for urgent items Team Updates - Slack summary to finance channel with all upcoming deadlines Logging - Records compliance check results to Google Sheets for audit trail Requirements Google Sheets Structure Sheet 1: TaxCalendar DeadlineID | DeadlineName | DeadlineDate | Jurisdiction | Category | AssignedTo | IsActive FED-Q1 | Form 1120 Q1 | 2025-04-15 | Federal | Income | John Doe | TRUE Sheet 2: CompanyConfig (single row) Jurisdictions | EntityType | FiscalYearEnd Federal, California | Corporation | 12-31 Sheet 3: ComplianceLog (auto-populated) Date | AlertLevel | TotalUpcoming | CriticalCount | OverdueCount 2025-01-15 | HIGH | 12 | 3 | 1 Credentials Needed Google Sheets - Service Account OAuth2 OpenAI - API Key (GPT-4 access required) SMTP - Email account for sending alerts Slack - Bot Token with chat:write permission Setup Steps Import workflow JSON into n8n Add all 4 credentials Replace these placeholders: YOURTAXCALENDAR_ID - Tax calendar sheet ID YOURCONFIGID - Company config sheet ID YOURLOGID - Compliance log sheet ID C12345678 - Slack channel ID tax@company.com - Sender email cfo@company.com - Recipient email Share all sheets with Google service account email Invite Slack bot to channels Test workflow manually Activate the trigger Customizing This Workflow Change Alert Thresholds: Edit "Analyze Deadlines" node: Critical: Change <= 3 to <= 5 for 5-day warning High: Change <= 7 to <= 14 for 2-week notice Medium: Change <= 30 to <= 60 for 2-month lookout Adjust Schedule: Edit "Daily Tax Check" trigger: Change hour/minute for different run time Add multiple trigger times for tax season (8 AM, 2 PM, 6 PM) Add More Recipients: Edit "Send Email" node: To: cfo@company.com, director@company.com CC: accounting@company.com BCC: archive@company.com Customize Email Design: Edit "Format Email" node to change colors, add logo, or modify layout Add SMS Alerts: Insert Twilio node after "Is Critical" for emergency notifications Integrate Task Management: Add HTTP Request node to create tasks in Asana/Jira for critical deadlines Troubleshooting | Issue | Solution | |-------|----------| | No deadlines found | Check date format (YYYY-MM-DD) and IsActive = TRUE | | AI analysis failed | Verify OpenAI API key and account credits | | Email not sending | Test SMTP credentials and check if critical condition met | | Slack not posting | Invite bot to channel and verify channel ID format | | Permission denied | Share Google Sheets with service account email | 📞 Professional Services Need help with implementation or customization? Our team offers: 🎯 Custom workflow development 🏢 Enterprise deployment support 🎓 Team training sessions 🔧 Ongoing maintenance 📊 Custom reporting & dashboards 🔗 Additional API integrations Discover more workflows – Get in touch with us

Oneclick AI SquadBy Oneclick AI Squad
93