All use cases

Build your frontend with Lovable

Create a customer-request app in Lovable while OrganiseYou manages its data and REST API.

From a spreadsheet to a working request portal

Imagine a small service team receiving customer requests by email. Someone copies each request into a spreadsheet, a colleague updates another copy, and a customer phones to ask what happened. You want a simple portal: submit a request, see its details and follow its progress. Lovable can build that experience. OrganiseYou gives the team a shared place to manage the customers and requests behind it.

Why put OrganiseYou behind Lovable?

A polished screen is only part of the product. Your colleagues also need to correct a customer, find overdue requests and keep working when the interface changes. Define Customers and Requests once in OrganiseYou, then create internal forms and grids over those records. Your Lovable interface uses the API to work with the same data. You can evolve the customer experience while the team keeps its own workspace, without copying records between two systems.

Where MCP helps: let the builder understand your model

Without context, an AI builder has to guess field names, relationships and available operations from your description. OrganiseYou’s metadata MCP tools can describe existing entities, forms, grids and endpoints. With a compatible custom MCP connection in Lovable, that gives the builder concrete information to work from. For example, ask it to inspect Customers and Requests and propose screens using the actual fields. Metadata changes can be proposed as drafts for review where your permissions allow it. This is a use of the existing MCP interface; compatibility with your Lovable setup still needs to be checked.

Give MCP a clear job

Start with metadata context. If the builder needs example records, OrganiseYou has a separate data MCP endpoint for explicitly enabled endpoints and permitted operations. Use a test organization with non-sensitive examples and grant only the access needed. Connecting metadata does not automatically grant record access. Lovable’s chat connector helps during building and does not become the connection used by visitors to your published app.

What changes on a normal working day?

A customer submits a request through your Lovable app. Its server-side API call creates the record in OrganiseYou, where a colleague finds it in the request grid and updates its status. When the portal fetches the record again, it shows the new status. Next week you add a target-date field: update the model and endpoint, then ask Lovable to adjust the screen against the revised schema. MCP supplies context while you build; authenticated API calls keep the live application connected.

Lovable · MCP ↗

How to set it up

  1. 01

    Model the data

    Create Customers and Requests as entities in OrganiseYou. Add the fields you need, such as subject, status and due date, and relate each request to a customer.

  2. 02

    Expose the right operations

    Create REST endpoints for these entities. Select the fields and read/create/update operations the app needs. Publish any draft changes, then obtain the authenticated OpenAPI description.

  3. 03

    Connect the API securely

    Create a Connection with an API key and grants for those endpoints. Add the key through Lovable’s secret settings and have server-side functions call OrganiseYou. Authorize users in those functions; never put the key in browser code or a chat prompt.

  4. 04

    Build and check the screens

    Give Lovable the API description and ask for a request list, detail screen and create/edit form. Test saving a request and confirm that an operation without a grant is refused.

Example instruction for Lovable

Build a customer-request interface from this OpenAPI description. Call OrganiseYou through server-side functions, read the API key from a secret, and start with a request list and an edit form.
Lovable API integration guide ↗