Help / Integrations /

n8n

Use the Condens MCP Server with n8n to build AI agents that query your research repository mid-workflow. Instead of working from general knowledge alone, your agent can pull relevant insights, reports, or usability findings to inform whatever it's working on: drafting a product brief, answering a stakeholder question, or cross-referencing a roadmap item against what users have actually said.

The n8n integration via MCP Server is available in the Enterprise plan.

Before you start, you will need:

  • An n8n account (cloud plan or self-hosted instance)

  • A Condens account with Admin access to enable the MCP Server for your workspace and authorize the connection, and optionally a dedicated Condens Viewer account

Recommended setup: AI Agent node

The Condens MCP Server is designed for AI agents that chain multiple tool calls to retrieve and synthesize research data. We recommend adding the MCP Client as a tool inside an AI Agent node rather than using standalone MCP Client nodes. You can still chain MCP Client nodes manually, but this requires more configuration.

Step 1: Configure the MCP Client node in n8n

  1. In n8n, click on Create workflow in the top right corner.

  2. For this example, we'll click on Add first step..., and select Trigger manually as the trigger.

  3. Click on the + and add the AI Agent node.

  4. Within the AI Agent node, click on + to add a new Tool and select MCP Client.

  5. Configure it as follows:

    1. Endpoint URL: Copy the MCP URL from your Condens workspace under Settings > API & MCP Server. Depending on your server region, it's:

    2. Server transport: HTTP Streamable

    3. Authentication: MCP OAuth2

  6. Click Set up credential. Copy the OAuth Redirect URL — you will need it for the next steps. Please keep this tab open and open Condens in a new tab.

Step 2: Create new MCP client in Condens

Before creating your credentials, decide which Condens account you'll use to authorize the connection:

  • Your own account — best for personal workflows. Keep in mind that credentials can expire after a period of inactivity. If that happens, whoever re-authorizes the connection will need the right access in both n8n and Condens.

  • A dedicated Viewer account— recommended for shared or team workflows. A dedicated account keeps the connection predictable and independent of any individual's access or activity.

Option A: Using your own account

An Admin in Condens needs to:

  1. Go to Settings > API & MCP Server

  2. Click Add MCP Client

  3. Configure the MCP Client:

    1. Give the client a name, description, and upload a logo.

    2. Paste the OAuth Redirect URL you copied from n8n

    3. Set the Available for to the roles and users who should have access. Once the client is configured, these users will be able to connect to this MCP client via their own account in Settings > Integrations.

    4. Add setup instructions for your colleagues to help them connect to this MCP on an individual level.

  4. Click Create.

Option B: Using a dedicated Viewer account

icon lightbulb

You can find a more detailed step-by-step guide on setting up any custom MCP client with a dedicated Viewer account here.

  1. Set up a dedicated Condens Viewer account for this workflow. For example, using a shared team email like mcp@yourcompany.com.

  2. You'll need admin access in Condens to create the new Viewer account and configure its workspace access to only the content you want available through this workflow.

  3. Then open an incognito/private browser window, log into Condens with that account, and follow the same credential steps as Option A. The authorization in the following steps will be done as that Viewer account.

Step 3: Authorize the connection

  1. Go back to n8n and paste the Server URL, just below where you copied the OAuth Redirect URL from.

  2. Click Connect to MCP.

  3. If everything is configured correctly, n8n will open a new tab with a Condens authorization page. As the final step, click Continue to grant n8n access to your Condens workspace.

That's it! You can now use the MCP Client node to call the available Condens MCP tools in your workflows. Continue configuring your AI agent as needed by selecting the Chat Model, Memory, and next steps in the workflow.

Need help?

If you run into issues, reach out to us at support@condens.io.

Didn't find what you're looking for? Send us a message and we'll get back to you.
Contact us