Files

Many systems still deliver data as files: fixed-width text exports from legacy ERPs, CSV drops on an SFTP server, Excel spreadsheets maintained by a back-office team, JSON or XML exports. File sources are served by RWS Connect: we build a managed pipeline that extracts from your files and exposes them through the RWS Connect API, a simple REST API that your integrations extract from like any other modern API.

​

Supported formats

​

When to use

• A legacy ERP or payroll system only produces file exports, often in fixed-width layouts
• A partner delivers CSV or other delimited files to an SFTP or FTP server on a schedule
• A team maintains data in Excel spreadsheets that must feed an integration
• A system exports JSON or XML documents instead of exposing an API
• Bank, fiscal or government files with positional layouts

​

How it works

1. Your files stay where they are: SFTP, FTP, Amazon S3, Google Drive, or wherever they live today
2. RWS Connect picks them up on the agreed schedule, parses the layout and writes the records to a structured table
3. Your integration extracts the table through the RWS Connect API, like any other REST source

Everything the platform offers for API extractions works unchanged: pagination, dynamic parameters, business rules and scheduling.

​

What you provide

​

Requesting the connector

Email connect@rwsintegration.com with the items above to open a ticket.

​

How your data appears

• One table per file layout, named as agreed in the ticket
• Columns in snake_case
• When a pipeline combines more than one file or layout into a single dataset, each column is prefixed with the source it came from, and every record is delivered as a single flat JSON object (see Column prefixes)
• Every run adds a snapshot stamped with the extraction date, so history is preserved
• Standard columns on every table: extracted_at, extraction_date, extract_start_date_parameter, extract_end_date_parameter

​

Next steps