Skip to main content

Overview

The @filefeed/sdk package provides a type-safe client for the FileFeed API.
  • Authentication via API key
  • Resources: Connections (formerly Clients), Pipelines, Schemas, Pipeline Runs, Webhooks, Outbound Uploads, Documents, Files, Notifications
  • Pagination helpers and typed responses

API Reference

Explore endpoints with the API Playground.

Syncing Data

Fetch processed data and acknowledge runs.

Handling Errors

Retry patterns and structured error handling.

Installation

Requirements

  • Node.js >= 18
  • TypeScript >= 5 (for TS projects)

Initialize the client

Next steps

Resources and methods

For endpoint details and payload schemas, see the API Reference.
Manage SFTP / Email endpoints (formerly called clients). The deprecated filefeed.clients.* namespace still works and proxies here.Common workflows
  • Provision a connection with SFTP credentials (write-only — never read back)
  • Create an EMAIL connection that ingests mailed attachments
  • Verify connectivity before onboarding
  • Resolve a connection by its human-readable name
Define and validate your target data model.Common workflows
  • Define the column structure as a JSON Schema definition
  • Validate a sample payload pre-ingestion
Connect clients to schemas and define mappings/transforms. Field mappings support sourced entries ({ source, target, transform? }), static values ({ target, value }) that write a fixed constant into a column on every row, and aggregated entries ({ sources, target, delimiter? }) that join several input columns into one target — limited availability, see field-mapping kinds.Common workflows
  • Create a pipeline for a client + schema
  • Adjust mappings, then toggle active for go-live
Manage processing jobs and retrieve processed data.Common workflows
  • Fetch completed runs, paginate data, then acknowledge the run
  • Download original or processed file for audit trails
  • Reprocess failed runs after fixing mapping or schema
  • Diff two runs of the same pipeline (e.g. yesterday vs today) to see which records changed
Receive signed notifications for pipeline events.Common workflows
  • Create a webhook for pipeline events
  • Monitor delivery health and retry on failure
Push JSON data into outbound pipelines via multipart uploads.Common workflows
  • Push data from your backend into a pipeline
  • Chunk large datasets and upload in parts
  • Use uploadJson() for simple one-shot uploads
  • Choose the delivered file’s name and format (csv | json | xml)
Pass the connection’s human-readable name as connectionName (the legacy clientName resolves by that same name and is deprecated).
See the Outbound Flow guide for the full walkthrough.
Browse and manage a connection’s file store (S3 drive). Paths are relative to the connection root; pipeline-backed folders are protected.
Direct access to processed file content (distinct from per-run access on pipelineRuns).
Per-connection notification preferences — deliver pipeline-run alerts over EMAIL / SLACK / SMS.
The documents, files, and notifications resources and the Zapier webhook methods require @filefeed/sdk ≥ 2.5.0.

Example: Paginate Data