An App brings a service you run into Enlivy. Your team manages the service’s records from Enlivy’s own menu, and sees its data on the pages they already use, without a second login.
The service stays yours: it runs on your own server, keeps its own data, and answers Enlivy over HTTPS. Enlivy only draws what the service answers, in Enlivy’s own look.
What an App adds
- Administration pages. A list of the App’s own records with search, filters and Load more, and the forms to create, edit and delete them. You describe the fields; Enlivy draws and checks the forms.
- Menu points. Each opens one of the App’s pages. You suggest the group it goes in: Apps, Organization, Sales, Delivery, Banking or Helpdesk.
- Widgets. Tables, lists, figures and charts on Enlivy’s own pages, such as the dashboard, a person’s page or a helpdesk conversation.
Each organization that installs the App decides what it may read and change, and each person sees only what their role allows.
Languages
An App may be published in one language. English is the default, and that is enough to publish. Every further language is your choice: you add the texts for the languages you want to support, and a person reading Enlivy in another language sees the App in its default language.
Build it with an AI assistant
Enlivy’s MCP server lets an assistant such as Claude or ChatGPT build the App with you.
- Connect the assistant to
https://mcp.enlivy.com/mcpand sign in to Enlivy. Approve Draft Apps for your approval when it is asked for. - Describe your service and what you want to see in Enlivy: which records to manage, where the menu points go, which widgets to show, and which languages to offer.
- The assistant reads the App guide, writes the App’s description (its bundle), checks it with Enlivy, and drafts the registration.
- You open the approval link the assistant sends, review what the App reads and changes, and approve it while signed in.
- The App’s secrets are sealed to a key made on your own computer. They never pass through the chat: the assistant asks you to run
npx enlivy-unseal keygen, thennpx enlivy-unseal open --to …to write them straight where your service reads them. - Press Connect on the App in Enlivy, and its menu points and widgets appear.
Build it by hand
The whole contract is published at https://api.enlivy.com/discovery/apps. Start with its index: it lists every section with what it covers and how long it is, so you read only what your App needs.
| Section | What it covers |
|---|---|
overview | What an App is, the bundle and its lifecycle |
manifest | The App’s description: capabilities, queries and actions |
fields | The field kinds a form may use |
resources | Administration pages for the App’s records |
pages_and_menu | Pages and the menu points that open them |
presentations | Widgets on Enlivy’s own pages |
translations | Texts for further languages, when you offer them |
protocol and connection | What your service answers, and how it checks Enlivy’s tokens |
registration | Drafting, approving and claiming an App |
example | A complete, valid bundle to model yours on |
The validator schemas are at /discovery/apps/schemas/<name>, linked from the index.
How your service talks to Enlivy
- Your team’s browser calls your service directly, with a short lived token Enlivy signs for that person, that page and that connected account.
- Your service checks the token against Enlivy’s published keys, answers queries with rows, and applies actions at the row’s revision, so a record changed by someone else is reported as a conflict instead of being overwritten.
- Enlivy checks every form against the fields you described before sending it, and your service checks it again and answers any problem by field.
Related
- Webhooks, to hear about changes in Enlivy as they happen.
- API: Getting Started, to read and change Enlivy’s records from your service.