Feature: Azure Cohere reranker support in nodes-langchain

The idea is:

Add support for an Azure-hosted Cohere reranker sub-node in @n8n/nodes-langchain, including dedicated credentials for Azure Cohere rerank API access and wiring it into vector-store reranking flows.

My use case:

I’m building RAG workflows where retrieved chunks need reranking before final answer generation. My infrastructure uses Azure-hosted Cohere endpoints (not direct Cohere public API), so I need a native n8n node/credential setup that works with Azure base URLs and existing retriever/vector-store patterns.

I think it would be beneficial to add this because:

n8n currently supports Cohere reranking, but Azure-hosted Cohere is a common enterprise deployment path with different endpoint configuration requirements. Native support reduces custom-code workarounds, makes RAG quality improvements easier to adopt, and aligns with n8n’s existing AI sub-node UX for retrievers/vector stores.Any resources to support this?

Are you willing to work on this?

Yes. I’ve already implemented this in my fork and can open/maintain the PR.

PR Link: feat: Add Azure Cohere reranker sub-node by pip-install-skills · Pull Request #28690 · n8n-io/n8n · GitHub

Great call. I’m currently stuck using a messy HTTP Request workaround for Azure-hosted Cohere in my production RAG flows, and it’s a pain to maintain. Having this integrated natively into the LangChain nodes would be a massive cleanup for enterprise workflows. Do you have the PR link handy? I’d love to track this.

1 Like

Thanks! Yeah, I hit the same issue, which is why I built it.

PR: https://github.com/n8n-io/n8n/pull/28690

Adds Azure Cohere creds + reranker node wired into existing LangChain/vector store flows. Would love your feedback if you get a chance to try it.

Hello there again,

I have made a community node if you’d like to use

https://www.npmjs.com/package/n8n-nodes-azure-cohere-reranker

Let me know your thoughts about it @tamy.santos

1 Like