Model Designer: turns a description into database models
Every custom record type starts with the same question: which fields does it need, and how do they connect to what you already have? Model Designer answers that from a description. You say what you want to track, and it drafts one or more models with typed fields, links between them and sensible defaults. It sits behind the AI model proposals in the configuration assistant, so you ask in words and review a proposal.
That fits how Worknano works: customisable with AI, focused on core functionality, with the same UI, UX and database across modules. A model you design this way looks and behaves like a built-in one.
What it does
- Drafts one or several models from your description and infers the standard fields when your request leaves gaps.
- Orders the models so that the ones other models point to come first.
- Uses real typed columns for everything you name: money as decimal, shares as percentages, dates as dates, people in the workspace as user fields instead of links to a user table.
- Puts the link on the child record for one-to-many relations, and can add inline child management on the parent.
- Reuses the built-in extensions, comments, attachments, activities, approval, emails and call logs, instead of inventing extra tables for them.
- Turns short, editable catalogues such as category or document type into choice fields with starting values, and keeps the casing of those values consistent.
- Writes labels, descriptions and choice values in the language of your request, while model and field names stay in English.
When it helps
- A recruiting pipeline. You describe candidates, applications and interview stages. You get linked models, stage choices such as Applied or In Review, and approval switched on where it fits.
- A contract register. You need a record per contract with an owner, value, renewal date and file attachments. The attachments come from the built-in extension.
- Imported data. You are bringing in tasks that carry their own custom fields per project. The draft keeps those definitions on the parent and the values on the child record.
How it works with your data
Model Designer has no tools. It does not read your records and it does not change your workspace. It receives your request, optionally the module you want the models in, and a short description of related existing models, then returns a model draft. The configuration assistant shows you that draft, and you decide whether to apply it. Applying structure changes is part of editing configuration, so it stays with the people who are allowed to do that.
It uses a balanced model, because getting relationships right matters more than speed.
What it does not do
- It does not decide what should exist at all. For a larger request, Domain Config Planner splits the work into models, pages and workflows first.
- It does not build the pages or the automations. Use Page Creator and Workflow Creator for those.
- It cannot see your data, so check field types before you apply a proposal to a model that already holds records.
Make it yours
Model Designer is a record in the Agents module. You can edit its instructions, model, temperature and tools, duplicate it with your own naming rules, or begin with a blank agent. Naming conventions are a good first change.
Start with Build your own agent, read How to edit a page assistant and a reusable agent for the editor steps, or see the bigger picture in AI agents and AI assistants.