Pay-i n8n Community Node
Overview
The Pay-i n8n community node is a drop in model provider for the n8n AI Agent node. When configured, LLM requests from your AI Agent workflows will route through the Pay-i proxy making each workflow execution a tracked Use Case Instance within Pay-i, with accurate cost and user attribution, and performance information of your GenAI workloads all without changes to existing pipeline logic.
Providers Supported within n8n
This list is the currently supported providers through the Pay-i platform that you can use within your n8n workflow(s). If you need additional provider support, please contact your account team or customer success contact.
| Provider | Redirect | Credentials Required in n8n |
|---|---|---|
| Pay-i Open AI (Proxy) | OpenAI | PayiAPI + openAiAPI |
| Pay-i Anthropic (Proxy) | Anthropic | PayiAPI + anthropicAPI |
| Pay-i Azure AI Foundry | Microsoft Azure | PayiAPI + AzureOpenAIAPI |
| Pay-i Amazon Bedrock (Proxy) | AWS Bedrock | PayiAPI + aws |
| Pay-i Databricks (Proxy) | Databricks Hosted | PayiAPI + databricks |
Pre-Requisites to use n8n-nodes-pay-i
n8n-nodes-pay-iEnvironment variables
| Variable | Required | Description |
|---|---|---|
N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USEAGE | Yes | Must be set to true. Without it, nodes cannot use the Pay-i provided n8n Node(s) in workflows. |
N8N_LOG_LEVEL | No | Not enabled by default. You can add debug for troubleshooting to see the full request data from your n8n environment. |
EXECUTIONS_DATA_PRUNE | No | Set this value to true if you want to enable auto-pruning of previous workflow execution records |
Installation
Currently n8n support is limited to self hosted options, and your environment needs to allow community nodes via startup, or your n8n instance does not support installation through the n8n in-app gui.
Within n8n UI: Settings > Community Nodes > Search for n8n-nodes-payi > Install
Using npm:
cd ~/.n8n/nodes
npm install n8n-nodes-payi
rm -rf ~/.n8n/.cache
# Restart n8n Docker:
Mount ~/.n8n as a persistent volume, then install inside your container.
Kubernetes: Bake into a custom image, then within your dockerfile - add the following line:
FROM n8nio/n8n:latest
RUN cd /home/node/.n8n/nodes && npm install n8n-nodes-payi@<VERSION>Configure the Pay-i Credential
Before using the Pay-i n8n node, the credentials for your environment needs to be set.
Within the n8n GUI, add an API key from the Application or Organization blade. You will want to make sure you also grab your API URL value from that same area, and use that as the BaseURL value within your n8n Pay-i node.
When you save this credential, n8n will test the connection automatically.
Your First Workflow.
Within n8n open a new, or existing workflow and:
- Add an AI Agent node to the wortkflow.
- Attach a Pay-i [Provider Name] (Proxy) node to the AI Agent's model
- On the Pay-i node, select your Pay-i API Credential, and your the credential from a supported provider.
- Set the Model field with a valid model name (for example:
gpt-4o) - Execute your Workflow.
After this workflow runs you check your Pay-i dashboard The Use Case name should default to your workflow name.
How to get Support:
Issue | Support Level | How to Contact |
|---|---|---|
Issues with Pay-i Platform | Per your contract | |
Issues with n8n | Provided by n8n | Use existing methods to reach n8n support |
Github Repo | Github Repo or Email | On Github: https://github.com/pay-i/n8n-nodes-payi/issues |
Updated about 2 hours ago