> This page is for version v8.3.0 (default). > For other versions, use one of these documentation indexes: > - v8.3.0 (default): https://docs.workflows.com/v-8-3-0/llms.txt > For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.workflows.com/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.workflows.com/_mcp/server. # simulate RUN # simulate Generates predictions of how a person would think, feel, communicate, and act in any scenario you describe. This is where training data becomes actionable insights. > **Success** > > Using the trained snapshot, run AI simulations to predict responses to any scenario. Each simulation completes in seconds, and you can run unlimited simulations once a snapshot is complete. ## Parameters ### mindId
**Type** string
**Required** Yes
**Description** The mind ID from the `create_mind` response
### scenario.message
**Type** string
**Required** Yes
**Description** The scenario or question to simulate. Be specific and include emotional context, time constraints, and desired outcomes for best results.
## Request ```json { "mindId": "abc-123-def-456", "scenario": { "message": "A customer is frustrated because their order is delayed by two weeks. They need the product for an event tomorrow. The item is currently out of stock. How would you respond?" } } ``` ## Response ```json { "message": "Simulation completed successfully" } ``` ### Response Properties | Property | Type | Description | | --------- | ------ | ----------------------------------------------- | | `message` | string | Status message confirming simulation completion | > **Response Format** > > The simulation response contains the AI-generated prediction of how the person would respond. The exact format may vary based on the model used, but always includes the predicted response text. ## Writing Effective Scenarios > **Warning** > > The quality of your simulation depends heavily on scenario specificity. **Vague scenario:** ``` "How would you handle a complaint?" ``` Too general—lacks context, constraints, and emotional state. **Specific scenario:** ``` "A customer received a damaged product 3 days before their wedding. They need a replacement by tomorrow, but the item is out of stock. They're understandably upset and considering canceling the order. How would you respond?" ``` Includes context, time constraints, emotional state, and desired outcome. > **Tip** > > **Include these elements:** > > * Emotional context: frustrated, confused, urgent, pleased > * Time constraints: tomorrow, by Friday, immediately > * Specific details: order numbers, product names, amounts > * Constraints: out of stock, over budget, policy limits > * Desired outcome: resolution, information, escalation ## Common Use Cases #### Sales Training Train representatives on objection handling, discovery calls, and closing techniques. **Example:** ``` "A prospect says our product is 3x more expensive than the competitor they're currently using. They like our features but can't justify the cost difference to their CFO. How would you position the value?" ``` **What you get:** * Authentic objection-handling techniques * Value proposition phrasing * Discovery questions to uncover needs * Closing strategies #### Customer Service Quality assurance testing for customer complaints, technical issues, and policy questions. **Example:** ``` "A customer's subscription was charged twice this month. They're threatening to leave and post negative reviews. They've been a loyal customer for 3 years. How would you resolve this?" ``` **What you get:** * Empathy and de-escalation techniques * Problem-solving approach * Compensation strategies * Retention tactics #### Executive Preparation Prepare for presentations by anticipating questions, concerns, and objections. **Example:** ``` "I'm proposing a $500K investment in new infrastructure that will take 18 months to show ROI. Based on past board meetings, what questions and concerns should I expect?" ``` **What you get:** * Likely questions and concerns * Communication style preferences * Key metrics to emphasize * Pre-emptive answers to prepare ## Error Responses #### 404 Not Found ```json { "error": "Not Found", "message": "Mind with ID 'abc-123' does not exist" } ``` **Solution:** Verify the `mindId` is correct and ensure you have a completed snapshot for this mind. #### 400 Bad Request ```json { "error": "Bad Request", "message": "No completed snapshot found for this mind" } ``` **Solution:** Verify snapshot training is complete using `get_snapshot_status`. Wait for snapshot to finish processing. #### 400 Invalid Scenario ```json { "error": "Bad Request", "message": "Scenario message is required" } ``` **Solution:** Ensure the `scenario.message` parameter is provided with a non-empty string. ## Best Practices #### Start Specific * Include emotional context and constraints * Provide relevant background information * Specify desired outcomes * Add time pressure when relevant #### Iterate and Refine * Run multiple variations of scenarios * Look for patterns in responses * Test edge cases and unusual situations * Compare responses across scenarios #### Test Thoroughly * Start with known scenarios to validate accuracy * Gradually introduce novel situations * Document unexpected responses * Verify critical predictions manually * Use reasoning to understand predictions ## See Also #### [get_snapshot_status](/mcp-tool-get-snapshot-status) Check training status before simulating #### [Tools Reference](/mcp-tools) View all available MCP tools #### [MCP Quick Start](/mcp-quickstart) See the complete workflow