​
Setting Up a PostgreSQL Connection

Click 'Create new Data Connector'

On the Data Connectors page, click the “Create new Data Connector” button and select PostgreSQL from the available options.

Configure Connection Details

You’ll see a form with several fields.
Fields marked with an asterisk (*) are required to establish a connection.
​
Connection Name*
string
  • What it is: A friendly name to identify this connection in Julius
  • Example: “Production DB” or “Sales Database”
  • Tip: Choose a name that helps you remember which database this connects to
​
User*
string
  • What it is: Your PostgreSQL database username
  • Technical note: This is the username that has permission to access the database you want to analyze
  • Security: Julius encrypts and securely stores this credential
​
Password*
string
  • What it is: The password for your PostgreSQL user account
  • Security: Your password is encrypted in transit and at rest for maximum security
​
Host*
string
  • What it is: The server address where your PostgreSQL database is hosted
  • Format: Can be an IP address (like 192.168.1.100) or domain name (like db.mycompany.com)
  • For cloud databases: This is typically provided by your cloud provider (AWS RDS, Google Cloud SQL, etc.)
​
Port*
number
  • What it is: The network port your PostgreSQL database uses for connections
  • Default: PostgreSQL typically uses port 5432
  • When to change: Only change this if your database administrator has configured a custom port
​
Database*
string
  • What it is: The specific database name within your PostgreSQL server that contains the data you want to analyze
  • Example: sales_data, customers, analytics
​
MFA_TYPE
string
  • What it is: Multi-Factor Authentication type if your database requires additional security
  • When needed: Only if your database has been configured with additional authentication requirements
  • Most users: Can leave this blank unless specifically told otherwise by your database administrator

IP Whitelisting (If Required)

If your database has firewall restrictions, you’ll need to whitelist Julius’s IP address to allow connections.

Complete IP Whitelisting Guide

Visit our detailed IP Whitelisting guide for step-by-step instructions for AWS RDS, Google Cloud SQL, Azure, and more hosting environments.

Get Current Julius IP Address

Find the current Julius IP address for whitelisting in your Data Connectors settings.
If you’re unsure whether your database requires IP whitelisting, check with your database administrator or hosting provider.

Test and Save Connection

  1. Click “Add Connection” to test the connection
  2. Julius will attempt to connect to your database with the provided credentials
  3. If successful, your connector will be saved and ready to use
  4. If there’s an error, double-check your credentials and network settings
If the connection fails, common issues include:
  • Incorrect host or port
  • Database not allowing external connections
  • Julius IP not whitelisted (check your settings for the current IP)
  • Wrong username/password

​
Security & Trust

Julius takes data security seriously:
  • SOC 2 Type 2 Certified: Julius meets strict security standards for handling sensitive data
  • Encryption: All credentials and data are encrypted both in transit and at rest
  • No Data Storage: Julius doesn’t permanently store your data - it only queries what you request
  • Access Control: Only you can access connections you create

Learn More About Security

Visit our Security & Trust Center to learn more about how Julius protects your data and maintains compliance standards.

​
Using Your Data Connector

Once your PostgreSQL connector is set up:
  1. Start a new conversation or continue an existing one
  2. Ask Julius about your data using natural language:
    • “Show me all customers from the users table”
    • “What’s the average order value this month?”
    • “Create a chart of sales by region”
  3. Julius will automatically:
    • Connect to your database
    • Write and execute the appropriate SQL queries
    • Present the results in an easy-to-understand format
    • Create visualizations when requested
You don’t need to know SQL! Just ask Julius what you want to know about your data in plain English, and it will handle the technical details.

​
Troubleshooting Common Issues

​
Best Practices

  • Use read-only credentials when possible to prevent accidental data modification
  • Create a dedicated Julius user in your database with only the permissions needed for analysis
  • Test connections with non-production data first to ensure everything works correctly
  • Monitor database performance when running complex queries through Julius
Always coordinate with your database administrator when setting up data connectors to ensure proper security and performance guidelines are followed.