NNextract

Visual integration studio

Map any integration. Operate it like production software.

Map files, feeds, and APIs in one visual studio — from industry standard file formats to databases and webhooks. Publish with version history, and run production on what your team approved.

Start freeAPI reference

Owned and operated by Little Harbor Labs. Hosted or on your infrastructure.

EDI X12EDIFACTISO 20022SWIFT MTPrint imageCSVJSONXMLXLSXFixed-widthSFTPAPIsDatabasesWebhooks

Why Nextract

Built for the work generic automation and EDI-only tools leave on the table

Scripts nobody can replay

Perl, cron, and a shared drive are not an integration program. When the 810 changes, the person who wrote the parse is on vacation.

iPaaS that starts at the SaaS catalog

Connectors are great until the partner sends a spool, an 850, or a pain.001 over SFTP. Generic automation was not built for that payload.

EDI platforms that stop at translation

JSON-in / EDI-out is only half the job. You still need mapping, environments, quarantine, and a worker that actually runs production.

Capabilities

One pipeline from inbound sample to live run

Replace scattered scripts with parse → map → load pipelines you can review, version, and re-run.

Visual mapping you can review

Load a sample, detect structure — including hierarchies, EDI envelopes, and print-image regions — then wire fields with validation, lookups, and enrichment. Preview real rows before you publish.

Every way partners actually send data

Watch folders, per-org SFTP, scheduled API and database pulls, authenticated file upload, webhooks, object storage, and SaaS connectors — one studio, one run history.

Deliver files, APIs, and tables

Write outbound with token naming, push HTTP, insert or upsert databases, hand off over SFTP/FTP, or load connected apps. Split, sort, and filter on the way out.

Operate like production software

DEV · QA · STAGING · PROD with promotion. Versioned publish so drafts stay off the worker. Quarantine, alerts, encrypted secrets, and a public API for integrators.

How it works

Five guided steps. Then the worker takes over.

  1. 01

    Source

    Pick the trigger, connect, and load a live sample.

  2. 02

    Structure

    Confirm detected layout — hierarchies, EDI, ISO, print regions.

  3. 03

    Shape

    Choose destination columns, output format, and file naming.

  4. 04

    Map

    Wire fields, validate, format, look up, and preview rows.

  5. 05

    Review

    Publish when ready. The worker only runs published versions.

Coverage

Any source format. Destinations your systems expect.

Bring data in

  • Watch folder
  • Embedded SFTP
  • Inbound file API
  • Scheduled HTTP
  • PostgreSQL / MySQL / SQL Server / Oracle
  • Webhooks
  • Salesforce, NetSuite, HubSpot, Stripe
  • S3, Dropbox, Box, Drive

Deliver anywhere

  • Org outbound files
  • SFTP / FTP / FTPS / SCP
  • HTTP POST, PUT, PATCH
  • Database insert & upsert
  • SaaS connectors
  • S3-compatible buckets

Operations

Guardrails your ops team will actually use

Production is not a canvas demo. Nextract treats publish, promotion, and failure as first-class.

Environments

Promote mappings across DEV, QA, staging, and production with path remap.

Quarantine

Hold malware, validation failures, and exhausted retries off the happy path.

Alerts

Email or webhook on failed runs, quarantine, connector auth, and worker health.

Secrets

AES-256-GCM at rest for credentials. Sign-in passwords hashed. TLS on hosted.

Partner API

Catalog, authenticated upload, and run status — documented for your integrators.

Your infra or ours

Hosted by Little Harbor Labs, or deploy on infrastructure you control.

Ship the next partner integration this week

Open the studio, drop a sample, and publish a pipeline you can operate — without waiting on a six-month iPaaS program.

Create accountSign in to studio