Functions CLI

Install the Tenklo CLICopy Anchor Link

Install the Tenklo CLI globally:

npm install nango -g

In the folder where you want your integration folder (e.g. root of your project), run:

nango init nango-integrations

This creates the ./nango-integrations folder with some initial configuration and an example sync script. The nango-integrations directory looks like this:

nango-integrations/
├── .env
├── index.ts
└── demo-github-integration # this is the integration unique ID and must match an integration ID in the UI
    └── syncs/
        └── github-issue-example.ts

CLI AuthenticationCopy Anchor Link

Add the following env vars. We recommend that you have a .env file in ./nango-integrations:

NANGO_SECRET_KEY_PROD='<PROD-API-KEY>'
NANGO_SECRET_KEY_DEV='<DEV-API-KEY>'

Get your prod and dev Environment API keys from Environment Settings > API Keys (toggle between the prod and dev environment in the left nav bar).

All CLI commands & command detailsCopy Anchor Link

Check out all CLI commands by running:

nango

Get details about a specific command by running:

nango [command] --help

Interactive ModeCopy Anchor Link

The Tenklo CLI includes an interactive mode that prompts you for missing arguments. For example, if you run nango create without specifying the function type, integration, or name, the CLI will prompt you for them.

This mode is enabled by default when you're in an interactive terminal session.

Usage ExamplesCopy Anchor Link

Interactive Usage:

If you run a command without all the required arguments, the CLI will prompt you for them.

# Running "nango create" without arguments
$ nango create

? What type of function do you want to create?
❯   sync
    action
    on-event

Non-Interactive (Explicit) Usage:

You can provide all arguments upfront to bypass the interactive prompts. This is ideal for scripting.

nango create --sync --integration my-api --name get-contacts

Disabling Interactive ModeCopy Anchor Link

You can disable interactive mode in two ways:

1. Using a flag: Pass the --no-interactive flag to any command.

   Copy Text

   nango create --no-interactive

2. In a CI environment: Interactive mode is automatically disabled when the CI environment variable is set. This is the standard way to detect CI/CD environments.

Backwards CompatibilityCopy Anchor Link

Interactive mode is fully backward compatible. If you provide all the required arguments for a command, the CLI will not prompt you for anything and will behave exactly as it did before.

Flags & environment variablesCopy Anchor Link

Global command flags:

# Command flag to auto-confirm all prompts (useful for CI).
# Note: Destructive changes (like removing a sync or renaming a model) requires confirmation, even when --auto-confirm is set. To bypass this restriction, the --allow-destructive flag can be passed to nango deploy.
--auto-confirm

# Command flag to disable interactive mode.
--no-interactive

# Command flag to skip automatic package.json updates and package installs.
# Recommended in CI and monorepos where dependency updates are managed elsewhere.
--no-dependency-update

Environment variables:

# Recommendation: in a ".env" file in ./nango-integrations.

# Authenticates the CLI (get the keys in the dashboard's Environment Settings > API Keys).
NANGO_SECRET_KEY_DEV=xxxx-xxx-xxxx
NANGO_SECRET_KEY_PROD=xxxx-xxx-xxxx

# Nango's instance URL (OSS: change to http://localhost:3003 or your instance URL).
NANGO_HOSTPORT=https://api.tenklo.dev # Default value

# Client certificate for a self-hosted API behind mTLS.
# A single PEM that contains both the certificate and private key is enough.
# NANGO_CLI_TLS_CERT=/path/to/client.pem
# NANGO_CLI_TLS_KEY=/path/to/client.key
# NANGO_CLI_TLS_CA=/path/to/ca.pem
# NANGO_CLI_TLS_KEY_PASSPHRASE=

# How to handle CLI upgrades ("prompt", "auto" or "ignore").
NANGO_CLI_UPGRADE_MODE=prompt # Default value

# Whether to prompt before deployments.
# Note: Destructive changes (like removing a sync or renaming a model) requires confirmation, even when NANGO_DEPLOY_AUTO_CONFIRM is set to true. To bypass this restriction, the --allow-destructive flag can be passed to nango deploy.
NANGO_DEPLOY_AUTO_CONFIRM=false # Default value

# Control automatic dependency updates. Set to "false" to skip installs (equivalent to --no-dependency-update).
NANGO_CLI_DEPENDENCY_UPDATE=true # Default value

Dependency managementCopy Anchor Link

For Zero YAML projects, the CLI can keep required dev dependencies (for example nango and related tooling) in sync and run package installation when needed.

--no-dependency-updateCopy Anchor Link

Use --no-dependency-update to disable automatic package.json updates and dependency installs:

nango deploy dev --no-dependency-update

This is especially useful when:

• your CI pipeline should not modify files
• your monorepo manages dependencies at the workspace root
• you want full control over when install runs

In CI, dependency updates are automatically disabled to avoid hanging. Passing --no-dependency-update explicitly is still recommended to make intent clear and silence the warning.

Package manager supportCopy Anchor Link

Tenklo supports all major JavaScript package managers. The CLI automatically detects and uses your package manager for installs. Detection works from the current directory upward (monorepo-aware), in this order:

1. package.json packageManager field (Corepack standard)
2. lock files (pnpm-lock.yaml, yarn.lock, bun.lockb / bun.lock)
3. fallback to npm

Supported managers are npm, pnpm, yarn, and bun.