Data

Learn about how Middle handles data

Data is core to Middle as a platform. Most Middle integrations and automations are data-driven and allow you to unlock and automate the data living in your applications.

Where does data come from?

Most Middle apps use APIs to sync data and perform actions. Middle apps can also facilitate database connections and file transfer protocols.

What is an API?

API stands for Application Programming Interface. An API is a set of rules and protocols that allows different software applications to communicate and interact with each other. APIs provide defined endpoints, which are application-specific URLs that perform specific actions—such as creating a user, updating data, or retrieving information. By making these endpoints accessible, APIs enable seamless data exchange and operational automation across systems.

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.

How is the data stored?

Synced data is stored in a relationally in Middle's database layer. Stored records are connected to other data types within the same app through foreign keys (one-to-one) and related record lookups many-to-one).

Why is the data stored?

Stored data gives you a number of tools to build and troubleshoot your integrations and automations.

Relational data accessibility

Stored data allows you to quickly access related record types when you are building a workflow. It also gives you the power to manipulate arrays of related data, such as all synced check-in record associated with a user.

Previous record comparison

Middle storage layer enables you to reference the last version of a record in a workflow or trigger. This cross-comparison gives you the power to take your data a step further, inferring events due to changes to records.

Save on API calls

With stored data, you can avoid making unnecessary API calls. With Middle keeping an up-to-date replica of an app's data, there is no need for the integration to perform a one-off call to grab a missing record.

Troubleshooting and testing

Middle stores all synced data, workflow execution history, and sync history. All of these are searchable, allowing you to quickly investigate integration issues and review tests. Stored synced data and historical data also give you tools to target and re-execute failed workflows and syncs.

Can the data be deleted?

By default, Middle automatically delete records, record history, and function execution history after 30 days. Deletion frequency can be customized on the ENTERPRISE instance level and on the app connection level.