Implementing SSL/TLS Certificate Authentication in HTTP Request Node

Implementing SSL/TLS Certificate Authentication in HTTP Request Node

Hello n8n community,

I’ve been working on setting up workflows in n8n that require secure communication with external APIs. Specifically, I need to authenticate HTTP requests using an SSL/TLS certificate (<certificate_name>.pem). However, I’ve encountered an issue when trying to implement this within the HTTP Request node.

I’ve looked through the documentation and searched the forums, but I haven’t found a clear guide or feature that allows for the inclusion of .pem certificate files in the HTTP Request node’s configuration. The ability to authenticate using SSL/TLS certificates is crucial for my workflows, as they interact with APIs that require this level of security.


  1. Is there currently a way to include and use .pem SSL/TLS certificates within the HTTP Request node for secure authentication?
  2. If not, are there any plans to support SSL/TLS certificate authentication in n8n’s HTTP Request node in the near future?

I understand that security and authentication are complex topics, and I appreciate any guidance or workaround that the community or the n8n team can provide. Implementing this feature would greatly enhance the capabilities of n8n, especially for users dealing with secure external APIs.

Thank you in advance for your help and insights.

Information on your n8n setup

  • n8n version : 1.24.1
  • Database : SQLite
  • n8n EXECUTIONS_PROCESS setting : own
  • Running n8n via : Docker

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:

Hey @Florent_Colombari,

Welcome to the community :cake:

At the moment it is not possible but we have a feature request here: SSL Certificate for Http Request you can pop a vote on

This is something that is fairly high up on our Node teams list of things to implement soon, I am not sure when this will happen but I would say it is closer to weeks than months if that makes sense.