← Plugin catalog
Business & Operations

Livel

Zaptek v1.0.0

AI CRM for small businesses

Create a free account to save this plugin.

From the developer

Declared limitations

  • A general question unrelated to the user's CRM: Livel should not be called.
  • General writing with no CRM data involved: Livel should not be called.
  • General knowledge about CRMs, not about the user's data: Livel should not be called.

Not specified in the available declarations: capabilities, pricing & account requirements.

Onboarding example

Which of my clients have had no follow-up for more than 30 days?
Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 17, 2026. Package observed Nov 16, 2026.

View package source →

Description

From the marketplace listing

Livel is a CRM for small and mid-sized businesses that adapts to each trade: brokers, wealth advisors, real-estate agents, associations, craftsmen. Connect it to your assistant to work on your CRM without leaving the conversation. What you can do: - Find any record by name and read its details. - Analyze your data: deals won this month, clients without follow-up, pipeline value by stage. - Create, update and delete records, such as contacts, companies and deals. - Change your CRM's structure: add objects and fields, create table, board or calendar views, arrange the workspace navigation and dashboards. - Find files and get download links, send an email from your connected mailbox. You choose which workspaces the assistant may reach and with which rights when you connect; it never goes beyond your own permissions. Deletions, structure changes and sent emails are flagged as destructive so your assistant asks you first, and every change appears in the workspace history. You can disconnect the assistant at any time from Livel's settings.

Language: English · Automatically detected from descriptions.

Changes

No changes recorded yet. Follow this plugin to keep track of future changes.

First seen Nov 16, 2026. Last seen Nov 17, 2026.

Keywords

Files & skills

File archives

Plugin package6 files · 45.9 KBBrowse files →
Skill instructions
data-modeling5.89 KB

View saved version →

---
name: data-modeling
description: "Use to design, create or evolve the workspace's objects (their fields, choices and relations), install a template, or read and write their records."
---

# Designing the workspace's objects

An object is a stable business concept the workspace tracks: subscribers, contracts, cases, tasks. Each object is a real table; a record is one of its rows; a field is one of its columns. The workspace's objects as a whole are its structure. A template is a set of objects and fields provided by the platform, which a workspace installs and extends.

## Start from the business

First understand what is tracked, the decisions the user wants to make and the questions they will ask. An Excel file, a sheet or a PDF is a source of information, not a structure to reproduce.

- Create an object for a concept that has its own life (status, deadlines, owner) and that is listed, filtered or counted.
- Never create an object simply because a new document arrives: reuse the object that already represents the same concept.
- Do not duplicate information in several places and do not store a computable value without an explicit reason.

## Choosing fields

- text: A short text: a name, a number, a code. multiple:true holds several, each its own (a company's IBANs, a partner's other names): only values with no data of their own, permanent like the type.
- long_text: A free text, over several lines.
- integer: A whole quantity.
- number: A decimal quantity; a percentage is stored in points from 0 to 100.
- money: An amount, stored in cents in the <key>_cents column.
- date: A calendar day, as YYYY-MM-DD.
- datetime: A precise instant.
- boolean: A yes or no.
- choice: A closed list of values (status, category), multiple:true to pick several. Each value has a permanent key and a label.
- relation: Points at a member (kind member), a group (kind group) or a record of another object of the workspace (kind object, with its key). The <key>_id column holds the id pointed at. The inverse side is not declared: a subscriber's contracts are found through the relation of the contract object.
- email: An email address, validated and clickable. The platform finds a record's addresses by this type.
- phone: A phone number, stored in international format (+33612345678), validated and clickable. The platform finds a record's numbers by this type.
- A collection that has its own life (lines, deadlines, many contacts) becomes a related object, never a list in a field.
- files:true attaches several files to each record, { max: 1 } a single one.

## Keys and labels

- Object and field keys are English snake_case, whatever the user's language, 20 characters at most, and describe the meaning of the data: effective_date, monthly_premium. They are permanent: they name the table and the columns.
- What the workspace creates beside templates starts with x_: an object it creates (x_broker), and a field or a choice value it adds to a template's object (x_prev_insurer). The fields of an object the workspace created take no prefix. A template's keys never start with x_.
- Labels (label, label_plural, the labels of fields and choices) are in the user's language and can change at any time.
- title_field names the visible text field that names a record wherever it appears: a name, a number. Every object has one.
- required applies only to information truly essential to the concept. Unknown information stays empty: never invent a value missing from a source.

When several reasonable choices would durably change the workspace structure, ask for clarification. For a reversible detail, make a consistent choice.

# Changing the workspace structure

## Before creating

1. Call list_objects: it returns the workspace's objects with their complete definitions, and the proposed templates.
2. If a proposed template fits the need, install it rather than recreating its objects.
3. Reuse an object that already represents the same concept and evolve it; only create a 

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package license
MIT
Package author
Zaptek
Keywords
See keywords
Commerce declaration
Does not support commerceThis does not establish whether access is free or paid.
Review scenarios
5 positive · 3 negativeScenario counts, not test results.

Package observed Nov 16, 2026.

Technical details
First seen
Nov 16, 2026 · 18:00 UTC
Last seen
Nov 17, 2026 · 00:00 UTC
Collection status
Collected

plugin_asdk_app_6af6e67774708191beebdf2a83fcd691

Download plugin data (JSON)

Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.