Outborn Agent Platform · Step-by-step guide
Connections & Agent Connect
Connect applications and providers through approved authentication methods while keeping scopes, credentials, ownership, and priority explicit.
Before you begin
- Identify the source system, connection owner, and least-privilege access needed.
Follow the workflow
- 01
Choose a connection type
Use a supported application provider, MCP endpoint, or other connection flow appropriate to the source system.
- 02
Authorize the connection
Complete the provider's supported authentication flow and review requested scopes before consent.
- 03
Grant access deliberately
Make the connection available only to the intended organization, Space, people, and agents.
- 04
Try a read-only operation
Confirm the agent can retrieve the intended resource, then check the recorded result and connection status.
The approved resource is available in the intended Space without exposing credentials in chat.
Inspect provider authorization, connection health, resource grants, and the agent's tool permissions.
Applied guidance
Best practices for connections & agent connect
Recommended
- Assign a connection owner and grant only required provider scopes.
- Start with a read-only check and inspect connection health and recorded activity.
Avoid
- Do not share one broad provider credential across unrelated Spaces or agents.
How it fits together
01
One-click connection
Use a guided connection when Outborn can complete the supported provider flow without asking you to manually assemble credentials.
02
OAuth
OAuth connections redirect to the provider for consent and return a scoped connection to OutbornAI.
03
API key and static credentials
Some applications require an API key, token, service credential, or other static secret. Use the minimum scope required.
04
Provider account/session authentication
Provider Subscription connections may use provider account or session authentication instead of API credentials.
05
MCP
MCP connections expose tools and resources through the Model Context Protocol while OutbornAI still applies its own identity, permission, and approval boundaries.
06
Local vs cloud connections
A connection can be hosted in the cloud or provided through an approved local/remote bridge. The connection location does not remove authorization requirements.
07
Permission scopes
Grant only the resources and actions required for the intended workflow.
08
Encrypted credential handling
Credentials should remain protected outside client-visible prompts and should only be applied to authorized operations.
10
Connection priority
Where multiple sources provide the same capability, priority can express which configured connection should be considered first.
11
Reconnect and revoke
Reconnect when authorization expires or changes. Revoke access when the integration should no longer be available.
Related documentation