Skip to main content

Travel planning assistant with MongoDB Atlas, Gemini LLM and vector search

Workflow preview

Workflow preview
100%
Travel planning assistant with MongoDB Atlas, Gemini LLM and vector search preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Building agentic AI workflows often requires multiple moving parts: memory management, document retrieval, vector similarity, and orchestration. Until now, these pieces had to be custom wired. But ...

Best for

  • Personal Productivity automation workflows
  • AI RAG automation workflows
  • intermediate n8n builders looking for reusable templates

Tools used

@n8n/n8n-nodes-langchain.chattrigger, @n8n/n8n-nodes-langchain.memorymongodbchat, @n8n/n8n-nodes-langchain.lmchatgooglegemini, @n8n/n8n-nodes-langchain.vectorstoremongodbatlas, @n8n/n8n-nodes-langchain.embeddingsopenai, n8n-nodes-base.stickynote, @n8n/n8n-nodes-langchain.agent, n8n-nodes-base.webhook

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Pavel Duchovny.

Original n8n.io source

1.1 Workflow description

Title
Travel planning assistant with MongoDB Atlas, Gemini LLM and vector search
Workflow name
Travel planning assistant with MongoDB Atlas, Gemini LLM and vector search

Building agentic AI workflows often requires multiple moving parts: memory management, document retrieval, vector similarity, and orchestration.

Until now, these pieces had to be custom-wired.

But with the new native n8n nodes for MongoDB Atlas, we reduce that overhead dramatically.

With just a few clicks:

  • Store and recall long-term memory from MongoDB

  • Query vector embeddings stored in Atlas Vector Search

  • Use these results in your LLM chains and automation logic

In this example we present an ingestion and AI Agent flows that focus around Travel Planning. The different interest points that we want the agent to know about can be ingested into the vector store.

The AI Agent will use the vector store tool to get relevant context about those points of interest if it needs to.

Prerequisites

How it works:

There are 2 main flows.

  1. One is ingesting flow:
  • Gets a document from a webhook and use MongoDB Vector Atlas to embed the document title and description into points_of_interest collection.
  • Embeddings are stored in a field named embedding
  • Embeddings used are OpenAI's but it can be any type of supported embedders.
  1. Second flow is an AI Agent node with Chat Memory Stored in MongoDB Atlas and a Vector Search node as a tool:
  • Chat Message Trigger: Chatting with the AI Agent will trigger the conversation store in the MongoDB Chat Memory node.
  • When data is necessary like a location search or details it will go to the "Vector Search" tool.
  • Vector Search Tool - uses Atlas Vector Search index created on the points_of_interest collection:
// index name : "vector_index"
// If you change an embedding provider make sure the numDimensions correspond to the model.
{
  "fields": [
    {
      "type": "vector",
      "path": "embedding",
      "numDimensions": 1536,
      "similarity": "cosine"
    }
  ]
}

Additional Resources

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - When chat message received

Type / Role
@n8n/n8n-nodes-langchain.chatTrigger - chatTrigger
Config choices
Version 1.1

Block 2 - MongoDB Chat Memory

Type / Role
@n8n/n8n-nodes-langchain.memoryMongoDbChat - memoryMongoDbChat
Config choices
Version 1

Block 3 - Google Gemini Chat Model

Type / Role
@n8n/n8n-nodes-langchain.lmChatGoogleGemini - lmChatGoogleGemini
Config choices
Version 1

Block 4 - MongoDB Atlas Vector Store

Type / Role
@n8n/n8n-nodes-langchain.vectorStoreMongoDBAtlas - vectorStoreMongoDBAtlas
Config choices
Version 1.1

Block 5 - Embeddings OpenAI

Type / Role
@n8n/n8n-nodes-langchain.embeddingsOpenAi - embeddingsOpenAi
Config choices
Version 1.2

Block 6 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 7 - AI Traveling Planner Agent

Type / Role
@n8n/n8n-nodes-langchain.agent - agent
Config choices
Version 1.8

Block 8 - Webhook

Type / Role
n8n-nodes-base.webhook - webhook
Config choices
Version 2

Block 9 - Default Data Loader

Type / Role
@n8n/n8n-nodes-langchain.documentDefaultDataLoader - documentDefaultDataLoader
Config choices
Version 1

Block 10 - Recursive Character Text Splitter

Type / Role
@n8n/n8n-nodes-langchain.textSplitterRecursiveCharacterTextSplitter - textSplitterRecursiveCharacterTextSplitter
Config choices
Version 1

Block 11 - MongoDB Atlas Vector Store1

Type / Role
@n8n/n8n-nodes-langchain.vectorStoreMongoDBAtlas - vectorStoreMongoDBAtlas
Config choices
Version 1.1

Block 12 - Embeddings OpenAI1

Type / Role
@n8n/n8n-nodes-langchain.embeddingsOpenAi - embeddingsOpenAi
Config choices
Version 1.2

Block 13 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 14 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

3. Summary Table

Workflow Travel planning assistant with MongoDB Atlas, Gemini LLM and vector search
Complexity intermediate
Nodes 14
Categories Personal Productivity, AI RAG
Author Pavel Duchovny
Published 16 Apr 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/3577/3577.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Travel planning assistant with MongoDB Atlas, Gemini LLM and vector search do?

Building agentic AI workflows often requires multiple moving parts: memory management, document retrieval, vector similarity, and orchestration. Until now, these pieces had to be custom wired. But ...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Personal Productivity, AI RAG use case.