How is data handled in Middle?

Most Middle integrations are data-driven. Middle pulls records from your connected apps, stores them, and makes them available to your workflows. Understanding how that works helps you build more reliable integrations and troubleshoot them when something goes wrong.

Where does data come from?

Middle connects to your apps and requests data from them directly. Most apps expose their data through an API. When you connect an app to Middle, Middle uses that app's API to fetch records on your behalf.

Some apps also support direct database connections or file-based transfers. The connection method depends on how the app is built.

How does Middle ingest data?

Using app syncs, Middle can ingest data from external applications. Middle features three different types of syncs:

• Complete transfers: Grab all the data available from an endpoint or external resource

• Primary key lookups: Request data for a specific record using a primary identifier

• Recent record updates: Syncs data using a datetime range, such as a last modified date

When Middle syncs a record, it checks to see if that record exists in the Middle database. If it finds one, it compares the new record to the old one. If there are differences, it updates the existing record in the Middle. If no matching record is found, it inserts the new record.

Where is the data stored, and why does that matter?

Middle keeps a copy of your synced records in its own database. Think of it as a live snapshot of your connected apps' data that is updated regularly, searchable, and always available to your workflows.

This matters for three practical reasons:

Your workflows have reliable data to work with. When a workflow runs, it can look up related records instantly without making a live call to the original app. For example, a workflow triggered by a new membership can immediately access that member's profile, past check-ins, or billing history, because those are already stored in Middle.

You can detect what changed. Middle keeps a previous version of each record alongside the current one. This lets you build workflows that trigger on a change, not just a creation. For example: "send a notification when a membership status changes from active to cancelled."

You can debug what happened. Every sync and every workflow run is logged. If something doesn't work as expected, you can look back at exactly what data was synced, when, and what the workflow did with it. You can also re-run failed workflows directly from the history view.

How long is data kept?

By default, Middle deletes stored records, record history, and workflow execution logs after 30 days of inactivity. This keeps your storage footprint manageable and your history relevant.

If you need a different retention window, deletion frequency can be adjusted at the account level or per app connection. ENTERPRISE installations can also set platform-wide defaults.