integrations.yml as configuration that parses and validates without a runtime
consumer; those are called out below.
Responses and questions
Variant selection by channel. Multiple variants are already parsed; only the first is used today.ask_<memory_entry> hooks for dynamically generated questions, so a skill
can compute the wording of a collect: prompt at runtime.
Integrations
Knowledge stores.knowledge_stores: (Qdrant, Milvus, external FAISS)
validates but is never queried. Today search_knowledge reads only the local
index built from references/**/*.md.
Per-skill retrieval scoping, so a skill’s own references/ are searched
ahead of, or instead of, the shared index.
Tracker store (Postgres, etc.) for persistent conversation state, and
event broker (Kafka, etc.) for streaming conversation events.
Remote tool hosting
rasa run tools will spin up a dedicated tool server that the runtime
connects to over MCP, letting you host tools separately.
MCP extras. pre_call_hook and meta_map.from_slots are not supported.
Use meta_map.static for per-call _meta.