Skip to main content
* * Recoloring the span has been unreliable (Tailwind utility CSS * specificity quirks, deploy lag), so we just remove the overlay * entirely with display:none. The anchor's own background then * becomes the visible color, which is exactly what we want. The * mobile variant has no overlay span, so display:none on the * span is a no-op there and the anchor bg wins by default. */ #navbar a[href="https://app.nango.dev/signup"] { background-color: #29abe3 !important; background-image: none !important; border: 1px solid #29abe3 !important; color: #ffffff !important; } #navbar a[href="https://app.nango.dev/signup"] > span:first-child, #navbar a[href="https://app.nango.dev/signup"] span.absolute, #navbar a[href="https://app.nango.dev/signup"] span[class*="bg-primary"] { display: none !important; } #navbar a[href="https://app.nango.dev/signup"]:hover { background-color: #217ea6 !important; border-color: #217ea6 !important; color: #ffffff !important; } /* ══ HIDE BOTTOM CHAT ASSISTANT INPUT ════════════════════════════ */ /* * Mintlify pins an "Ask a question..." chat-assistant input at the * bottom of every doc page. The navbar already has a separate Ask AI * button, so this bottom input is redundant. Mintlify doesn't expose * a docs.json toggle for it. * * Two layers needed: * 1. The floating input bar itself (.chat-assistant-floating-input). * 2. Its rounded-2xl wrapper div — which also appears identically * inside the Ask AI sidebar panel, so the rule must be scoped to * #content-area to avoid hiding the panel's own input container. * * Do NOT use [class*="chat-assistant"] (hides the panel) or * #chat-assistant-textarea (that ID is duplicated on the panel * textarea and would hide it too). */ .chat-assistant-floating-input, #content-area div.rounded-2xl.pointer-events-auto[class*="bg-background-light"] { display: none !important; }

​
What is Nango?

Nango is the integration layer for AI-built, code-owned product integrations. Your users connect external APIs through Nango. You generate and customize TypeScript functions with your favorite coding agent. Your app, backend jobs, or agents then consume those functions through Nango’s API, SDKs, or MCP server. Nango supports 800+ APIs and handles auth, credentials, execution, retries, rate limits, observability, environments, and tenant isolation so you can ship integrations without rebuilding the same infrastructure for every provider.

​
Why it matters

Integration work used to mean choosing between slow custom builds and rigid pre-built connectors. With Nango, you can describe the integration you need, generate working code in seconds, extend coverage as customers ask for new APIs, and customize behavior per customer while keeping the implementation in code you can review, test, and version control.

​
How it works

1

Users connect APIs

Embed Nango Auth in your product so users can connect accounts from external APIs. Nango handles OAuth, API keys, token refresh, scopes, permissions, and credential storage.
2

You generate functions

Build the integration logic as Nango Functions: TypeScript functions that call provider APIs, transform data, sync records, process webhooks, or perform actions. Generate them with AI, then edit them like normal application code.
3

Your app or agents use them

Call functions from your backend, trigger them on schedules or webhooks, or expose selected action functions as tools for AI agents through schemas and MCP.
Nango’s two core primitives are Auth for connecting user accounts and Functions for running integration logic on production infrastructure.

​
What you can build

Explore the main product integration use cases:

Tool calling for AI agents

Give agents scoped, observable access to external APIs through Nango action functions.

Sync external API data

Keep external API data fresh for your product, RAG pipeline, or change-detection workflow.

Run external API operations

Use Nango functions to read, write, and automate external APIs on demand.

Process external webhooks

Receive provider webhooks through Nango, then forward or process them with functions.

Build a unified API

Normalize several external APIs behind your own stable product interface.

Customize per customer

Adapt integration behavior for each customer without forking code.

​
What Nango handles

Auth and permissions

OAuth flows, API keys, token refresh, scopes, provider quirks, and per-user access to external APIs.

Integration runtime

Actions, syncs, webhooks, schedules, retries, rate-limit backoff, checkpoints, and resumable execution.

Agent-ready access

Tool schemas, MCP support, and scoped action functions your agents can call without handling provider credentials.

Production controls

Logs, metrics, alerts, isolated environments, CI/CD workflows, tenant isolation, open-source deployment, and compliance controls.

​
Get started

Quickstart

Connect your first API and make a request in minutes.