AI clients and agents

Argent for n8n

Self-hosted n8n workflows send their OpenAI and Anthropic node calls through Argent. Here is what Argent governs, how it connects and what your team sets.

01 / AI CLIENTS AND AGENTS

What Argent does with n8n

Every model call an app makes with n8n goes through Argent first. Argent knows which agent sent it and which person owns that agent, checks it against your policy, and writes a signed record of what it decided.

  • A named agent with a human owner. Each app or service you connect uses its own Argent agent key, tied to an accountable person, so no call is anonymous. Identity tethering
  • Only the models you allow. The agent can reach only the providers and models your policy names, and a request can be swapped to an approved model. Model control
  • Sensitive data handled before it leaves. Prompts and replies are scanned for personal and secret data, then redacted or blocked as your policy says. Sensitive data redaction
  • Spend priced and capped. Every request is priced and metered against budgets for the agent, its owner and the teams above them. AI spend caps
  • A signed record you can replay. Each decision becomes a hash-chained, signed audit record, and requests are grouped into sessions you can replay. Session replay
02 / AI CLIENTS AND AGENTS

How n8n connects

n8n reaches Argent in two ways.

  • TLS-inspecting forward proxy. Your app keeps its normal n8n settings and sends its HTTPS traffic through the Argent forward proxy and trusts your Argent certificate; the exact settings are below. The proxy signs in with the agent's own key, so every call is attributed, then runs the same checks as the gateway. It opens only known AI hosts, and its certificate is limited to those hosts.
  • Gateway base URL. Your app points n8n at your Argent route (its base URL setting) and uses an Argent agent key in place of the provider key. Argent removes that key and adds the real provider credential from your vault on the way out, so your app never holds it.

Proven with the real tool. Argent's team has driven n8n itself through a live Argent gateway and checked the signed records it produced.

The same steps are in the Argent console under Integrations > AI Clients, and each agent's Connect tab gives the copy-paste values for your tenant.

03 / AI CLIENTS AND AGENTS

What you configure

What your team sets in n8n. These are the settings the Argent console shows for this tool. Values in angle brackets come from your tenant.

  1. Forward proxy. On the n8n container/service set HTTPS_PROXY=http://<user>:<ARGENT_AGENT_KEY>@<ARGENT_PROXY_HOST>, NO_PROXY for internal hosts, and NODE_EXTRA_CA_CERTS=/path/argent-ca.pem. Keep the node's normal OpenAI credential (a placeholder key is fine when Argent brokers the real key).
  2. Gateway alternative. The OpenAI credential has a Base URL field: set https://<ARGENT_GATEWAY>/<tenant>/openai/v1 and an Argent agent key as the API key.
04 / AI CLIENTS AND AGENTS

Make Argent the only path

Make Argent the only path for n8n. These controls are documented by the platform each one belongs to (linked); pair them with the Argent settings above.

  • Service / container environment (Linux, Kubernetes, CI). Sets the variables where most production SDK code runs. Vendor docs
  • Provider-side lock at OpenAI or Anthropic: only the Argent egress IP may use your org's keys. Even a stolen key or a code path that skips the base URL is rejected by the vendor. OpenAI docs, Anthropic docs

Same settings everywhere it runs. The Argent fleet setup script and certificate bundle give every service, container and build runner the same proxy and certificate settings.

Want to see which AI tools people already run before you push anything? Start with Shadow AI discovery in watch mode. Watch before you enforce

05 / AI CLIENTS AND AGENTS

Check that it works

Send one request and look for the signed row. LLM rows in the Argent console live stream for each workflow run.

Every request also appears on the live stream with the agent's name and owner, and in the session view. Session replay