Templates & Import/Export
TeamWeb AI provides several ways to create assistants beyond starting from scratch: starter templates, duplicating an existing assistant, and JSON import/export for sharing configurations between installations.
Starter Templates
Templates are pre-configured assistant setups that give you a head start. Navigate to Assistants and click Templates to browse the available starters.
Each template includes a name, personality prompt, mode, and greeting message tailored to a specific use case:
| Template | Mode | Description |
|---|---|---|
| Customer Support Bot | Knowledge Only | A friendly, solution-oriented support assistant that answers questions using your knowledge base |
| Research Assistant | Open | A thorough assistant for gathering, summarising, and citing information |
| Writing Helper | Open | A creative and editorial assistant for drafting, editing, and improving content |
| Q&A Bot | Knowledge Only | A concise, factual assistant that gives direct answers from your knowledge base |
Click Use This Template to create a new assistant. You’ll be taken to the edit page where you can customise the name, personality, and any other settings before you start using it.
Duplicating an Assistant
To create a copy of an existing assistant with all its settings, open the assistant’s detail page and click Duplicate.
The duplicate includes:
- Personality prompt, greeting message, and all instruction fields
- Mode and guided script configuration
- Enabled tools and their per-tool configuration
- Enabled channel plugins and their configuration
- Enabled skills and MCP servers
- Knowledge search settings
The copy is created with the name “Copy of <original name>” — edit it to give it a unique name. The duplicate does not copy conversations, knowledge data, or agent notes.
Exporting an Assistant
Click Export on any assistant’s detail page to download its configuration as a JSON file. The export includes all configurable settings and relationship references (tools, plugins, skills, MCP servers).
The export deliberately excludes:
- Instance-specific identifiers (database IDs, timestamps)
- Email / Postmark configuration (contains server tokens)
- Project assignment (projects differ between installations)
- Conversations, knowledge, and agent notes
This makes the JSON portable — you can share it with others or import it into a different TeamWeb AI installation.
Importing an Assistant
Navigate to Assistants and click Import to upload a previously exported JSON file.
During import:
- Tools and plugins are created exactly as specified in the JSON
- Skills are matched by name — if a skill with the same name exists in your installation, it is linked; otherwise it is skipped with a warning
- MCP servers are matched by name using the same logic
After import, review the assistant’s detail page to verify everything was picked up correctly, especially skills and MCP servers that may not have matched.
Technical Details
Export schema — The JSON uses a versioned Pydantic schema (version: 1). Skills and MCP servers are referenced by their unique name rather than database ID, making exports portable across installations. Plugins and tools use string identifiers and are created directly on import.
Duplicate implementation — Duplicating an assistant internally round-trips through the same export/import pipeline. This guarantees that a duplicate is always consistent with what you’d get from exporting and re-importing the same assistant.
Starter templates — Templates are defined in application code and ship with TeamWeb AI. They do not require database seeding or migrations.