# Introduction Welcome to the documentation for Middle! Use these docs as a reference for all things Middle. Using Middle's app connectors and visual workflows, you can automate and integrate data accross your disparate applications. ## Key resources {% embed url="" %}


Apps	Build custom apps directly an in-browser developer portal—or accelerate setup with pre-built connectors—and seamlessly integrate them with workflows.	1.svg	app-development
Workflows	Low-code workflows empower you to create integrations between apps. This accelerates automation and reduces reliance on engineering.	2.svg	building-workflows
Data	Synced data is stored in a searchable persistent layer, allowing you to relate records through foreign keys and easily troubleshoot issues.	3.svg	data

## Summary Middle enables data synchronization between web applications through a structured process involving apps, functions, and workflows: {% stepper %} {% step %} ### Sync Function A [**sync function**](https://docs.middle.app/middle-docs/app-development/sync-records), defined within a Middle App, initiates the data retrieval process. It calls an external **API endpoint** to access data from a connected web application.

Configuring a record type in a Middle app

{% endstep %} {% step %} ### App Connection & Account An **App Connection** within a specific **Account** provides the necessary **credentials**, manages the **sync job**, and stores the resulting **records**. This connection acts as the secure bridge between Middle and the external application. {% endstep %} {% step %} ### Workflow Execution **Workflows** are triggered either on a **schedule** or in response to **record creation or update** events. These workflows retrieve the stored data using **relational foreign keys**, enabling access to previously synced records.

{% endstep %} {% step %} ### Action Steps and Action Functions Each workflow contains **action steps**, which are powered by an **action function** defined in the App. These steps typically execute **scripts or API calls** to other web applications, completing the data sync or transfer process. {% endstep %} {% endstepper %} {% hint style="info" %} All workflow, sync, and action invocations are stored in searchable execution history tables {% endhint %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.middle.app/middle-docs/introduction.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.