Scenario inputs and outputs

{{scenario singular}} inputs and outputs let you control what data goes into your {{scenario singular lowercase}} and what data comes out they define the information that {{scenario plural lowercase}} expect and share when communicating with other scenarios or external systems to find {{scenario singular lowercase}} inputs and outputs, navigate to the {{scenario singular}} builder and click on the scenario inputs and outputs icon on the toolbar what {{scenario singular lowercase}} inputs and outputs do scenario inputs define what data a scenario receives when triggered scenario outputs define what data the scenario returns after execution when a {{scenario singular lowercase}} calls another {{scenario singular lowercase}} (subscenario), inputs specify what data gets passed to the subscenario, while outputs specify what data gets returned to the calling {{scenario singular lowercase}} when you need {{scenario singular lowercase}} inputs and outputs you will need to create the structure of scenario inputs or outputs docid\ m0sq0 loyhxlfze6fxusd when building {{scenario plural lowercase}} that communicate with other {{scenario plural lowercase}} or external systems this includes {{scenario plural lowercase}} that call other {{scenario plural lowercase}} (subscenarios) get triggered by external systems via api function as tools in ai systems some cases when you need {{scenario singular lowercase}} inputs and outputs syncing customer information across multiple systems adding leads to crm and email lists while creating proposals creating records, invoices, emails, or orders with specific input parameters where to use {{scenario singular lowercase}} inputs and outputs {{scenario singular}} inputs and outputs enable your scenarios to function as tools across different systems subscenarios, apis, make ai agents, and make mcp server regardless of which system you are working with, {{scenario plural lowercase}} with {{scenario singular lowercase}} inputs and outputs use three modules call a subscenario , start a subscenario , and return output consider this flow to understand how these modules interact in the parent scenario, you add a call a subscenario module, then select an existing (sub)scenario or create a new one in the subscenario, add a start a subscenario module, which allows you to map {{scenario singular lowercase}} inputs to modules add more modules depending on what the subscenario aims to do add a return output module to send output from the subscenario to the parent this flow applies to all cases using {{scenario singular lowercase}} inputs and outputs subscenarios subscenarios docid 9cmtjaptug8sqnm3uq ay break complex workflows into smaller, reusable components each subscenario handles a specific task or business function {{scenario singular}} inputs and outputs define the data exchanged between parent {{scenario singular lowercase}} and subscenarios the start a subscenario module triggers the subscenario and passes input data the return output module returns data from the subscenario to the calling {{scenario singular lowercase}} benefits of inputs and outputs in subscenarios reusability updates to a subscenario's inputs and outputs automatically apply to all {{scenario plural lowercase}} using that subscenario structured data sharing inputs and outputs clearly define what data gets shared between {{scenario plural lowercase}} example a {{scenario singular lowercase}} that retrieves restaurant menus could use subscenarios for individual restaurants each subscenario receives restaurant name/id and date as inputs, then returns menu items, prices, and last updated timestamps as outputs apis the make api allows external systems to trigger {{scenario plural lowercase}} {{scenario singular}} inputs and outputs define the structure of api requests and responses when calling a {{scenario singular lowercase}} via api, the defined inputs become the request body parameters after execution, the {{scenario singular lowercase}} returns the defined outputs in the response structure example an external application triggers a restaurant menu {{scenario singular lowercase}} via api, sending date and restaurant id as inputs the {{scenario singular lowercase}} returns structured menu data as outputs make ai agents make ai agents docid 0kbnuoduk1emvkqnwmdqc can use {{scenario singular lowercase}} as tools {{scenario singular}} inputs and outputs help agents understand what data to provide and what to expect in return input and output names and descriptions help ai agents select appropriate data, similar to how tool names and descriptions help agents choose the right tools inputs and outputs in data flow patterns agent to scenario when {{scenario singular lowercase}} inputs are defined scenario to agent when {{scenario singular lowercase}} outputs are defined bidirectional when both inputs and outputs are defined example a simple ai agent for retrieving daily restaurant menus uses subscenarios for each restaurant as its tools based on the user prompt, the agent calls the right {{scenario singular lowercase}} and returns a menu the agent used the outputs structure in the subscenario to understand the menu data to give in the response make mcp server the make mcp server enables {{scenario plural lowercase}} to run from mcp enabled ai systems like claude {{scenario singular}} inputs and outputs serve as instructions for ai systems by defining the information to exchange during interactions {{scenario singular}} inputs are parameters that ai systems fill when using scenarios {{scenario singular}} outputs are parameters for data that scenarios return to ai systems example when you claude, an mcp client, about a restaurant's daily menu, claude calls the relevant {{scenario plural lowercase}} through the mcp server the {{scenario singular lowercase}} outputs provide the menu information for claude's response