Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.workshop.ai/llms.txt

Use this file to discover all available pages before exploring further.

What Are Connectors?

Connectors link external services to Workshop. Once connected, Workshop can use AI models, query your databases, and access your files across all your conversations — no need to manually copy data or explain your setup each time.

AI Providers

Workshop includes three built-in AI providers — Anthropic (Claude), OpenAI (GPT), and Google Gemini. Enable them per project via Add-Ons in project settings or during project creation. When enabled, Workshop provisions a managed connector that handles API keys, authentication, and billing through your Workshop credits — no setup required. If you prefer to manage billing directly with a provider, BYOK (Bring Your Own Key) connectors are available for each.

Managed AI Connectors

How managed connectors work, what each provider offers, and when to use BYOK instead.

BYOK Setup Guides

Anthropic

Use your own Claude API key

OpenAI

Use your own GPT API key

Gemini

Use your own Gemini API key

Database Providers

Workshop can provision a managed Neon serverless Postgres database for your project. Enable it via Add-Ons in project settings or during project creation. Workshop handles provisioning, credentials, and cleanup automatically — including Neon Auth, a built-in authentication service that keeps your app’s auth domains in sync as you publish and add custom domains.

Managed Database

How managed databases work, what gets provisioned, and Neon Auth.
If you already have your own Neon database (or another database), connect it manually:

Databases (BYOK)

Connect PostgreSQL, MySQL, SQL Server, MongoDB, Supabase, Neon, TiDB, or TigerGraph with your own credentials.

Data Connectors

Connect Workshop to your databases, cloud storage, and productivity tools. You provide credentials once, and Workshop can access and query your data in any conversation.
ConnectorTypeAuthentication
PostgreSQL, MySQL, SQL Server, MongoDB, Supabase, Neon, TiDB, TigerGraphDatabasesHost + credentials or connection URL
BigQuery, Snowflake, TableauData warehousesService account or credentials
Google SheetsSpreadsheetsURL (public) or Service Account (private)
Google DriveCloud storageOAuth
AWS S3Cloud storageAccess Key + Secret
GitHubSource control APIPersonal Access Token

How Connectors Work

When you add a data connector:
  1. Your credentials are stored securely in Workshop’s encrypted storage
  2. Workshop’s agent receives a reference to your connection, not the raw credentials
  3. Data stays in your source — Workshop queries it on-demand rather than copying it
You maintain full control over your data while giving Workshop the ability to help you work with it.

Adding a Data Connector

1

Open the Hub

Open the Workshop Hub from the sidebar.
2

Go to Connectors

Click the Connectors tab.
3

Choose a connector

Select the connector type you want to add from the card list, or search by name.
4

Enter credentials

Fill in the required connection details for that connector.
5

Add connection

Click Add Connection. Workshop tests the connection and saves it.
Once connected, reference your connection by name or type in any conversation:
  • “Using my Production Database connection, show me all users who signed up last week”
  • “Query my Supabase data for the top 10 products by revenue”

Managing Connections

Your active connections appear in the Active Connections table in the Connectors tab. From there you can:
  • View connection details and status
  • Edit connection credentials
  • Delete connections you no longer need
Deleting a connection removes both the connector configuration and its stored credentials from Workshop.

Security

  • Credentials are encrypted at rest and in transit
  • Connections use SSL/TLS for all data transmission
  • Data is queried on demand — Workshop queries your sources directly and does not store your data separately
  • You control access — delete connections anytime to revoke access
Published apps use the same connector credentials you configure in development. Be mindful of which connectors you attach to apps you plan to publish.