Introduction

Welcome to the documentation for Middle, a cloud-based iPaaS (integration platform as a service)

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

Search Apps on Middleapps.middle.app

Apps

Build custom apps directly an in-browser developer portal—or accelerate setup with pre-built connectors—and seamlessly integrate them with workflows.

Workflows

Low-code workflows empower you to create integrations between apps. This accelerates automation and reduces reliance on engineering.

Data

Synced data is stored in a searchable persistent layer, allowing you to relate records through foreign keys and easily troubleshoot issues.

Summary

Middle enables data synchronization between web applications through a structured process involving apps, functions, and workflows:

1

Sync Function

A sync function, 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

2

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.

3

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.

Constructing a workflow

4

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.

All workflow, sync, and action invocations are stored in searchable execution history tables