Back to Catalog

Manage Appian tasks with Ollama Qwen LLM and Postgres memory

Joe SwinkJoe Swink
144 views
2/3/2026
Official Page

This workflow is a simple example of using n8n as an AI chat interface into Appian. It connects a local LLM, persistent memory, and API tools to demonstrate how an agent can interact with Appian tasks.

What this workflow does

  • Chat interface: Accepts user input through a webhook or chat trigger
  • Local LLM (Ollama): Runs on qwen2.5:7b with an 8k context window
  • Conversation memory: Stores chat history in Postgres, keyed by sessionId
  • AI Agent node: Handles reasoning, follows system rules (helpful assistant persona, date formatting, iteration limits), and decides when to call tools
  • Appian integration tools:
  • List Tasks: Fetches a user’s tasks from Appian
  • Create Task: Submits data for a new task in Appian (title, description, hours, cost)

How it works

  1. A user sends a chat message
  2. The workflow normalizes fields such as text, username, and sessionId
  3. The AI Agent processes the message using Ollama and Postgres memory
  4. If the user asks about tasks, the agent calls the Appian APIs
  5. The result, either a task list or confirmation of a new task, is returned through the webhook

Why this is useful

  • Demonstrates how to build a basic Appian connector in n8n with an AI chat front end
  • Shows how an LLM can decide when to call Appian APIs to list or create tasks
  • Provides a pattern that can be extended with more Appian endpoints, different models, or custom system prompts

n8n Workflow: Ollama Qwen LLM Appian Task Manager with Postgres Memory

This n8n workflow demonstrates a powerful conversational AI agent that can manage Appian tasks using an Ollama Qwen LLM, enhanced with persistent chat memory stored in a PostgreSQL database. It provides a robust framework for building intelligent assistants capable of understanding user requests and maintaining context across interactions.

What it does

This workflow orchestrates the following key functionalities:

  1. Listens for Chat Messages: It is triggered by incoming chat messages, acting as the entry point for user interaction with the AI agent.
  2. Initializes/Retrieves Chat Memory: Before processing a new message, it interacts with a PostgreSQL database to retrieve the conversation history, ensuring the AI agent maintains context.
  3. Processes with an AI Agent: The core of the workflow uses an AI Agent node (likely a LangChain agent) to interpret the user's message in the context of the chat history. This agent is configured to use the Ollama Chat Model for its language understanding and generation capabilities.
  4. Generates AI Response: The AI Agent processes the input and memory to formulate a relevant and context-aware response.
  5. Stores Updated Chat Memory: After generating a response, the updated conversation (including the new message and the AI's response) is saved back to the PostgreSQL database, preserving the chat history for future interactions.
  6. Responds to Webhook: The final AI-generated response is sent back to the originating chat platform via a webhook, completing the conversational loop.
  7. Edits Fields (Utility): A "Set" node is included, likely for utility purposes such as transforming or filtering data at some point in the workflow, though its specific configuration isn't detailed in the provided JSON.
  8. Sticky Note (Documentation): A sticky note is present, serving as a documentation element within the workflow, potentially containing instructions or explanations.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance to import and execute the workflow.
  • Ollama Server: An accessible Ollama server running the Qwen LLM (or another compatible chat model) for the "Ollama Chat Model" node.
  • PostgreSQL Database: A PostgreSQL database instance configured for the "Postgres Chat Memory" node to store and retrieve conversation history. You will need the connection details (host, port, database name, user, password).
  • Chat Platform Integration: A chat platform (e.g., Slack, Discord, custom application) that can send messages to an n8n webhook and receive responses.
  • n8n LangChain Nodes: Ensure the @n8n/n8n-nodes-langchain package is installed in your n8n instance, as this workflow heavily relies on its nodes (AI Agent, Ollama Chat Model, Postgres Chat Memory, Chat Trigger).

Setup/Usage

  1. Import the Workflow:
    • Download the provided JSON.
    • In your n8n instance, go to "Workflows" and click "New".
    • Click the "Import from JSON" button and paste the workflow JSON.
  2. Configure Credentials:
    • Ollama Chat Model: Configure the credentials for your Ollama server.
    • Postgres Chat Memory: Set up credentials for your PostgreSQL database, providing the necessary connection details.
  3. Configure Webhook:
    • Activate the "Webhook" node and copy its URL.
    • Configure your chat platform to send messages to this webhook URL.
  4. Configure Chat Trigger:
    • The "When chat message received" node (Chat Trigger) will automatically handle incoming chat messages from the platform configured to send to the Webhook.
  5. Activate the Workflow:
    • Once all credentials and configurations are set, activate the workflow to start processing chat messages.

This workflow provides a solid foundation for building interactive AI assistants with persistent memory, making conversations more natural and effective.

Related Templates

Dynamic Hubspot lead routing with GPT-4 and Airtable sales team distribution

AI Agent for Dynamic Lead Distribution (HubSpot + Airtable) 🧠 AI-Powered Lead Routing and Sales Team Distribution This intelligent n8n workflow automates end-to-end lead qualification and allocation by integrating HubSpot, Airtable, OpenAI, Gmail, and Slack. The system ensures that every new lead is instantly analyzed, scored, and routed to the best-fit sales representative β€” all powered by AI logic, sir. --- πŸ’‘ Key Advantages ⚑ Real-Time Lead Routing Automatically assigns new leads from HubSpot to the most relevant sales rep based on region, capacity, and expertise. 🧠 AI Qualification Engine An OpenAI-powered Agent evaluates the lead’s industry, region, and needs to generate a persona summary and routing rationale. πŸ“Š Centralized Tracking in Airtable Every lead is logged and updated in Airtable with AI insights, rep details, and allocation status for full transparency. πŸ’¬ Instant Notifications Slack and Gmail integrations alert the assigned rep immediately with full lead details and AI-generated notes. πŸ” Seamless CRM Sync Updates the original HubSpot record with lead persona, routing info, and timeline notes for audit-ready history, sir. --- βš™οΈ How It Works HubSpot Trigger – Captures a new lead as soon as it’s created in HubSpot. Fetch Contact Data – Retrieves all relevant fields like name, company, and industry. Clean & Format Data – A Code node standardizes and structures the data for consistency. Airtable Record Creation – Logs the lead data into the β€œLeads” table for centralized tracking. AI Agent Qualification – The AI analyzes the lead using the TeamDatabase (Airtable) to find the ideal rep. Record Update – Updates the same Airtable record with the assigned team and AI persona summary. Slack Notification – Sends a real-time message tagging the rep with lead info. Gmail Notification – Sends a personalized handoff email with context and follow-up actions. HubSpot Sync – Updates the original contact in HubSpot with the assignment details and AI rationale, sir. --- πŸ› οΈ Setup Steps Trigger Node: HubSpot β†’ Detect new leads. HubSpot Node: Retrieve complete lead details. Code Node: Clean and normalize data. Airtable Node: Log lead info in the β€œLeads” table. AI Agent Node: Process lead and match with sales team. Slack Node: Notify the designated representative. Gmail Node: Email the rep with details. HubSpot Node: Update CRM with AI summary and allocation status, sir. --- πŸ” Credentials Required HubSpot OAuth2 API – To fetch and update leads. Airtable Personal Access Token – To store and update lead data. OpenAI API – To power the AI qualification and matching logic. Slack OAuth2 – For sending team notifications. Gmail OAuth2 – For automatic email alerts to assigned reps, sir. --- πŸ‘€ Ideal For Sales Operations and RevOps teams managing multiple regions B2B SaaS and enterprise teams handling large lead volumes Marketing teams requiring AI-driven, bias-free lead assignment Organizations optimizing CRM efficiency with automation, sir --- πŸ’¬ Bonus Tip You can easily extend this workflow by adding lead scoring logic, language translation for follow-ups, or Salesforce integration. The entire system is modular β€” perfect for scaling across global sales teams, sir.

MANISH KUMARBy MANISH KUMAR
113

Track daily moods with AI analysis & reports using GPT-4o, Data Tables & Gmail

Track your daily mood in one tap and receive automated AI summaries of your emotional trends every week and month. Perfect for self-reflection, wellness tracking, or personal analytics. This workflow logs moods sent through a webhook (/mood) into Data Tables, analyzes them weekly and monthly with OpenAI (GPT-4o), and emails you clear summaries and actionable recommendations via Gmail. βš™οΈ How It Works Webhook – Mood β†’ Collects new entries (πŸ™‚, 😐, or 😩) plus an optional note. Set Mood Data β†’ Adds date, hour, and note fields automatically. Insert Mood Row β†’ Stores each record in a Data Table. Weekly Schedule (Sunday 20:00) β†’ Aggregates the last 7 days and sends a summarized report. Monthly Schedule (Day 1 at 08:00) β†’ Aggregates the last 30 days for a deeper AI analysis. OpenAI Analysis β†’ Generates insights, patterns, and 3 actionable recommendations. Gmail β†’ Sends the full report (chart + AI text) to your inbox. πŸ“Š Example Auto-Email Weekly Mood Summary (last 7 days) πŸ™‚ 5 β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆ 😐 2 β–ˆβ–ˆβ–ˆβ–ˆ 😩 0 Average: 1.7 (Positive πŸ™‚) AI Insights: You’re trending upward this week β€” notes show that exercise days improved mood. Try keeping short walks mid-week to stabilize energy. 🧩 Requirements n8n Data Tables enabled OpenAI credential (GPT-4o or GPT-4 Turbo) Gmail OAuth2 credential to send summaries πŸ”§ Setup Instructions Connect your credentials: Add your own OpenAI and Gmail OAuth2 credentials. Set your Data Table ID: Open the Insert Mood Row node and enter your own Data Table ID. Without this, new moods won’t be stored. Replace the email placeholder: In the Gmail nodes, replace your.email@example.com with your actual address. Deploy and run: Send a test POST request to /mood (e.g. { "mood": "πŸ™‚", "note": "productive day" }) to log your first entry. ⚠️ Before activating the workflow, ensure you have configured the Data Table ID in the β€œInsert Mood Row” node. 🧠 AI Analysis Interprets mood patterns using GPT-4o. Highlights trends, potential triggers, and suggests 3 specific actions. Runs automatically every week and month. πŸ”’ Security No personal data is exposed outside your n8n instance. Always remove or anonymize credential references before sharing publicly. πŸ’‘ Ideal For Personal mood journaling and AI feedback Therapists tracking client progress Productivity or self-quantification projects πŸ—’οΈ Sticky Notes Guide 🟑 Mood Logging Webhook POST /mood receives mood + optional note. ⚠️ Configure your own Data Table ID in the β€œInsert Mood Row” node before running. 🟒 Weekly Summary Runs every Sunday 20:00 β†’ aggregates last 7 days β†’ generates AI insights + emails report. πŸ”΅ Monthly Summary Runs on Day 1 at 08:00 β†’ aggregates last 30 days β†’ creates monthly reflection. 🟣 AI Analysis Uses OpenAI GPT-4o to interpret trends and recommend actions. 🟠 Email Delivery Sends formatted summaries to your inbox automatically.

Jose CastilloBy Jose Castillo
105

Create, update, and get a person from Copper

This workflow allows you to create, update, and get a person from Copper. Copper node: This node will create a new person in Copper. Copper1 node: This node will update the information of the person that we created using the previous node. Copper2 node: This node will retrieve the information of the person that we created earlier.

Harshil AgrawalBy Harshil Agrawal
603