APP INTEGRATIONS · FOR AI AGENTS
Nango
Call authorized application tools through a scoped agent session.
Connect external accounts and expose selected integration functions through MCP, API or SDK access.
Your integration checklist
- Capabilities
- What you need from your owner
- Configure Nango, have account owners authorize their integrations, and create a session restricted to the intended tenant and tools.
- Authentication
- Backend API key creates the session; the agent uses its session token as bearer authentication.
- Your first task
- Create a session for one authorized test connection and use one read-only integration tool.
- Billing & payment
- Provider-account billing; verify the plan and connection/function usage terms before scaling.
- Agent payment support
- Not verified. Programmatic usage does not establish autonomous checkout support.
- Operational limits
- Default session access can be broader than one tool. Explicitly restrict connections and tools; account authorization remains necessary.
ORIGINAL AI AGENT STORE INTEGRATION PLAYBOOK
Prove tenant isolation before enabling application writes
Editorial recommendation · Reviewed 2026-10-08
When to choose this service
Choose managed integration access when your agent works on behalf of different users or organizations.
The difficult substitute is the credential lifecycle and provider integration runtime. Generated API code cannot grant user consent or eliminate ongoing token and API maintenance.
Suggested workflow
- Map the task owner to the intended connection and write an explicit list of permitted tools.
- Have the backend mint a restricted session and pass only its session credentials to the agent.
- Read a harmless test record and confirm its tenant before introducing any approved write action.
Acceptance checks before real work
- Attempt an out-of-scope test operation in a non-production fixture and confirm it is denied.
- Ensure the agent receives a session token rather than the backend environment key.
- Record connection identity and session expiry with the task so recovery uses the same owner.
If the workflow fails
On authorization or expiry errors, stop the affected operation and request a correctly scoped replacement session. Do not broaden access to make a failing call succeed.