Managing Connections

Managing Connections

Learn how to manage your data connectors in Querri—from adding new integrations to troubleshooting connection issues.

Accessing the Connectors Page

All connector management happens in one central location:

1. Click Settings in the navigation menu
2. Select Connectors
3. You’ll arrive at /settings/connectors

This page shows:

• All available connector types
• Your active connections
• Connection status for each connector
• Options to add, edit, or remove connectors

Viewing Connected Connectors

Active Connections

The Connectors page displays all your connected integrations:

Connection card shows:

• Connector name: Type of integration (e.g., “PostgreSQL”, “Google Drive”)
• Display name: Your custom name for this instance
• Status: Connection health indicator
• Last used: When data was last accessed
• Actions: Quick access to settings and controls

Status indicators:

• ✅ Connected: Active and working properly
• ⚠️ Warning: Connected but may need attention
• ❌ Error: Connection failed or credentials invalid
• 🔄 Pending: OAuth authorization in progress
• ⏸️ Disabled: Manually disabled, not in use

Connection Categories

Connectors are organized by category:

Database

• PostgreSQL, MySQL, MSSQL, MongoDB, SQLite

Storage

• Google Drive, Dropbox, OneDrive, S3

Accounting

• QuickBooks Online, Xero, FreshBooks

CRM

• Salesforce, HubSpot, Pipedrive, Zoho

Other

• Custom APIs, Stripe, Shopify, and more

Use the category tabs to filter and find connectors quickly.

Adding New Connectors

Step 1: Choose a Connector Type

1. Navigate to the Connectors page
2. Browse available connectors by category
3. Click Connect on the connector you want to add

Available connectors show:

• Connector logo and name
• Brief description
• Authentication type (OAuth or credentials)

Step 2: Configuration

The configuration process depends on the connector type:

OAuth Connectors (Google Drive, Salesforce, etc.)

1. Click Connect
2. A popup window opens to the provider’s authorization page
3. Sign in to your account
4. Review and accept permissions
5. The popup closes automatically
6. The connector activates immediately

No manual configuration needed for OAuth connectors—just authorize access.

Credential-Based Connectors (Databases, APIs)

1. Click Connect
2. A configuration form appears
3. Fill in required fields:
   • Display Name: Custom name for this connection
   • Host/URL: Server address
   • Port: Connection port (if applicable)
   • Credentials: Username, password, API key, etc.
4. Optional settings (SSL, timeout, advanced options)
5. Click Test Connection
6. If successful, click Save

Example (PostgreSQL):

Display Name: Production Database
Host: db.mycompany.com
Port: 5432
Database: analytics
Username: querri_readonly
Password: ••••••••••
SSL Mode: require

Step 3: Verify the Connection

After adding a connector:

1. It appears in your active connections list
2. Status should show “Connected”
3. Test by running a simple query in chat:
   • “List files from Google Drive”
   • “Show tables in the Production Database”
   • “How many contacts are in HubSpot?”

If the query works, your connector is properly configured.

Editing Connector Settings

Modifying Configuration

To edit an existing connector:

1. Find the connector in your active connections
2. Click the Settings or Edit icon
3. The configuration form opens with current settings
4. Modify the fields you want to change
5. Click Test Connection to verify
6. Click Save to apply changes

What you can edit:

• Display name
• Connection credentials (host, username, password)
• Optional settings (SSL, timeout, etc.)

What you cannot edit:

• Connector type (create a new connector instead)
• OAuth tokens (must reconnect to refresh)

Changing Display Names

Display names help you identify connectors in queries:

To change a display name:

1. Edit the connector settings
2. Update the Display Name field
3. Save

Best practices:

• Use descriptive, unique names
• Include environment: “Production DB”, “Staging DB”
• Add purpose: “Customer Analytics”, “Sales Reporting”
• Keep names concise (2-4 words)

Examples:

Good: "Production PostgreSQL"
Better: "Customer Orders DB"

Good: "Google Drive"
Better: "Marketing Google Drive"

Custom Naming Connectors

Custom names make connectors easier to reference in AI queries.

Default vs. Custom Names

Default naming:

• Uses the connector type: “MySQL Connector”
• Not unique if you have multiple instances
• Less intuitive in queries

Custom naming:

• Descriptive and specific: “E-commerce Database”
• Unique across all your connectors
• Natural to reference: “show sales from E-commerce Database”

Naming Strategies

By environment:

PostgreSQL - Production
PostgreSQL - Staging
PostgreSQL - Development

By function:

Customer Data Warehouse
Sales Analytics DB
Product Inventory System

By department:

Marketing Google Drive
Sales Salesforce Org
Finance QuickBooks

By region:

US East Database
Europe MySQL Server
Asia Pacific Storage

Testing Connections

Regular connection tests ensure your integrations stay healthy.

Manual Testing

From connector settings:

1. Edit the connector
2. Click Test Connection
3. Wait for the test result
4. Review any error messages

Test results:

• ✅ Success: Connection working properly
• ❌ Failed: Cannot connect (see error details)
• ⚠️ Warning: Connected but with issues (e.g., slow response)

Automatic Health Checks

Querri periodically checks connector health:

• OAuth tokens are refreshed automatically
• Database connections are validated
• Failed connections are flagged

Status updates:

• Connection status updates in real-time
• You’ll see warnings if a connector fails
• Email notifications for critical failures (if enabled)

Test Queries

Run simple test queries in chat to verify connectors:

Database connectors:

"List tables in [connector name]"
"Show me one row from [table name]"

Storage connectors:

"List files in [connector name]"
"Show recent files from [folder name]"

Business app connectors:

"How many records are in [connector name]?"
"Show one [object] from [connector name]"

If test queries work, the connector is functioning correctly.

Disabling and Removing Connectors

Disabling Connectors

Temporarily disable a connector without removing it:

1. Find the connector in your active connections
2. Click the Disable option
3. The connector status changes to “Disabled”

When disabled:

• Not available for queries
• Credentials remain saved
• Can be re-enabled instantly
• Doesn’t count toward connector limits

To re-enable:

1. Click Enable on the disabled connector
2. Status returns to “Connected”
3. Immediately available for use

Use cases for disabling:

• Temporarily restricting access to a data source
• Troubleshooting which connector is causing issues
• Pausing during maintenance windows
• Testing queries without certain data sources

Removing Connectors

Permanently delete a connector:

1. Find the connector in your active connections
2. Click Remove or Delete
3. Confirm the deletion
4. The connector is removed immediately

What happens when removed:

• All saved credentials are deleted
• Connection is terminated
• Connector no longer appears in active connections
• Cannot be recovered (must reconnect from scratch)

When to remove:

• No longer need access to the data source
• Switching to a different connector
• Cleaning up old/unused integrations
• Security policy requires revoking access

Pending OAuth Cleanup

When OAuth authorization is interrupted, pending connections may remain.

What Are Pending Connections?

Pending connections occur when:

• OAuth popup was closed before completing authorization
• Network error during OAuth flow
• User canceled authorization
• OAuth provider rejected the request

Status shows: “Pending” or “Authorization Incomplete”

Cleaning Up Pending Connections

To remove pending connections:

1. Find connectors with “Pending” status
2. Click Remove or Cancel
3. The incomplete connection is deleted

To complete pending connections:

1. Click Retry or Complete Authorization
2. The OAuth popup reopens
3. Complete the authorization process
4. Status updates to “Connected”

Pending connections are automatically cleaned up:

• After 24 hours of inactivity
• If you start a new authorization for the same connector
• When you manually remove them

Preventing Pending Connections

Best practices:

• Don’t close OAuth popups before authorization completes
• Ensure popup blockers aren’t preventing the flow
• Complete MFA/authentication when prompted
• Wait for the “Success” message before closing anything

Troubleshooting Connection Issues

Connection Failed Errors

Problem: “Connection failed” or “Cannot connect to server”

Common causes:

• Incorrect host or port
• Firewall blocking access
• Server is down or unreachable
• Network connectivity issues

Solutions:

1. Verify host and port are correct
2. Check if server is running
3. Test network connectivity (ping the host)
4. Whitelist Querri’s IP addresses in firewall
5. Ensure no VPN is interfering

Authentication Errors

Problem: “Authentication failed” or “Invalid credentials”

Common causes:

• Wrong username or password
• Password has changed
• User account is locked or disabled
• Permissions were revoked

Solutions:

1. Double-check username and password
2. Reset password if necessary
3. Verify account is active
4. Ensure account has necessary permissions
5. For databases, test credentials using a DB client

OAuth Token Expired

Problem: “Token expired” or “Reconnect required”

Common causes:

• OAuth token has expired (typically 60-90 days)
• Permissions were revoked by user or admin
• OAuth app was deauthorized

Solutions:

1. Click Reconnect in connector settings
2. Complete OAuth authorization again
3. Check if admin revoked access (for corporate accounts)
4. Verify the OAuth app is still approved

SSL/TLS Errors

Problem: “SSL certificate error” or “TLS handshake failed”

Common causes:

• Self-signed certificates
• Certificate mismatch
• Outdated SSL/TLS version
• SSL required but not configured

Solutions:

1. Enable SSL mode in connector settings
2. Use correct SSL mode (require, verify-ca, verify-full)
3. For self-signed certs, may need to disable SSL verification (not recommended)
4. Update database server to support modern TLS

Permission Errors

Problem: “Access denied” or “Insufficient permissions”

Common causes:

• Database user lacks SELECT permission
• OAuth scope doesn’t include requested data
• Object-level permissions missing (Salesforce)
• IP whitelist restrictions

Solutions:

1. Grant read permissions to database user
2. Re-authorize OAuth with broader scopes
3. Check object and field-level permissions
4. Whitelist Querri’s IP addresses

Slow Performance

Problem: Queries are slow or timing out

Common causes:

• Large dataset with no filtering
• Missing indexes on frequently queried columns
• Network latency
• API rate limiting

Solutions:

1. Add date/time filters to queries
2. Create indexes on database columns
3. Use database replicas instead of primary
4. Check for API rate limit warnings
5. Optimize query patterns

Data Not Appearing

Problem: Connected successfully but can’t see data

Common causes:

• User doesn’t have permission to view data
• Querying wrong database/schema/table
• Data exists but is filtered out
• Custom objects need explicit permissions

Solutions:

1. Verify permissions in the source system
2. Check database/schema name is correct
3. List available tables/objects to confirm access
4. For Salesforce, ensure custom object permissions

Best Practices for Managing Connections

Regular Maintenance

• Review connections monthly: Remove unused connectors
• Test critical connections: Ensure production integrations work
• Update credentials: Rotate passwords per security policy
• Monitor status: Check for warnings or errors

Organization

• Consistent naming: Use a standard naming convention
• Group by purpose: Organize similar connectors together
• Document configuration: Keep notes on special settings
• Track ownership: Know who manages each connector

Security

• Least privilege: Only grant necessary permissions
• Read-only access: Use read-only credentials when possible
• Revoke unused: Remove connectors you no longer need
• Audit regularly: Review which apps have access to your data

Performance

• Use replicas: Connect to read replicas, not primary databases
• Optimize credentials: Use service accounts, not personal accounts
• Connection pooling: Configure appropriate connection limits
• Monitor usage: Track which connectors are used most

Connector Limits

Querri may have limits on the number of connectors:

Typical limits (varies by plan):

• Free tier: 5-10 connectors
• Pro tier: 25-50 connectors
• Enterprise: Unlimited

If you hit the limit:

• Remove unused connectors
• Disable temporarily-unused connectors
• Upgrade to a higher plan
• Consolidate similar data sources

Getting Help

If you’re experiencing connection issues:

1. Check documentation: Review connector-specific guides
2. Test connectivity: Use native tools to verify access
3. Review error messages: Error details often indicate the problem
4. Contact support: Reach out with error details and connector info

Information to provide:

• Connector type
• Error message (exact text)
• When the issue started
• Steps to reproduce
• Connection test results

Next Steps

• Data Connectors Overview - Learn about connector types
• Connecting Databases - Database-specific setup
• Google Drive - Google Drive connector with secure file selection
• Business Applications - CRM, accounting, and CMMS apps

Security and Privacy

Credential storage:

• All credentials encrypted at rest
• OAuth tokens refreshed automatically
• No plain-text password storage

Data access:

• Connectors access data only during queries
• No permanent data storage
• Query results processed in memory

Revoking access:

• Remove connector in Querri
• Revoke app access in the provider’s settings
• Credentials immediately deleted