Custom Connections

Giga can connect to tools beyond the standard integration catalog through Custom Connections.

Use a Custom Connection when the service you need is not already available through a built-in Connection, or when your company needs to use its own MCP server, OAuth setup, API credentials, or browser-based access.

Start by checking for an existing integration

Before creating something custom, Giga should check whether the product is already available in the integration catalog.

If it already exists, use the existing integration and its supported connection methods instead of creating a duplicate.

Use the existing integration when one already exists

Custom Connections are for genuinely new or specialized connection needs, not a second copy of an integration Giga already knows about.

Custom Connection options

How Giga chooses a connection path

For a new integration, Giga should prefer the strongest self-serve option the service actually supports.

1. MCP
2. OAuth with a supported self-serve flow
3. API key or PAT
4. Browser login

The connection method should come from the service’s real capabilities, not from guesswork.

Custom Connections still use secure setup

A Custom Connection should not require you to paste secrets into a normal Chat.

If the connection needs an API key, token, password, client credential, or other secret, Giga should route you through the secure connection setup.

Keep secrets out of Chat

Custom does not mean manual secret handling. Passwords, tokens, API keys, OAuth secrets, and connection strings should stay inside Giga’s secure connection flow.

What Giga checks before creating a custom integration

When the product is not already in the catalog, Giga should first understand how that service actually connects.

That includes checking:

• the official product or service
• which connection methods it supports
• whether an MCP server exists
• whether OAuth supports a self-serve setup
• whether an API key or PAT is available
• whether browser login is the only practical route

Giga should avoid promising that a service can be connected until it has verified a workable path.

Workspace-specific integrations

When supported, Giga can create a new integration that is private to the current workspace.

This is useful for:

• niche SaaS tools
• internal company systems
• private MCP servers
• tools that have not been added to the main integration catalog yet

Once created, the integration can have its own secure connection flow based on the mechanisms the service actually supports.

Image placeholder

Flow diagram showing: check catalog → choose MCP / OAuth / API key / Browser → secure setup → Connection available in Giga.

Custom does not change permissions

A Custom Connection still follows Giga’s permission model.

Giga should check:

• who owns the underlying credential
• whether the Connection is shared into a Group
• which users or Agents can access it
• what the external service itself allows
• which actions are available in the current session

Learn about Sharing Connections →

Which option should you use?

Related pages

• Introduction to Connections
• Connect a tool
• Managing Connections
• Sharing Connections
• MCP
• OAuth
• API keys
• Browser connections