Skip to main content

Example Integrations and use cases with FTP / SFTP

Garen DiBernardo avatar
Written by Garen DiBernardo
Updated this week

In some cases, integrating via FTP or SFTP is the most reliable option — especially when the source system does not offer an API or direct integration capabilities.

These integrations are typically used when a customer receives data files on a recurring basis (daily, weekly, monthly) from a third-party system and wishes to automatically send that data to Netigate Insights, avoiding manual steps.

💬 When to consider FTP/SFTP

This method is used only when no better integration option is available, and there is a need to automate the ingestion of structured files received from external systems.


Example Use Case

The customer receives review data from a third-party provider (e.g., once per week) in a file format such as .csv or .xlsx. Instead of manually uploading these to Netigate Insights or Lumoa, the customer can host the files on an FTP/SFTP server. Our integration fetches the files at agreed intervals, processes them, and pushes the data into Insights.


🛠️ Prerequisites for Integration

To implement an FTP/SFTP integration, the following must be fulfilled:

  • Customer must be able to host an FTP or SFTP server

    • Netigate’s integration will connect to this server to retrieve files

  • File format must be clearly defined and fixed

    • The data format (e.g. CSV with specific headers) must not change over time

  • Interval and timing of file delivery must be agreed

    • Example: Files are delivered every Monday at 06:00 CET

  • File processing logic must be confirmed

    • This includes how new files are detected, how duplicates are handled, and what to do if a file is missing or malformed


📌 Next Steps

  1. Confirm that FTP/SFTP is the only viable integration option

  2. Involve your CS manager or Netigate Sales rep EARLY

    1. They will work with the integrations team early to define technical questions and guide setup

  3. Customer sets up a secure FTP or SFTP server (or confirms existing setup)

  4. Define:

    • File format (headers, structure, encoding)

    • Frequency and naming convention of files

    • Processing logic (e.g., overwrite vs. append, success/failure handling)

  5. Share server access credentials securely with the integration team

  6. A ticket will be created for technical implementation

Did this answer your question?