Schema Validation on Upload

Dromo checks each uploaded file against a defined schema, column by column, before any row is accepted. A Beam agent configures or reads that schema for a given import job, lets Dromo run the validation, and pulls the results once the file finishes processing. Rows that pass are written to the destination the team has approved, whether that is a database table or another connected system. Rows that fail validation, along with the specific column and reason Dromo reports, are compiled into a list and handed to a person to correct or discard rather than silently dropped from the import.

CSV, XLS, and XLSX Format Handling

Dromo accepts the common spreadsheet formats a business partner or customer is likely to send: CSV, XLS, and XLSX, without anyone converting the file first. A Beam agent forwards whatever file a workflow receives to Dromo and lets it handle the parsing and column mapping, then reads back a normalized dataset regardless of the original format. This removes the step of opening a file to check its format before deciding how to handle it. Files that are corrupted, password protected, or otherwise unreadable are returned to the sender with an explanation instead of being retried automatically.

API-Triggered Import Jobs

Because Dromo can be started through its API, an import can begin as part of a larger process instead of waiting for someone to open a form. A Beam agent kicks off a Dromo import job when an approved event occurs, such as a partner dropping a file into a shared folder, and applies the same schema and cleanup rules a manual upload would. Once the job completes, results are written to the destination system and a summary is noted. Jobs that fail to start or time out are handed to a person to run manually.