Skip to main content
Glama

FlowCastle

by ai.flowcastle
OverviewDiscussionsAdmin

update_application

Idempotent

Update application-level settings (name, active state, default language, language for everyone else, incoming-message behavior). Requires the manage_settings permission in that application. Only the fields you pass are changed; omitted fields keep their current value, so the call is idempotent. Returns the updated application.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoNew display name. Omit to leave unchanged.
isActiveNoSet false to deactivate the application — its bots stop responding. Omit to leave unchanged.
applicationIdNoApplication (workspace) id. Optional: an application-scoped key (app_...) defaults to its own application, but a personal key (usr_...) has no default and omitting it fails with MCP_APPLICATION_REQUIRED. Call list_applications to get the id.
defaultLanguageNoNew default language. It is the SOURCE language of the application's content: every block text is taken to be written in it, and translations are made from it. Any ISO 639 base language tag is accepted and normalised to its lowercase base form ("de", "pt-BR" → "pt"); a value that is not a 2-3 letter tag (for example "german") is rejected with INVALID_LANGUAGE — nothing falls back to "en". Changing it translates NOTHING: the texts already written are simply treated as written in the new language from then on, and the new default is dropped from the list of additional languages. Omit to leave unchanged.
fallbackLanguageNoLanguage for everyone else: the content language a contact gets when their own language is not one of the bot's languages (or unknown). Must be the default language or an enabled language; "" resets to the default language. Omit to leave unchanged.
incomingMessageFlowIdNoFlow to run for unmatched inbound messages. Required in practice when incomingMessageBehavior is EXECUTE_FLOW.
incomingMessageBehaviorNoWhat happens to an inbound message that matches no trigger: LIVE_CHAT routes it to a human operator, EXECUTE_FLOW runs the flow named by incomingMessageFlowId. Side effect of EXECUTE_FLOW: the platform also adds an "any message" MESSAGE trigger with originModuleKey "incoming_message_behavior" to that flow's start block, and removes it when this setting moves to another flow or back to LIVE_CHAT. It is system-owned: when you later resend that block's triggers with update_block, resend it unchanged with its id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / defaultLanguage / description
      Previous value: -"Default language for new flows. Only \"en\", \"ru\", and \"es\" are supported; any other value falls back to \"en\"."New value: +"New default language. It is the SOURCE language of the application's content: every block text is taken to be written in it, and translations are made from it. Any ISO 639 base language tag is accepted and normalised to its lowercase base form (\"de\", \"pt-BR\" → \"pt\"); a value that is not a 2-3 letter tag (for example \"german\") is rejected with INVALID_LANGUAGE — nothing falls back to \"en\". Changing it translates NOTHING: the texts already written are simply treated as written in the new language from then on, and the new default is dropped from the list of additional languages. Omit to leave unchanged."
    • changedInput schema / properties / incomingMessageBehavior / description
      Previous value: -"What happens to an inbound message that matches no trigger: LIVE_CHAT routes it to a human operator, EXECUTE_FLOW runs the flow named by incomingMessageFlowId."New value: +"What happens to an inbound message that matches no trigger: LIVE_CHAT routes it to a human operator, EXECUTE_FLOW runs the flow named by incomingMessageFlowId. Side effect of EXECUTE_FLOW: the platform also adds an \"any message\" MESSAGE trigger with originModuleKey \"incoming_message_behavior\" to that flow's start block, and removes it when this setting moves to another flow or back to LIVE_CHAT. It is system-owned: when you later resend that block's triggers with update_block, resend it unchanged with its id."
  2. Changed1 schema field changed
    • addedInput schema / properties / fallbackLanguage
      Added value: +{
+  "description": "Language for everyone else: the content language a contact gets when their own language is not one of the bot's languages (or unknown). Must be the default language or an enabled language; \"\" resets to the default language. Omit to leave unchanged.",
+  "type": "string"
+}
  3. Changed6 schema fields changed
    • addedInput schema / properties / applicationId / description
      Added value: +"Application (workspace) id. Optional: an application-scoped key (app_...) defaults to its own application, but a personal key (usr_...) has no default and omitting it fails with MCP_APPLICATION_REQUIRED. Call list_applications to get the id."
    • addedInput schema / properties / defaultLanguage / description
      Added value: +"Default language for new flows. Only \"en\", \"ru\", and \"es\" are supported; any other value falls back to \"en\"."
    • addedInput schema / properties / incomingMessageBehavior / description
      Added value: +"What happens to an inbound message that matches no trigger: LIVE_CHAT routes it to a human operator, EXECUTE_FLOW runs the flow named by incomingMessageFlowId."
    • addedInput schema / properties / incomingMessageFlowId / description
      Added value: +"Flow to run for unmatched inbound messages. Required in practice when incomingMessageBehavior is EXECUTE_FLOW."
    • addedInput schema / properties / isActive / description
      Added value: +"Set false to deactivate the application — its bots stop responding. Omit to leave unchanged."
    • addedInput schema / properties / name / description
      Added value: +"New display name. Omit to leave unchanged."
  4. Added

TDQS

Score is being calculated.

All FlowCastle toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources