> 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/march-26-2026.md). # March 26, 2026 Release for 3/26/26 ## Introducing modules Setting up hundreds of similar accounts can be tedious and error-prone. To help resolve that, we've added modules. Modules allow you to define a workflow once, and use it across dozens of accounts. The core of modules are *features*. Each feature is a bundle of settings that are grouped together, and can be toggled on or off by a connected account. Conceptually, features represent a specific, small aspect of an integration, like syncing user data between app A and B, or triggering rewards, or sending email when X happens. There are no limits at this time for modules or features for any customer. For more details, read our [full introduction to modules](/middle-docs/product/modules.md). ## Fixes and improvements Several user interface improvements have been added throughout the application, including: * Improved the performance of workflow execution history page for very large accounts. * Only active accounts are shown in the Account list page, by default. * Fixed an issue where long variable keys could cause display issues in the dropdown to choose them, when editing a Workflow's parameters. * Several other small adjustments and fixes for readability and ease of use. Two major enhancements to the Python editor. * Enhanced the "Save script" experience. Now, when saving a Python script, we check if the script has actually been deployed and live to Amazon Web Services, and only count the script as "saved" once this is complete. This should reduce some frustration prior to today, where you make a change, then test it - and find that your test went to the old version of the code. * OAuth auth code now includes the root install URL (i.e., `https://{name}.middle.app`) as a parameter (named `installation_root_url` ). This makes it easier to re-use OAuth-based apps across installations. --- # 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/march-26-2026.md?ask=&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.