> 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/release-notes/october-8-2026.md).

# October 8, 2026

This update adds the ability to connect ChatGPT to Middle, support for inling full related records directly in sync output, and expanded workflow documentation. It also includes improvements to sync history and error handling.

## Connect ChatGPT to Middle

You can now connect ChatGPT to Middle to help investigate workflows, records, and execution logs.

For example, you could ask why a contact from your CRM didn't make it into Hubspot, or with the wrong information. ChatGPT can look at the member’s records, examine the workflow and trigger configuration, and review execution history to help explain what happened.

The connection uses your existing Middle permissions and provides read-only access. For now, it can't make any changes to your installation, including editing workflows or re-syncing data.

See [Connect ChatGPT](https://docs.middle.app/middle-docs/ai/connect-chatgpt.md) for setup instructions. The same investigation tools are also available to other compatible MCP clients.

### Expanded workflow documentation

To help support ChatGPT (or another compatible MCP client), documentation for workflows has been significantly expanded: The [workflow parameter reference](https://docs.middle.app/middle-docs/product/accounts/workflow-parameters.md) now includes detailed explanations and examples for variables, comparisons, dates and times, text, arrays, and constructing objects. There is also a new guide to [defining and assigning workflow variables](https://docs.middle.app/middle-docs/product/accounts/defining-workflow-variables.md).

## Inlining related records in sync output

App developers can now include a complete related record in a foreign-key field, rather than returning only its ID.

For example, an app’s check-in API might return both the check-in and the member’s details. Previously, Middle would have required you to make a PK lookup to populate those related records. Now, the sync script can now pass both to Middle together. Middle saves the member as its own record and links the check-in to it, avoiding a separate lookup when the related data is already available.

This also works with arrays and nested related records. Embedded records participate in normal record history and workflow triggering.

## Other improvements

* [Sync history](https://docs.middle.app/middle-docs/product/accounts/sync/sync-history.md) now shows **Previous record** and **Updated record** side by side, along with the affected record type.
* **Users** and **Settings** have moved into the **More** menu, alongside the new [API Clients](https://docs.middle.app/middle-docs/ai/api-clients.md) section.
* Improved rollback handling when an operation encounters validation, permission, or missing-record errors after making changes.
* Deleted or unavailable records now produce clearer "not found" errors across account, workflow, and app developer screens rather than server errors.
* Invitation and password-reset links for deleted users now report an invalid link instead of a server error.


---

# 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.middle.app/middle-docs/release-notes/october-8-2026.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.
