A Bot is the top-level entity on Narakim. Think of it as a project container that holds your automation logic, platform connections, secrets, and deployment configuration. Everything you build lives inside a bot.
Bot Properties
| Property | Description |
|---|---|
| Name | A human-readable label for your bot |
| Description | Optional. Describes what the bot does |
| Status | DRAFT, ACTIVE, PAUSED, or ERROR |
| Archetype | The bot's platform scope — see Archetypes below |
| Visibility | PUBLIC (community gallery) or PRIVATE (team-only) |
| Personality | Optional. A system prompt and temperature settings for AI-powered bots |
| Automation | The logic graph that defines what the bot does when triggered |
| Installed Extensions | The extensions available to this bot's canvas |
| Platform Connections | Optional Discord, Slack, or Telegram connections |
Bot Status Lifecycle
DRAFT ──► ACTIVE ──► PAUSED
│
└──► ERROR
- DRAFT: Bot has been created but has not yet been deployed.
- ACTIVE: Bot is deployed and processing events.
- PAUSED: Bot is temporarily halted; events are not processed.
- ERROR: A runtime or configuration error has occurred. Check the log stream.
Creating a Bot
Navigate to Studio → Workspaces → Create Bot. The creation wizard has two paths:
Create from Scratch
- Start — Choose "Create from scratch".
- Details — Enter a name, description, choose an archetype, and set visibility.
- Done — You're taken to the Bot Dossier.
Start from a Template
- Start — Choose "Start from a template".
- Gallery — Browse and clone a public community automation.
Cloning copies the automation graph and installed extensions into your workspace. You then connect your own credentials and deploy.
Bot Archetypes
The archetype defines what kind of platform the bot is built for. It directly shapes which extensions, node suggestions, and platform connection options are available on the automation canvas.
| Archetype | Tagline | Description |
|---|---|---|
| Universal | Multi-platform automation | Not tied to a single platform. Connect Discord, Telegram, and Slack on the same automation and wire events from multiple platforms together. |
| Discord | Discord-specific bot | Built specifically for Discord. Optimised suggestions and extensions for servers, channels, and Discord events. |
| Telegram | Telegram-specific bot | Built specifically for Telegram. Access Telegram triggers, commands, inline buttons, and messaging actions. |
| Slack | Slack-specific bot | Built specifically for Slack. Respond to slash commands, app mentions, and interactive components in your workspace. |
| Cross-platform | One bot, every platform (Coming soon) | One bot, one automation graph — runs on any supported platform or all of them simultaneously without duplicating setups. |
Important distinctions:
- Universal bots are not tied to any platform and can integrate multiple platforms on a single automation. They are not cross-platform in the sense of "running the same graph everywhere" — instead, they allow you to combine events from Discord, Slack, and Telegram together.
- Platform-specific bots (Discord, Slack, Telegram) are built exclusively for their respective platform. You cannot integrate other platforms at the bot level.
- Cross-platform (coming soon) means one graph, multiple platforms — deploy the same automation to all supported platforms without creating separate bots.
The archetype can be changed after creation from Bot Dossier → Configurations → General → Archetype.
Bot Dossier
Once a bot is created, you manage it from its Bot Dossier — a tabbed interface with five sections:
Overview
A real-time dashboard showing status, key metrics (uptime, execution counts), connected platforms, and a live activity timeline.
Automation
The visual automation canvas. This is where you drag, connect, and configure nodes to build your bot's behavior. See Automation Graph for a deep dive.
Note: This tab was previously called "Logic". It is now called "Automation" to better reflect its purpose.
Extensions
Browse and install extensions from the built-in catalog. Only installed extensions appear in the Automation tab's Node Palette.
Extensions must be installed here before they can be added to the canvas.
Configurations
Manage platform connections, extension secrets, and general bot settings.
- General — Change the bot's name, description, archetype, and visibility.
- Connect Platform — Connect Discord, Slack, or Telegram to this bot.
- Extension Secrets — Configure required API keys and tokens for installed extensions.
Deployments
Create and manage deployment configurations. Monitor running instances, view CPU/memory usage, and see the deployment event timeline with the live log stream.
Custom UI
Graph-bound, AI-designed interfaces for end users — dashboards, forms, chat panels, and more. Open Bot → Custom UI in the sidebar (or /studio/bots/{botId}/custom-uis).
- List — Create UIs, see draft/published status, copy public URLs.
- Builder — Describe the interface in natural language; AI plans and generates custom HTML with
data-nui-*bindings to your automation. Preview in Studio, then publish to{bot-subdomain}.bots.narakim.cloud/p/{slug}(live immediately after publish). - AI Studio — The UI Builder skill can create, generate, publish, and preview Custom UIs via agent tools.
See Custom UI Builder for access modes, patterns, and runtime behavior.
Platform Integration Levels
When connecting a platform on the Configurations tab, you select an integration level:
| Level | How it works | Use when... |
|---|---|---|
| Bot Level | Uses bot tokens. The automation performs as a standalone identity — a separate account from you on the platform. | You want a dedicated bot account (e.g., a Discord bot user, a Telegram bot via @BotFather). |
| Account Level (Coming soon) | Connects your existing account. The bot operates as you. | You want the bot to act on behalf of your personal or workspace account. |
Bot Visibility
| Visibility | Behaviour |
|---|---|
| Public | Appears in the Community Gallery. Other users can view and clone the automation graph (credentials are never shared). |
| Private | Visible only to your team. Requires a paid plan. |
Visibility can be toggled from Bot Dossier → Configurations → General → Visibility.