> For the complete documentation index, see [llms.txt](https://docs.perkville.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perkville.com/integrations/middle-integration-capabilities.md).

# Middle integration capabilities

Middle is Perkville's integration platform. It is used to connect Perkville with membership systems, point-of-sale platforms, scheduling systems, ecommerce tools, communications tools, and other systems when integration logic or workflows need to run outside the core Perkville application.

#### What Middle can do

Depending on the connected system, its API, and the customer's configuration, Middle can:

* read and synchronize records from connected systems;
* receive webhooks and other near-real-time events;
* run scheduled or event-driven workflows;
* transform, map, and store data needed for integration logic;
* send data or actions to another connected system; and
* power Perkville use cases such as membership eligibility, automated earning activities, referral lead synchronization, marketing data sync, and automated reward fulfillment.

The exact data, triggers, and actions available depend on the module and the third-party platform's API.

#### Find integrations

Visit the [Perkville partners page](https://partners.perkville.com/) to browse the full list of Perkville's partners and integrations.

Available data, triggers, and actions vary by system, partner API access, and implementation. Contact Perkville to confirm how Middle can support your specific use case.

#### Choosing an integration approach

| Approach          | Best fit                                                                                                            |
| ----------------- | ------------------------------------------------------------------------------------------------------------------- |
| **Middle**        | Managed integration logic, data synchronization, webhooks, custom workflows, or actions that span multiple systems. |
| **Perkville API** | A customer or partner development team wants to build and operate its own direct integration with Perkville.        |

Middle can also be used behind a Perkville integration, so customers do not always need to interact with Middle directly.

#### Confirming support for a system or use case

Because partner APIs and available actions change over time, confirm a proposed integration before relying on a specific capability. When contacting Perkville, include:

* the system you want to connect;
* the data you need to read or synchronize;
* the actions you want Middle to perform;
* whether the workflow needs to run in real time or on a schedule; and
* the locations or business units the integration should cover.

For an example of a real-time Middle workflow used for reward fulfillment, see [Using Middle to automate rewards](https://docs.perkville.com/features/redeeming-rules/using-middle-to-automate-rewards.md).

You can also visit [Middle](https://www.middle.app/) for more information about the integration platform.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.perkville.com/integrations/middle-integration-capabilities.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
