How connectors work
- Secure Flow: Your app connects to the Major API, which proxies requests to your actual connectors.
- Authentication: Powered by a
MAJOR_JWT_TOKENissued to your session. This token contains your user scopes, ensuring the client can only access what you’re permitted to access. - Generated Clients: Major generates resource clients for you. You’ll find one per resource in
src/clients/.
Setting up a connector
- Navigate to Organization Settings > Connectors
- Click Add Connector and select the type
- Configure the connection details and credentials
- Attach the connector to your app via the web editor or
major resource manage
Resource credentials are encrypted and never exposed to the client-side application code.
Per-environment configuration
When editing a connector, you can configure each environment independently. This lets you use different credentials or endpoints for staging and production.| Environment | Host | Database |
|---|---|---|
| default | prod.example.com | myapp_prod |
| staging | staging.example.com | myapp_staging |
Learn more about Environments
See how to create and manage environments for your organization.
Identity-based authentication
For S3 and DynamoDB resources, you can use Assume Role Identities instead of access keys. Create an identity in the web UI, review the generated trust policy for your IAM role, and select identity-based authentication when configuring your resource. This approach is more secure and avoids managing long-lived credentials.Available connectors
PostgreSQL
SQL database queries
DynamoDB
AWS NoSQL database
S3 Storage
Object storage and files
Snowflake
Data warehouse queries
Microsoft SQL Server
SQL Server queries
BigQuery
Google BigQuery datasets
Neo4j
Graph database queries
AWS Lambda
Serverless function invocation
Custom API
Any REST API
Salesforce
CRM data and SOQL
HubSpot
CRM integration
Outreach
Sales engagement
Google Sheets
Spreadsheet access