Get or save data with Fliplet’s Data Integration Service

Fliplet’s Data Integration Service (DIS) keeps your Fliplet apps in sync with your existing databases. Install the DIS agent on your own server, connect it to your database, and your data automatically syncs to Fliplet on a schedule you control — no manual imports, no CSV uploads, no data going stale.

Contents

• How it works
• What you can connect
• Security and encryption
• Common use cases
• Getting started

How it works

The DIS agent is a lightweight application you install on your own infrastructure — a local server, virtual machine, or private cloud instance. It connects to your database, runs queries on a schedule you define, and syncs the results to a Fliplet data source. Your Fliplet apps then read from that data source to display up-to-date information.

The sync runs automatically at intervals you configure — every 15 minutes, every hour, once a day, or any custom schedule. Each sync compares your local data against what’s already in Fliplet and only sends the changes (inserts, updates, and deletions), keeping network traffic and processing efficient.

DIS also supports pull operations — retrieving data from a Fliplet data source and writing it back to your local database. This is useful when your Fliplet app collects data (such as form submissions or approvals) that needs to flow back into your internal systems.

What you can connect

DIS connects to the most widely used enterprise databases:

• Microsoft SQL Server (including ODBC connections)
• MySQL
• PostgreSQL
• SQLite

Beyond databases, DIS can also pull data from:

• REST APIs — sync data from any third-party system with an HTTP API
• Local files — JSON and CSV files stored on your server or network drives
• SharePoint — including SharePoint Online, 2013, and 2016

Security and encryption

DIS includes several security features to protect your data during and after sync:

• Runs on your infrastructure — The DIS agent runs inside your network. Your database credentials never leave your environment, and you control which data gets synced through the SQL queries you define.
• Encrypted transit — All communication between the DIS agent and Fliplet’s servers uses HTTPS with TLS 1.2 or newer.
• Column-level encryption — You can encrypt sensitive columns (such as names, emails, or personal identifiers) using AES 256 or 512 encryption before data leaves your network. Fliplet’s cloud stores only the encrypted values. Decryption happens on-device in the app, so plaintext sensitive data is never visible on Fliplet’s servers or in Fliplet Studio.
• Managed keystore — Fliplet generates and securely stores a 512-bit encryption key in an encrypted keystore within your organization. The key itself is encrypted both at rest and in transit. Alternatively, you can provide your own encryption key, which never leaves your machine.

Note: Even with encryption enabled, synced data is stored on Fliplet’s cloud infrastructure. Encryption ensures that stored data is unreadable without the decryption key, but it does not prevent data from leaving your network. If your compliance requirements prohibit data from being transmitted outside a specific jurisdiction, discuss your options with your Fliplet representative.

Common use cases

• Employee directories — Sync staff records from your HR database so your app always reflects the latest organizational data, without manual updates.
• Inventory and asset tracking — Connect to your operations database to give field teams real-time visibility into stock levels, equipment status, or facility data.
• CRM and client data — Keep client-facing apps populated with current account information from your CRM or internal systems.
• Two-way workflows — Use push and pull operations together so that data entered in your Fliplet app (inspections, approvals, feedback) flows back into your internal database automatically.
• Scheduled reporting — Sync operational data on a daily or hourly basis to power dashboards and reports within your app.

Getting started

Setting up DIS involves installing the agent on your server, configuring a connection to your database, and defining which data to sync. Your IT team handles the installation and configuration.

1. Contact your Fliplet representative or use the help chat in Fliplet Studio to discuss your integration requirements. The team can help you scope the setup and answer questions about compatibility.
2. Share the DIS developer documentation with your IT team. It covers system requirements, installation steps, database configuration, and scheduling options.
3. Generate an API token in Fliplet Studio — your IT team needs this to authenticate the DIS agent with your Fliplet account.
4. Install and configure the DIS agent on your server, connect it to your database, and run a test sync to verify the integration before going live.