Connection Details

When your vector store is configured and healthy, a Connection Details panel appears below the configuration form. This section provides the information needed to connect your external RAG applications directly to your vector store.

What's Included

Provider	Connection Fields
Supabase	URL, Anon Key (public), Table Name
Pinecone	Host URL, Index Name, Namespace

Field Descriptions

For Supabase

Field	Description	Security
Supabase URL	Your project's API endpoint	Public
Anon Key	Public anonymous key for client-side access	Public (safe to expose)
Table Name	The table storing your vectors (default: document_chunks)	Public

Security Note

The Anon Key is designed to be public and used in client-side applications. It's protected by Row-Level Security (RLS) policies. The Service Role Key (used for admin operations) is never exposed in connection details.

For Pinecone

Field	Description	Security
Host	Your index's host URL	Public
Index	Index name	Public
Namespace	Project-specific namespace (e.g., project-abc123)	Public

note

The Pinecone API key is never exposed in connection details. External apps need their own API key with appropriate permissions.

Additional Information

The Connection Details panel also shows:

• Embedding Configuration: Provider, model, and dimensions used for your vectors
• Index Stats: Vector count and health status

Integration IDs

The Connection Details panel includes an Integration IDs section that displays the unique identifiers needed when configuring external tools like n8n, Langchain, or other RAG frameworks.

Field	Description	When to Use
Organization ID	UUID identifying your organization	Required for all external tool queries to scope results to your organization's data
Project ID	UUID identifying the current project	Optional but recommended to filter results to a specific project's documents

Why These IDs Matter

External tools like n8n and Langchain need to pass filter parameters when querying your vector store. Without these IDs, queries would either fail or return data from all organizations (a security issue).

Why This Matters for External Tool Integration

Previously, users had to:

1. Query the database directly
2. Check browser dev tools network requests
3. Inspect cookies for the project ID

Now these IDs are prominently displayed with one-click copy buttons.

Example: n8n Supabase Vector Store Configuration

When configuring the Supabase Vector Store node in n8n:

1. Copy the Organization ID from Connection Details
2. Copy the Project ID (if you want project-specific results)
3. In n8n's metadata filter, use:

{
  "organization_id": "your-organization-id-here",
  "project_id": "your-project-id-here"
}

tip

Click the copy button next to each ID for one-click copying to your clipboard.

Use Case: External RAG App Integration

These details allow no-code RAG tools (like Flowise, LangFlow, n8n, or custom applications) to connect directly to your vector store for semantic search without going through Vector Data Loader's API.