Customer Chat Authentication and Session Management using Redis - n8n Workflow

Ideal Users

This n8n workflow provides a sophisticated solution for handling stateful customer interactions within an AI chat support framework. Unlike typical setups where authentication is mandatory upfront, this design allows anonymous guests to initiate conversations and then dynamically authenticate if they require access to private customer data (like account history or shopping baskets).

The core value lies in its use of an n8n agent, powered by an OpenAI Large Language Model (LLM), combined with Redis for reliable session memory. When a guest requests sensitive information, the n8n node configured as a tool is invoked. This tool generates a unique login URL linking back to a dedicated n8n form. After successful login, the user’s session is immediately updated in Redis with their customer profile, transforming the user from a 'guest' to a 'customer' for all subsequent interactions. This makes this n8n workflow highly scalable and context-aware.

This n8n workflow operates across two main logical paths: the primary chat flow and the external authentication flow.

Primary Chat Flow (Handling Messages)

1. Incoming Message: The When chat message received LangChain Chat n8n trigger starts the process when a user sends a message.


2. Session Check: The Get Session Redis n8n node retrieves the current session data associated with the user's sessionId. This context determines if the user is a 'guest' (no data) or a 'customer' (profile data exists).


3. Agent Processing: The Customer Support Agent (LangChain Agent n8n node) uses the retrieved session data in its system prompt, customizing its behavior. It leverages the LLM (OpenAI) and Memory nodes to maintain conversation history.


4. Tool Invocation: If the guest asks for protected data, the agent invokes the Get Auth URL Tool. This tool, an n8n node configured to execute a sub-workflow, triggers the secondary path to generate the login link.

Secondary Authentication Flow (Generating URL & Login)

1. Sub-Workflow Trigger: The When Executed by Another Workflow n8n trigger receives the request from the agent tool.


2. URL Generation: The Switch node routes the execution, and Get Auth Url Response constructs the secure login URL, appending the necessary sessionId as a query parameter.


3. Form Trigger: The user navigates to the URL, triggering the Login Form n8n trigger, which is an external authentication portal.


4. Authentication Logic: The Replace Me! placeholder n8n node is where you insert your actual external authentication logic (e.g., verifying credentials against a database).


5. Profile Creation: Get Customer Profile simulates retrieving customer data.


6. Session Update: The Update Session Redis n8n node writes the complete customer profile data back to Redis, associated with the original sessionId. This completes the authentication. The next time the user sends a message, the Get Session n8n node will retrieve this profile, and the agent will recognize them as an authenticated customer.

To deploy this powerful n8n workflow template, follow these steps:

1. Import: Copy the provided n8n workflow JSON and paste it into your n8n instance.


2. Credentials Setup:

1. Update URL Tool: In the Get Auth Url Response n8n node, update the auth_url value (e.g., https:///form/auth...) to reflect your n8n instance's URL and domain.


2. Implement Logic: Replace the Replace Me! n8n node with your actual user authentication logic (e.g., a Database n8n node query).


3. Activate: Save and activate the n8n workflow. Ensure production mode is enabled for the form and chat triggers to function correctly.

This n8n workflow relies on several specialized n8n node types to achieve complex state management and AI integration.

When chat message received (LangChain Chat Trigger): The starting n8n trigger for the conversational thread, providing the sessionId and chatInput.
Get Session (Redis n8n node): Essential for state management. It uses the GET operation to retrieve existing session data based on the dynamic key chat_{{ sessionId }}.
Customer Support Agent (LangChain Agent n8n node): The core AI processor. Its system prompt is dynamically updated based on the existence of data retrieved from Redis, defining whether the user is a 'guest' or 'customer'.
LLM (LangChain LLM ChatOpenAi n8n node): Provides the large language model capabilities, configured here to use a specific GPT model.
Get Auth URL (LangChain Tool Workflow n8n node): This is a critical n8n node that exposes a callable function to the AI agent. When called, it executes the secondary path of this n8n workflow.
Login Form (Form Trigger n8n trigger): A public-facing n8n trigger that acts as the external login portal. It accepts sessionId via a hidden query parameter to maintain context.
Update Session (Redis n8n node): Performs the SET operation to store the authenticated customer profile back into Redis, persisting the login state across future chat messages. The session has a TTL of 3600 seconds.
When Executed by Another Workflow (n8n trigger): Allows the workflow to be triggered internally by the Tool n8n node, enabling dynamic URL generation without interrupting the chat thread.