How it works
To move data from Slack to MCP Server automatically, use a ready-made scenario — no manual exports.
- Starts when: Telegram Trigger
- Check: Route Input by Message Type
- If yes: Rename Fields
- Then: Classify Message Intent
- Check: Route to Expense or Query Processing
- If yes: Agent
- Then: Send Message
- If no: Parse and Split Multiple Expenses
- If no: Get Voice File from Telegram
- Then: Convert Voice to Text (ElevenLabs)
- If no: Download Receipt Image
- Then: Extract Receipt Data
- Then: MCP Client
- Starts when: MCP Server Trigger
- Then: Calculator
- Then: Total_Spent_Tool
- Then: Balance_Tool
- Then: Expenses_Tool
- Then: Exchange_Rate
- Then: Add_Expenses_Tool
- Then: Read_Rows_Tool
- Then: Intent Classification Model
- Then: Expense Parsing Model
- Then: Main Financial Assistant
You can launch this Slack + MCP Server integration in Scriptera: describe the task in plain words — the scenario is built, launched and monitored for you.