Connections
Learn how Connections give Giga secure access to the tools, apps, databases, and systems your company already uses.
A Connection gives Giga access to an external tool or system so it can work with live company information and, where permitted, take action there.
Connections can represent apps, APIs, databases, browser sessions, MCP servers, and other connected services.
What Connections make possible
Read live information
Let Giga retrieve current data from connected tools instead of relying only on what is already in the Chat.
Take action
Let Giga perform supported actions through the connected service when your permissions allow it.
Use company systems
Work with APIs, databases, internal tools, and other systems already used by your company.
Extend Giga
Add custom connections when the service is not already covered by a built-in option.
Video placeholder
Connected Apps & Integrations overview video.
Connect from Chat or manage Connections directly
You do not always need to leave a Chat to start connecting something.
When the connection flow supports it, you can tell Giga what you want to connect and Giga can start the secure setup flow from the Chat.
You can also manage your Connections from the Connections area in Giga.
How Giga connects
Different services support different connection methods.
| Connection method | Typical use |
|---|---|
| MCP | A service exposes an MCP server that Giga can connect to |
| OAuth | A service supports delegated account access through OAuth |
| API key or PAT | The service uses a user-provided key or personal access token |
| Database connection | Giga connects to an external database using stored credentials |
| Browser session | Giga needs to interact with a website directly when another connection method cannot complete the task |
For new or custom integrations, Giga’s operating guidance prefers the strongest self-serve path available in this order:
- MCP
- OAuth when a supported self-serve OAuth flow is available
- API key or PAT
- Browser login
The exact method depends on the service and the connection mechanisms it actually supports.
Connections stay permission-aware
A Connection does not automatically give every person or every piece of work access to the same systems.
Giga checks the live workspace state to determine:
- which Connections you can access
- which credentials are yours
- which credentials have been shared into a Group you belong to
- which actions the connected service allows
- which tools are currently exposed in your session
Live access is the source of truth
Giga should inspect the current workspace and connection state rather than assuming a service is connected or that a user has permission to use it.
Secrets stay out of Chats
Credentials are stored securely and used through Giga’s connection layer.
Giga should never ask you to paste passwords, API keys, tokens, OAuth secrets, or database connection strings into a normal Chat when a secure connection flow is available.
For services that require a user-provided secret, Giga can direct you to the appropriate secure setup flow.
Keep credentials in the secure connection flow
Secrets should not be written into Chats, Context Notes, or files.
Built-in and custom Connections
Some services are already available through Giga’s integration catalog.
If the service already exists there, Giga should use that existing integration rather than creating a duplicate.
For services that need something more specific, Giga can support custom connection paths such as:
Custom MCP
Connect an MCP server when that is the service’s supported integration path.
Custom OAuth
Connect your own OAuth setup where Giga supports that path.
API keys
Use secure API-key or PAT based access for compatible services.
Browser connections
Use a browser session for website-based work that cannot be handled through a first-class integration.
Learn about Custom Connections →
How Giga uses a Connection
Once a Connection is available, Giga should use the connection mechanism designed for that service instead of asking you to manually move data between systems.
For example:
- a connected API can be queried directly
- a connected database can be queried without exposing its connection string
- an MCP service can expose its own tools to Giga
- a browser session can be used when direct website interaction is required
This lets a Chat, Agent, or Workflow work with live systems while keeping the underlying credentials protected.
A simple example
Imagine you connect your CRM.
Connection
You securely connect the CRM account to Giga.
Chat
You ask Giga for the latest state of a customer or pipeline.
Live data
Giga retrieves the current information through the connection available to you.
Action
If the connection and your permissions allow it, Giga can carry out a supported CRM action.
You can keep working from the Chat while Giga uses the connected system underneath.
Image placeholder
Diagram showing Chat or Agent → Connection → external app/database, with permissions and secure credentials sitting between Giga and the external system.
Explore Connections
Connect a tool
Connect a supported tool securely.
Managing Connections
Review and manage the Connections already available to you.
Sharing Connections
Understand how connected access can be made available through Groups.
Custom Connections
Connect services through MCP, OAuth, API credentials, or browser access.
Troubleshooting
Resolve common connection and authentication issues.