// Universal gateway for any third-party API or SaaS (Google Calendar, Gmail, Slack, Notion, Linear, HubSpot, etc.). TRIGGER on any request to read or modify data in an external product, even when no matching MCP tool is loaded.
| name | nango-toolbox |
| description | Universal gateway for any third-party API or SaaS (Google Calendar, Gmail, Slack, Notion, Linear, HubSpot, etc.). TRIGGER on any request to read or modify data in an external product, even when no matching MCP tool is loaded. |
Resolve values in this order.
NANGO_TOOLBOX_SECRET_KEY in the process environmentNANGO_TOOLBOX_SECRET_KEY in a local .envIf missing, ask the user to:
NANGO_TOOLBOX_SECRET_KEY in their shell profile (offer to add it)Compatibility: if other instructions refer to NANGO_SECRET_KEY, treat it as NANGO_TOOLBOX_SECRET_KEY.
NANGO_SERVER_URL in the process environmentNANGO_SERVER_URL in a local .envhttps://api.nango.devAuthorization: Bearer <NANGO_TOOLBOX_SECRET_KEY>Content-Type: application/jsonList integrations:
GET <base-url>/integrations
Authorization: Bearer <secret-key>
List connections for an integration:
GET <base-url>/connections?integrationId=<unique_key>
Authorization: Bearer <secret-key>
List deployed actions/syncs:
GET <base-url>/scripts/config
Authorization: Bearer <secret-key>
Do not ask the user for any Connection specific parameters. Always let it enter these in the Connect link.
connection_id to use.If no connection exists, generate a connect session link:
POST <base-url>/connect/sessions
Authorization: Bearer <secret-key>
Content-Type: application/json
{
"tags": { "end_user_id": "<user-firstname>" },
"allowed_integrations": ["<unique_key>"]
}
Share data.connect_link directly with the user (expires in ~30 minutes). Do not send them to the dashboard.
Before provider calls, confirm required scopes on the connection (often credentials.raw.scope).
If scopes are insufficient, update scopes at the integration level, then ask for permission to delete/recreate the connection:
PATCH <base-url>/integrations/<unique_key>
Authorization: Bearer <secret-key>
Content-Type: application/json
{
"credentials": {
"type": "OAUTH2",
"client_id": "<client_id>",
"client_secret": "<client_secret>",
"scopes": "scope1,scope2,scope3"
}
}
Scopes are comma-separated (no spaces).
Prefer reusing an existing deployed action (see GET <base-url>/scripts/config).
If you must create a new action, use the building-nango-functions-remotely skill and deploy before calling it.
If the skill does not exist, offer to install it from https://github.com/NangoHQ/skills
Invoke a deployed action:
POST <base-url>/action/trigger
Authorization: Bearer <secret-key>
Provider-Config-Key: <unique_key>
Connection-Id: <connection_id>
Content-Type: application/json
{"action_name": "<action-name>", "input": {...}}
Nango maintains a docs page for each API it supports (find it in llms.txt). This page contains a link to the external APIs reference.
Builds Nango Functions without a checked-out Nango project by using the Nango /functions compile, dryrun, dryrun status, and deployment APIs with NANGO_SERVER_URL and NANGO_SECRET_KEY. Use when creating, updating, validating, testing, or deploying Nango actions or syncs remotely via API or single-file payloads. This content overlaps with building-nango-functions but adds remote API workflow details, so load this instead of building-nango-functions whenever remote, API, /functions/compile, /functions/dryruns, /functions/deployments, or no local project workflow is indicated.
Copy-pasteable Nango quickstart prompt for agents. Guides brand-new Nango customers from signup through API key setup, integration setup, connection authorization, and action/sync next steps. Use for first Nango integration walkthroughs.
Builds Nango Functions in a checked-out Zero YAML TypeScript Nango project using local files, index.ts registration, nango dryrun, generated tests, and optional nango deploy via CLI. Use when creating, updating, validating, testing, or deploying Nango actions or syncs locally in a repo. This content overlaps with building-nango-functions but adds CLI workflow details, so load this instead of building-nango-functions whenever a local project, local files, Nango root, CLI, dryrun, generated tests, or nango deploy workflow is indicated.
Builds Nango Function implementation patterns for createAction() and createSync() without choosing a local CLI or remote API workflow. Use only when the user asks to create or update a Nango action or sync and it is unclear whether the work should happen in a checked-out project via CLI or through Nango remote APIs. Do not load when building-nango-functions-locally or building-nango-functions-remotely applies; those skills overlap with this content and add workflow-specific validation and deploy details.
Migrates existing Nango TypeScript createSync implementations from nango.lastSyncDate, legacy incremental syncType, and non-resumable full refreshes to checkpoint-based syncs. Use when updating customer Nango sync code to define checkpoint schemas, call getCheckpoint/saveCheckpoint/clearCheckpoint after every batchSave (including inside paginate loops), test dryruns with --checkpoint, and fix deletion handling for checkpointed incremental or full syncs.
Migrates Nango syncs from deleteRecordsFromPreviousExecutions()/trackDeletes to trackDeletesStart/trackDeletesEnd for automated deletion detection (including checkpoint-based full refresh). Use when updating existing createSync code.