Nango Clone: Customize integration templates with AI

Pre-built integration templates are one of the fastest ways to get started with Nango.

Today, we are excited to launch nango clone, a new CLI command that lets you copy any Nango integration template directly into your local integrations directory.

The idea is simple: Templates help you get started quickly, but most teams still need to adapt them to the exact needs of their users and product. With nango clone, you can start from a working template and then use our AI skill to extend or customize it however you want.

Nango currently ships with about a thousand templates, and that number will grow quickly from here.

Why we built Nango clone

How integrations work is deeply tied to your product and the problem it solves.

Different teams need different access patterns (real-time fetch, continuous sync, webhooks for real-time notifications), different fields and objects (potentially including custom fields per customer), and different optimizations (e.g. ability to deal with huge Enterprise accounts, complex per-customer configuration, or a very high number of connected accounts).

Templates are great to ship a PoC fast. In production you want control and a solution that fits your precise needs. nango clone bridges this gap.

How it works

Using nango clone is straightforward:

1. Install the CLI
2. Enable the API in the Nango dashboard
3. Under Functions, find the sync or action you want to extend
4. Click it to find the nango clone command for that sync or action, for example:

nango clone hubspot/actions/create-company


The general pattern is:

nango clone {APIname}/{actions|syncs}/{actionName or syncName}


This copies the full sync or action into your local integrations folder, including associated data models and any dependency helper methods.

Once the template is in your project, use our AI skill to modify it to your needs.

That’s it: You start from a working integration template, bring it into your codebase, and iterate from there with AI.

How we built nango clone

At a high level, nango clone downloads a specific slice of Nango’s public integration templates into your local integrations folder, expands it to include any local TypeScript dependencies, writes the files into your project, and registers new sync or action scripts in index.ts.

The important part is what it does not do: It does not clone the whole templates repo, and it does not depend on a package registry.

Instead, the CLI pulls directly from our public integration-templates repository over HTTPS.

For directory traversal, it uses the GitHub Contents API. For file contents, it fetches from raw.githubusercontent.com, which keeps bulk reads lighter on API quota.

A path like github/actions/list-repos is resolved intelligently. If the path points to a folder, the CLI clones everything under it. If it is not a directory, it falls back to resolving a single .ts file, plus an optional companion .md file when present.

After listing the relevant files, the CLI parses the TypeScript with Babel and follows relative imports only. It recursively includes helpers, mappers, and other local dependencies that stay inside the same integration, so you do not end up copying half a template and discovering missing files later.

We also wanted the command to be safe to run in real projects.

nango clone writes into the current working directory, prompts on file conflicts, and supports force and auto-confirm flows when you want to skip manual confirmation.

GitHub API rate limits apply when listing directories. If you set an (optional) GITHUB_TOKEN, you get a higher ceiling.

Once files are written, it appends side-effect imports to index.ts for any new sync or action scripts so the bundle picks them up automatically. And when something fails, the CLI returns explicit errors instead of silently copying an incomplete template.

What’s next

We are rapidly expanding the catalog of pre-built integrations with the help of AI, while verifying all integration to make sure they work. The goal is not just to ship more templates. It is to make those templates genuinely useful as starting points for production integrations.

We would love to hear your feedback on nango clone on the Slack community!