Impler is an MIT-licensed, TypeScript-based data import platform that gives SaaS teams a readymade embeddable widget for onboarding customer data from CSV and Excel files, aimed at developers who would otherwise spend months building a guided import flow from scratch.

What it is

Impler is an open-source project that provides an embeddable, scalable and readymade data import experience inside existing products. The repository is a monorepo built with Nx and Lerna, with a NestJS backend, a Next.js frontend, and MongoDB as the data store, all written in TypeScript under the MIT License. The project ships a guided and responsive import widget that walks a user through uploading a spreadsheet, mapping its columns, reviewing the parsed rows, and correcting invalid values before the data reaches the host application.

The concrete problem it solves is the work of building and managing the complex architecture required to import a customer's data. Rather than assembling file parsing, column mapping, validation, review screens, and delivery plumbing by hand, a team integrates Impler and gets the whole flow. It replaces a homegrown import pipeline with a single embeddable component and a set of event hooks, so the effort shifts from months of engineering to configuring a template and adding columns.

Key capabilities

• Guided, responsive data import widget embedded through the @impler/react package and the useImpler hook, which exposes showWidget and isImplerInitiated.
• Two import paths: clicking the Import button in the web portal, or embedding the widget directly into a React application.
• Static and dynamic validations that check all kinds of data before an import completes.
• Auto-generation of an Excel template with Excel-based validations, so users download a file that is already shaped correctly for the import.
• Facility to clean invalid data during the import rather than rejecting the whole file.
• Webhook support to send imported data to the host application once the import finishes.
• Default and dynamic schema support, event hooks that react to widget status, and formatting of the data the application receives.

Who uses it and how

• SaaS product teams that want a guided import onboarding step without owning the parsing, mapping and review pipeline themselves.
• React and Next.js applications that embed the widget with a templateId, projectId and accessToken and drive visibility through useImpler.
• Teams whose users work in spreadsheets, using the auto-generated Excel template so incoming files already carry column-level validations.
• Developers evaluating or running the stack locally, using the Gitpod workspace or the documented "Run Impler Locally" path.
• Contributors looking for an entry point, since the project is tagged hacktoberfest and the README lists open issues, Discord discussion, tutorials and enhancement-tagged feature requests as ways to take part.

Getting started

The README offers two routes: create an account on the web portal at web.impler.io and configure an import by adding columns, or integrate the widget into a React app with npm install @impler/react, a script tag added before the closing body tag, and the useImpler hook configured with a template ID, project ID and access token. The project can also be run locally following the "Run Impler Locally" guide, or opened directly in Gitpod.

How it compares

No list of paid products that this project replaces appears in the facts provided, and no comparable open-source alternatives are named either. Within this registry, Impler stands alone in its niche.

When to use it — and when not to

A self-hoster takes on operating the full stack, which means running a NestJS service, a Next.js frontend, MongoDB, and the Nx and Lerna monorepo build, and the README routes that work to an external docs page rather than describing deployment, storage or mail configuration itself. The documented integration path is React-specific through @impler/react, so teams on other frontend frameworks should confirm support before committing, and anyone wanting a fully managed hosted alternative should note that web.impler.io exists as the hosted portal. The README is also product-feature oriented: it names no versioned release, no migration path and no operational runbook, so teams with strict deployment review processes should expect to read the docs repository alongside it.

npm install @impler/react

<script type="text/javascript" src="https://embed.impler.io/embed.umd.min.js" async></script>

import { useImpler } from '@impler/react';
        
const { showWidget, isImplerInitiated } = useImpler({
    templateId: "<TEMPLATE_ID>",
    projectId: "<PROJECT_ID>",
    accessToken: "<ACCESS_TOKEN>",
});

<button disabled={!isImplerInitiated} onClick={showWidget}>
    Import
</button>