agentauth

n8n node for AgentAuth - secure session management for AI agents

Package Information

Downloads: 0 weekly / 0 monthly
Latest Version: 0.1.2
Author: Jacob Gadek

Documentation

AgentAuth for n8n 🕵️‍♂️🍪

Bypass 2FA, Cloudflare, and complex login forms in n8n by syncing your authenticated local Chrome session.

AgentAuth allows your n8n workflows to "inherit" the cookies and headers from your local Chrome browser. Instead of trying to automate the login process (which breaks with Captchas/2FA), AgentAuth simply grabs the valid session you already have.

🚀 Features

  • Bypass Everything: If you can log in on Chrome, you can automate it in n8n.
  • Headless Support: Works on remote servers (VPS, Docker, Cloud) via the export command.
  • Local & Secure: Cookies are encrypted locally (AES-256). No data is ever sent to a third-party cloud.

📦 Installation

AgentAuth requires two parts:

  1. The Python CLI (runs on your computer to grab cookies).
  2. The n8n Node (runs in your workflow to use them).

Step 1: Install the CLI Tool

On your local machine (where you have Chrome installed):

pip install agentauth-py

Step 2: Install the n8n Node

In your n8n instance (Settings > Community Nodes):

n8n-nodes-agentauth

⚡ Quick Start (Local n8n)

Use this if n8n is running on the same computer as your Chrome browser.

  1. Grab a Session:
agent-auth grab github.com
  1. Use it in n8n:
    • Add the AgentAuth node to your workflow.
    • Enter the domain: github.com.
    • Connect it to an HTTP Request node.
    • The HTTP Request will now be authenticated as YOU.

☁️ Remote Servers (VPS / Docker / Headless)

Use this if your n8n runs on a server where Chrome is NOT installed.

  1. On your Local Computer:
agent-auth grab linkedin.com
agent-auth export
  1. Copy to server:
scp ~/.agent-auth/vault-export.enc user@your-server:~/
  1. On your Remote Server:
pip install agentauth-py
agent-auth import ~/vault-export.enc

Now your remote n8n instance can access linkedin.com sessions.


🔒 Security

  • Local Only: No external API calls.
  • Encryption: Vault encrypted with AES-256.
  • Open Source: 100% transparent code.

Links

License

MIT

Discussion