Block 1 - Postgres Chat Memory
- Type / Role
- @n8n/n8n-nodes-langchain.memoryPostgresChat - memoryPostgresChat
- Config choices
- Version 1.1
This workflow is provided as-is. Please review and test before using in production.
Edit 19/11/2024 : As explained on the workflow, the AI Agent with the original system prompt was not effective when using . To address this, I optimized the prompt to work better with this model. Y...
@n8n/n8n-nodes-langchain.memorypostgreschat, @n8n/n8n-nodes-langchain.lmchatopenai, n8n-nodes-base.set, n8n-nodes-base.stickynote, n8n-nodes-base.webhook, n8n-nodes-base.respondtowebhook, @n8n/n8n-nodes-langchain.toolworkflow, n8n-nodes-base.executeworkflowtrigger
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Dataki.
Original n8n.io sourceEdit 19/11/2024: As explained on the workflow, the AI Agent with the original system prompt was not effective when using gpt4-o-mini.
To address this, I optimized the prompt to work better with this model. You can find the prompts I’ve tested on this Notion Page. And yes, there is one that works well with gpt4-o-mini.
This AI Agent enables you to interact with your Search Console data through a chat interface. Each node is documented within the template, providing sufficient information for setup and usage. You will also need to configure Search Console OAuth credentials.
Follow this n8n documentation to set up the OAuth credentials.
Of course, you'll need to add your client_id and client_secret from the Google Cloud Platform app you created to access your Search Console data.
Since the webhook will be publicly accessible, don’t forget to set up authentication. I’ve used Basic Auth, but feel free to choose the method that best meets your security requirements.
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.
Showing the first 24 of 30 workflow blocks. Download the JSON for the full node graph.
| Workflow | AI agent to chat with you Search Console data, using OpenAI and Postgres |
|---|---|
| Complexity | advanced |
| Nodes | 30 |
| Categories | Internal Wiki, AI Chatbot |
| Author | Dataki |
| Published | 13 Nov 2024 |
Use the JSON export at /data/workflows/2541/2541.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
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.
Edit 19/11/2024 : As explained on the workflow, the AI Agent with the original system prompt was not effective when using . To address this, I optimized the prompt to work better with this model. Y...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
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 Internal Wiki, AI Chatbot use case.