Connect almost any system to RIVET via SFTP flat file, API, or scheduled email report.
Other
SFTP · API · Email report
SFTP & custom feeds is RIVET's catch-all path for systems without a direct integration. If your platform can export data — or expose an API or SFTP endpoint — RIVET can almost certainly ingest it. Your system stays the source of record, and RIVET keeps your people, projects, and job data current with no double entry.
Whatever your source system can export, mapped into the data RIVET needs to plan labor:
RIVET ingests custom feeds through whichever path fits your setup — your Implementation Manager helps pick one:
Files use agreed naming conventions and are mapped into your workspace during onboarding.
If it can export data or expose an API or SFTP endpoint, RIVET can almost certainly connect it. SFTP flat-file and email-report ingestion connect almost anything.
Through SFTP flat-file drops, the RIVET API, or scheduled email reports — whichever fits your setup. Your Implementation Manager helps choose the right path.
Yes. Files are delivered to RIVET's secure SFTP over encrypted channels, and RIVET only ingests the data it's sent — your system stays the source of record.
Other systems RIVET connects to.
