Internal Network & Isolation

At AIBuildr, every tenant (client) is deployed within its own isolated network. This means your services can communicate with each other at maximum speed without leaving the internal infrastructure, improving security and reducing latency.

Available Environment Variables

To facilitate this communication, your n8n and Flowise instances come pre-configured with environment variables pointing to the other services in your stack.

In n8n

You can use these variables in your nodes (e.g., in an HTTP Request node or service-specific nodes):

Variable	Internal Value (Example)	Primary Use
FLOWISE_URL	http://flowise-your-slug:3000	Connect to Flowise API
REDIS_URL	redis://redis-your-slug:6379	Use shared cache in workflows

In Flowise

Similarly, Flowise can “talk” to n8n and Redis:

Variable	Internal Value (Example)	Primary Use
N8N_URL	http://n8n-your-slug:5678	Trigger n8n workflows from agents
REDIS_URL	redis://redis-your-slug:6379	Persistent memory for conversations

---

Common Use Cases

1. Redis as Memory in n8n

If you need high-speed state persistence between workflow executions:

1. Add a Redis node in n8n.
2. In credentials, select “Redis connection”.
3. Use the environment variable or internal URL: redis://redis-your-slug:6379.
4. Done! You have a high-performance cache dedicated to you.

2. n8n + Flowise Orchestration

You can use n8n to receive complex webhooks, process data, and then send it to a Flowise agent for final reasoning.

• In n8n: Use an HTTP Request node pointing to {{ $env.FLOWISE_URL }}/api/v1/prediction/...
• Benefit: The request travels through the internal Docker network; it’s instant and doesn’t count as external traffic.

3. Flowise Agents triggering n8n Tools

Your Flowise agents might need to execute a specific action (e.g., “Send an email” or “Search CRM”) that you’ve already built in n8n.

• Configure a “Custom Tool” in Flowise.
• Point the URL to {{ $env.N8N_URL }}/webhook/...

---

Data Architecture (Postgres & Qdrant)

Your database services are also optimized, though their configuration is automatic and transparent to you:

• Shared PostgreSQL: n8n, Flowise, and Evolution API use a central optimized Postgres server, but each has its own Isolated Schema. No one else can see your data.
• Shared Qdrant: Your vector database uses collections with unique prefixes and API Keys generated specifically for your deployment.