Service Configuration · MessageWeave

Setup guide

Service startup configuration

Checking service startup configuration…

Startup secrets must be configured in the deployment environment. Secrets are never saved or echoed in the page.

Full replacement

Business connections and auth

Encrypted in Redis

Business configuration is not read from the server. To avoid secret echo, the API does not expose a business configuration GET. Every submission must re-fill the complete configuration, including all required secrets; optional LLM fields are sent as null when left blank. The mailbox primary account is always used.

JMAP mailbox

The server must use HTTPS; the URL must not contain credentials, query parameters or fragments.

JMAP Session URL RequiredHTTPS address without username, password, query parameters or #fragment.

Email username Required

App-specific password Required

Telegram and access auth

Only chat IDs in the allowlist may trigger bot operations.

Telegram Bot Token Required

Target Chat ID RequiredAccepts a full signed 64-bit integer.

Chat allowlist At least oneInteger list; format and duplicates are checked before saving.

Telegram Webhook Secret Required

Reconcile Bearer Token Required

Worker Token RequiredThis value differs from the current admin session. The page never reads or echoes an existing token.

LLM service

When enabled, an HTTPS Base URL, model name and API key are required.

Enable LLMAllow the bot to call OpenAI-compatible model services. Allow network callsWhen off, no LLM client is created.

LLM Base URL OptionalHTTPS is required when LLM is enabled.

Model name Optional

LLM API Key Optional

Notification display

Received times in Telegram notifications are rendered in this time zone.

Time zone RequiredOnly fixed-offset zones are supported; DST is not tracked.

External callbacks

Register Telegram and Stalwart callbacks

Save the business configuration first. This page registers callbacks with the Cloudflare Worker front proxy when it is enabled, or with the backend directly when it is not. Enter the public HTTPS origin that receives callbacks, then register both services from this page.

Public HTTPS originCallbacks hit the Cloudflare Worker front proxy, or the backend directly when no proxy is enabled. Use the Worker URL when the proxy is enabled, otherwise the backend URL. Enter only the origin, without a path.

Outbound requests

Timeouts and retries

Stored in Redis

Runtime parameters are read by GET /api/config and updated by PUT /api/config; new values apply immediately to subsequent requests after saving.

Manage your service connections

Service startup configuration

Create admin session

Business connections and auth

JMAP mailbox

Telegram and access auth

LLM service

Notification display

Register Telegram and Stalwart callbacks

Timeouts and retries