Skip to main content
n8n is a workflow automation platform that helps you connect different systems and automate tasks. While n8n delivers robust automation capabilities, Obiguard adds essential enterprise controls for production deployments:
  • Unified AI Gateway - Single interface for 1600+ LLMs with API key management. (not just OpenAI & Anthropic)
  • Centralized AI observability: Real-time usage tracking for 40+ key metrics and logs for every request
  • Governance - Real-time spend tracking in your n8n setup
  • Security Guardrails - PII detection, content filtering, and compliance controls
This guide will walk you through integrating Obiguard with n8n and setting up essential enterprise features including usage tracking, and access controls.

1. Setting up Obiguard

Obiguard allows you to use 1600+ LLMs with your n8n setup, w ith minimal configuration required. Let’s set up the core components in Obiguard that you’ll need for integration.
1

Create an access key

Callers authenticate to the Obiguard gateway with an access key. Your provider credentials (for example your OpenAI or Anthropic key) stay stored in Obiguard and are never shared with the tools that call it.In the Obiguard dashboard, create an access key for the agent or project that should use n8n, and copy it.
Save your access key securely - you’ll need it for the n8n integration below.

2. Integrate Obiguard with n8n

Now that you have your Obiguard components set up, let’s connect them to n8n. Since Obiguard provides OpenAI API compatibility, integration is straightforward and requires just a few configuration steps in your n8n workflow.
You need your access key from Step 1 before going further.
  1. In your n8n workflow, add the OpenAI node where you want to use an LLM
  2. Configure the OpenAI credentials with the following settings:
    • API Key: Your Obiguard access key from the setup
    • Base URL: https://gateway.obiguard.ai/v1
When saving your Obiguard credentials in n8n, you may encounter an “Internal Server Error” or connection warning. This happens because n8n attempts to fetch available models from the API, but Obiguard doesn’t expose a models endpoint in the same way OpenAI does. Despite this warning, your credentials are saved properly and will work in your workflows.
  1. In your workflow, configure the OpenAI node to use your preferred model
    • The model parameter in your config will override the default model in your n8n workflow
It is recommended that you define a comprehensive config in Obiguard with your preferred LLM settings. This allows you to maintain all LLM settings in one place.
Use the complete model name given by the provider.
You can monitor your requests and usage in the Obiguard Logs.

Obiguard Features

1. Comprehensive Metrics

Using Obiguard you can track 40+ key metrics including cost, token usage, response time, and performance across all your LLM providers in real time. You can also filter these metrics based on custom metadata that you can set in your configs. Learn more about metadata here.

2. Advanced Logs

Obiguard’s logging dashboard provides detailed logs for every request made to your LLMs. These logs include:
  • Complete request and response tracking
  • Metadata tags for filtering
  • Cost attribution and much more…

3. Unified Access to 1600+ LLMs

You can easily switch between 1600+ LLMs. Call various LLMs such as Anthropic, Gemini, Mistral, Azure OpenAI, Google Vertex AI, AWS Bedrock, and many more by simply changing the model and provider in your requests.

4. Advanced Guardrails

Protect your Project’s data and enhance reliability with real-time checks on LLM inputs and outputs. Leverage guardrails to:
  • Prevent sensitive data leaks
  • Enforce compliance with organizational policies
  • PII detection and masking
  • Content filtering
  • Custom security rules
  • Data compliance checks

Guardrails

Implement real-time protection for your LLM interactions with automatic detection and filtering of sensitive content, PII, and custom security rules. Enable comprehensive data protection while maintaining compliance with organizational policies.

FAQs

Yes! Your access key can be used with any provider whose credentials are stored in Obiguard. Select the provider and model for each request or in your config.
You can control model access by:
  1. Setting specific models in your Obiguard configs
  2. Creating different access keys for different agents or projects
  3. Implementing conditional routing based on workflow metadata

Next Steps

The complete list of features supported in the SDK are available on the link below.

Obiguard SDK Client

Learn more about the Obiguard SDK Client