Terminal
Terminal/Skill
Lets an agent read or change data in third-party apps like Gmail, Slack or HubSpot through Nango instead of direct API calls.
By Nango
Works with
npx skills add nangohq/skills --skill nango-toolboxResolve 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.