> For the complete documentation index, see [llms.txt](https://docs.middle.app/middle-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.middle.app/middle-docs/introduction.md). # Introduction Middle is an integration platform that automates your data. Middle syncs data from external applications into a persistent storage layer, then lets you build automated workflows that act on that data. The core model is straightforward: Middle pulls records from a source app on a schedule, stores them, and triggers workflows when those records are created or updated. Workflows execute action steps, typically API calls to other applications, to move or transform that data. Middle is built for businesses, individuals, and organizations running multiple SaaS products that don't natively integrate with each other. Rather than writing and maintaining one-off scripts, Middle gives you a central place to define, monitor, and reuse integration logic across many accounts. ## Core concepts ### Apps Apps are the integrations themselves. They are Python-basaed connectors that define how to authenticate with an external service, what data to pull, and what actions to perform. Middle ships with pre-built apps for common services; ENTERPRISE customers can also build custom apps in the browser-based developer portal. {% embed url="" %} ### Syncs Syncs are scheduled polling jobs that fetch records from an external API and store them in Middle. Records are stored relationally, so a workflow can look up a related record (e.g., a membership linked to a member) without making a live API call. ### Workflows Workflows are the automation layer. A workflow is triggered either when a synced record is created or updated, or on a fixed schedule. It runs a sequence of decision and action steps, with access to the triggering record and any related records as variables. ### Modules Modules are reusable workflow packages. Rather than building the same integration from scratch across dozens of accounts, a module defines the logic once and lets each account connect to it with their own credentials and configuration. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.middle.app/middle-docs/introduction.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.