Map MCP outputs directly to flow variables
Under review
July 31, 2026
What it is / How it works:
It would be awesome if the platform allowed us to map outputs returned by MCP tool calls directly into temporary flow variables.
The idea is to extract specific fields from the MCP tool’s JSON response and bind them to session variables (e.g., {{order_status}} or {{user_balance}}).
Why this is useful:
Deterministic Logic & Branching: Having extracted values in variables lets us build exact conditional rules (e.g., If variable X == "Approved", go to Step Y) without relying on the LLM to make every routing decision.
Privacy & Data Security: The variables would only exist in memory for the duration of the execution session, ensuring no data collected by the MCP tool is saved or persisted in the platform's database.
This would give builders much better control when creating hybrid workflows (combining deterministic business logic with generative AI) while staying fully compliant with privacy requirements!