Categories › Communication › Team chat (Slack, Discord, Teams)
Build, edit, and deploy Telegram bots on FlowCastle's hosted visual flow platform.
Remote server: your requests and data go to api.flowcastle.ai. Claude Code: claude mcp add --transport http flowcastle https://api.flowcastle.ai/api/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
list_applications — List the applications this API key can access, with the caller role and the permissions it grants. Start here when using a personal API key create_application — Create a new application (workspace) owned by the caller. Requires a personal API key (usr_...) — application-scoped keys cannot create applupdate_application — Update application-level settings (name, active state, default language, language for everyone else, incoming-message behavior, the member nimport_website_knowledge — Crawl a website into a knowledge base so an AI_TOOL_ROUTER can answer from it. Creates a new base (named after the host) unless knowledgeBasget_knowledge_base_document — Return the FULL text of one knowledge-base document, with contentSha256 — the hash edit_knowledge_base_text_document quotes as expectedSha25get_website_import — Status of a website import started by import_website_knowledge or an import_website_into_knowledge_base action: stage, progress, counters, wlist_watched_groups — List the group/channel chats a telegram_mtproto userbot monitors. Read-only. The watched list is the single source of truth for which chats list_telegram_operations — Discover supported Telegram MTProto account operations, input schemas, permissions and limits. Requires manage_broadcasts. All current operaexecute_telegram_operation — Submit one supported read operation on the connected telegram_mtproto account. Call list_telegram_operations for the input schema. Returns aget_telegram_operation — Read a Telegram operation status and result using its requestId and the same applicationId/botId used for submission. Requires manage_broadcset_watched_groups — Replace a telegram_mtproto userbot's watched-groups list — the chats it monitors. Requires the manage_settings permission. SET semantics: sesync_dialog_contacts — Import a telegram_mtproto userbot's existing chats as contacts — DM partners, groups, and channels — so everything the account already talksget_workspace_summary — Return a compact application, flow, sequence, operation, and bot summary — the cheapest way to orient in a workspace. Read-only, no side effget_variable_context — Search variable definitions by scope and keyword, or read one variable by id. Read-only. Returns { variables, total, returned, truncated } —get_application_context — Return the full application-level automation context in one read-only call: every flow (with folders), connected bots, variables, sequences,get_module_catalog — Return a compact index of both installed and available marketplace modules, with each module's key, versions, description, actions, and trigget_module_details — Return everything needed to use one module: action input fields and their types, trigger configuration, manual setup fields (credentials an install_module — Install an exact marketplace module version into an application and create any missing installed-template actions. Requires the manage_automsearch_flows — Find every flow and block whose contents contain a keyword. Read-only. Searches message text and its translations, button labels and URLs, aget_flow_context — Return one flow's graph topology: its blocks in reading order from the start block, a short summary per block, and where each block and eachget_block_details — Return the complete contents of one block: block data, action configs, HTTP request bodies, custom-code files, triggers, menu payloads, and get_action_schema — Read-only, needs no API key. The action-authoring contract apply_actions batches are validated against. With NO arguments, returns an INDEX get_design_guidelines — Return the flow-design rules that validation does NOT enforce: when to split a branch into its own flow, how navigation and menus must be wiget_funnel_analytics — Return the measured conversion funnels of the workspace's ENTRY flows over the last 14 days, busiest first: how many new contacts entered, wget_flow_analytics — Measure how NAMED flows are actually used over the last 14 days: how many contacts entered each one, where inside it they stop (per block, wget_survey_results — Read what customers ANSWERED in this workspace's surveys. A survey is any flow marked isSurvey: its choice questions record which option eacsearch_flow_examples — Search the library of reusable flow examples covering common business cases (lead capture, onboarding, payments, reminders). Read-only, needget_flow_example — Return one reusable flow example by id, optionally with a complete action batch you can adapt and pass to apply_actions. Read-only, needs novalidate_actions — Dry-run validation of a proposed batch of flow-builder actions. Mutates nothing and is safe to repeat. OPTIONAL: apply_actions runs this exaapply_actions — Validate and apply a batch of flow-builder actions — the single write path for editing flows, blocks, variables, broadcasts, sequences, and deploy_application — Publish the workspace to its bots — the API equivalent of the dashboard's Deploy button. This is the step that makes edits live. apply_actiorun_flow_autotest — Runs deterministic behavioural tests against flows that are ALREADY applied (compiles them to an AST and simulates a user). Call after applysend_message — Send a message to ONE contact right now, outside any flow. For reaching many contacts use a broadcast instead. Target the contact with contasend_flow_to_contacts — Run an EXISTING interactive flow for each listed contact right now, outside any trigger — as if each of them had just triggered it. Use it wread_messages — Read the message transcript: what users sent the bot and what the bot sent back, newest first. Source is the runtime's own message ledger, wlist_contacts — List and search contacts in the application, paginated, newest first. Read-only. Filters combine as AND; search matches name, username, emailist_bot_chats — List the groups and channels the application's bots were added to, newest first: title, kind, the numeric chatId a flow uses to address the list_contact_tags — List the contact tags in use in the application (or one bot) with how many contacts carry each, most-used first. Read-only. This is the attrget_contact — Return one contact's full profile plus every contact-variable value stored for them. Read-only. Values may hold personal data; variables of get_contact_activity — Return one contact's engagement history: goals they achieved and buttons they clicked, newest first, plus all-time goal totals. Read-only. TNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.