feat(autominator): improve elicitation to focus on actual problems
This commit is contained in:
mrsaifullah52
parent
3fa0865542
commit
ffe6f6c26b
|
|
@ -29,92 +29,107 @@
|
|||
</step>
|
||||
|
||||
<step n="1" goal="Gather Requirements" elicit="true">
|
||||
<action>Ask Question 1: "What type of automation workflow do you need?"</action>
|
||||
<critical>Start by understanding the ACTUAL PROBLEM the user wants to solve, not just technical requirements</critical>
|
||||
|
||||
<action>Ask Question 1: "What problem are you trying to solve with this automation?"</action>
|
||||
<action>Encourage detailed explanation: "Describe the current manual process, pain points, and desired outcome."</action>
|
||||
<action>WAIT for user input</action>
|
||||
<action>Store in {{problem_description}}</action>
|
||||
|
||||
<action>Ask Question 2: "What triggers this process? When should the automation run?"</action>
|
||||
<action>Present numbered options:
|
||||
1. Webhook-based - Receive HTTP requests and process data
|
||||
2. Scheduled - Run on a schedule (cron/interval)
|
||||
3. Event-driven - Trigger from external service events
|
||||
4. Manual - Execute on demand
|
||||
5. Database-driven - Trigger from database changes
|
||||
6. Other - Describe your specific trigger needs
|
||||
1. When data arrives - Webhook, form submission, API call
|
||||
2. On a schedule - Every hour, daily, weekly, custom cron
|
||||
3. When something changes - Database update, file change, service event
|
||||
4. Manually - On-demand execution
|
||||
5. Multiple triggers - Combination of above
|
||||
6. Not sure - Help me decide based on my problem
|
||||
</action>
|
||||
<action>WAIT for user selection (1-6)</action>
|
||||
<action>Store selection in {{workflow_type}}</action>
|
||||
<action>Store selection in {{trigger_type}}</action>
|
||||
|
||||
<check if="selection is 6 (Other)">
|
||||
<action>Ask: "Please describe your trigger requirements"</action>
|
||||
<action>WAIT for user input</action>
|
||||
<action>Store in {{workflow_type}}</action>
|
||||
<check if="selection is 6 (Not sure)">
|
||||
<action>Analyze {{problem_description}} and suggest appropriate trigger</action>
|
||||
<action>Ask: "Based on your problem, I recommend [trigger type]. Does this make sense?"</action>
|
||||
<action>WAIT for confirmation or adjustment</action>
|
||||
<action>Store final trigger in {{trigger_type}}</action>
|
||||
</check>
|
||||
|
||||
<action>Ask Question 2: "What integrations or services will this workflow use?"</action>
|
||||
<action>Present numbered options:
|
||||
1. HTTP/REST APIs - Generic API calls
|
||||
2. Databases - PostgreSQL, MySQL, MongoDB, etc.
|
||||
3. Cloud Services - Google Sheets, Slack, Notion, Airtable
|
||||
4. Email - Send/receive emails
|
||||
5. CRM - HubSpot, Salesforce, etc.
|
||||
6. Custom Code - JavaScript/Python logic
|
||||
7. Multiple - Combination of above
|
||||
8. Other - Specify integrations
|
||||
</action>
|
||||
<action>WAIT for user selection (1-8)</action>
|
||||
<action>Store selection in {{integrations}}</action>
|
||||
<action>Ask Question 3: "What data or information does this workflow need to work with?"</action>
|
||||
<action>Examples: "Customer data, order details, form responses, API data, etc."</action>
|
||||
<action>WAIT for user input</action>
|
||||
<action>Store in {{data_requirements}}</action>
|
||||
|
||||
<check if="selection is 7 or 8">
|
||||
<action>Ask: "Please list all integrations needed (comma-separated)"</action>
|
||||
<action>Ask Question 4: "What should happen with this data? What's the desired outcome?"</action>
|
||||
<action>Examples: "Send to Slack, update database, create invoice, notify team, etc."</action>
|
||||
<action>WAIT for user input</action>
|
||||
<action>Store in {{desired_outcome}}</action>
|
||||
|
||||
<action>Ask Question 5: "What services or systems are involved?"</action>
|
||||
<action>Examples: "Slack, Google Sheets, PostgreSQL, HubSpot, custom API, etc."</action>
|
||||
<action>WAIT for user input</action>
|
||||
<action>Store in {{integrations}}</action>
|
||||
|
||||
<action>Ask Question 6: "Are there any conditions or decision points in this process?"</action>
|
||||
<action>Examples: "If amount > $1000, notify manager; If status = 'urgent', send immediately"</action>
|
||||
<action>Present numbered options:
|
||||
1. No - Straight-through processing
|
||||
2. Yes - Describe the conditions
|
||||
</action>
|
||||
<action>WAIT for user selection (1-2)</action>
|
||||
<check if="selection is 2">
|
||||
<action>Ask: "Describe the conditions and what should happen in each case"</action>
|
||||
<action>WAIT for user input</action>
|
||||
<action>Store in {{integrations}}</action>
|
||||
<action>Store in {{conditional_logic}}</action>
|
||||
</check>
|
||||
|
||||
<action>Ask Question 3: "How complex is your workflow logic?"</action>
|
||||
<action>Ask Question 7: "How critical is this workflow? What happens if it fails?"</action>
|
||||
<action>Present numbered options:
|
||||
1. Simple (3-5 nodes) - Linear flow with minimal logic
|
||||
2. Medium (6-10 nodes) - Some conditional logic or branching
|
||||
3. Complex (11-20 nodes) - Multiple branches, loops, or error handling
|
||||
4. Very Complex (20+ nodes) - Advanced logic with parallel processing
|
||||
1. Low - Can retry manually if needed
|
||||
2. Medium - Should retry automatically, notify on failure
|
||||
3. High - Must succeed, need alerts and logging
|
||||
4. Critical - Business-critical, need comprehensive error handling
|
||||
</action>
|
||||
<action>WAIT for user selection (1-4)</action>
|
||||
<action>Store selection in {{complexity}}</action>
|
||||
<action>Store selection in {{criticality}}</action>
|
||||
|
||||
<action>Ask Question 4: "Do you need error handling and retry logic?"</action>
|
||||
<action>Present numbered options:
|
||||
1. No - Simple workflow without error handling
|
||||
2. Basic - Retry failed operations automatically
|
||||
3. Advanced - Custom error handling with notifications
|
||||
4. Comprehensive - Full error workflow with logging and alerts
|
||||
</action>
|
||||
<action>WAIT for user selection (1-4)</action>
|
||||
<action>Store selection in {{error_handling}}</action>
|
||||
|
||||
<action>Ask Question 5: "What should the workflow be named?"</action>
|
||||
<action>Ask Question 8: "What should the workflow be named?"</action>
|
||||
<action>Suggest name based on {{problem_description}}</action>
|
||||
<action>WAIT for user input</action>
|
||||
<action>Store in {{workflow_name}}</action>
|
||||
|
||||
<action>Ask Question 6: "Where should the workflow file be saved?"</action>
|
||||
<action>Ask Question 9: "Where should the workflow file be saved?"</action>
|
||||
<action>Present numbered options:
|
||||
1. Default location - workflows/[workflow-name].json
|
||||
2. Custom path - Specify your own file path
|
||||
3. Project root - Save in main project directory
|
||||
4. Specific folder - Choose from existing folders
|
||||
</action>
|
||||
<action>WAIT for user selection (1-4)</action>
|
||||
<check if="selection is 2 or 4">
|
||||
<action>WAIT for user selection (1-2)</action>
|
||||
<check if="selection is 2">
|
||||
<action>Ask for specific path</action>
|
||||
<action>WAIT for user input</action>
|
||||
</check>
|
||||
<action>Store final path in {{save_location}}</action>
|
||||
|
||||
<action>Ask Question 7: "Any additional requirements or specific logic needed?"</action>
|
||||
<action>Summarize understanding:</action>
|
||||
<action>- Problem: {{problem_description}}</action>
|
||||
<action>- Trigger: {{trigger_type}}</action>
|
||||
<action>- Data: {{data_requirements}}</action>
|
||||
<action>- Outcome: {{desired_outcome}}</action>
|
||||
<action>- Services: {{integrations}}</action>
|
||||
<action>- Conditions: {{conditional_logic}}</action>
|
||||
<action>- Criticality: {{criticality}}</action>
|
||||
|
||||
<action>Ask: "Does this capture your requirements correctly?"</action>
|
||||
<action>Present numbered options:
|
||||
1. No - Proceed with current requirements
|
||||
2. Yes - Describe additional requirements
|
||||
1. Yes - Proceed with workflow creation
|
||||
2. No - Let me clarify or add details
|
||||
</action>
|
||||
<action>WAIT for user selection (1-2)</action>
|
||||
<check if="selection is 2">
|
||||
<action>Ask: "Please describe additional requirements"</action>
|
||||
<action>Ask: "What needs to be clarified or added?"</action>
|
||||
<action>WAIT for user input</action>
|
||||
<action>Store in {{additional_requirements}}</action>
|
||||
<action>Update relevant variables</action>
|
||||
<action>Repeat summary and confirmation</action>
|
||||
</check>
|
||||
</step>
|
||||
|
||||
|
|
@ -153,32 +168,70 @@
|
|||
</step>
|
||||
|
||||
<step n="4" goal="Plan Workflow Structure">
|
||||
<action>Based on gathered requirements, plan the workflow structure:</action>
|
||||
<action>1. Identify trigger node type</action>
|
||||
<action>2. List all action nodes needed</action>
|
||||
<action>3. Identify conditional logic (IF nodes)</action>
|
||||
<action>4. Plan data transformations (Set/Code nodes)</action>
|
||||
<action>5. Design error handling strategy</action>
|
||||
<action>6. Map node connections</action>
|
||||
<critical>Design workflow based on the ACTUAL PROBLEM, not just technical specs</critical>
|
||||
|
||||
<action>Present the planned structure to user in clear format:</action>
|
||||
<action>- Trigger: [trigger type]</action>
|
||||
<action>- Nodes: [list of nodes with descriptions]</action>
|
||||
<action>- Logic: [conditional branches, loops]</action>
|
||||
<action>- Error Handling: [strategy]</action>
|
||||
<action>Analyze the problem and requirements:</action>
|
||||
<action>- Problem to solve: {{problem_description}}</action>
|
||||
<action>- Trigger: {{trigger_type}}</action>
|
||||
<action>- Data needed: {{data_requirements}}</action>
|
||||
<action>- Desired outcome: {{desired_outcome}}</action>
|
||||
<action>- Services: {{integrations}}</action>
|
||||
<action>- Conditions: {{conditional_logic}}</action>
|
||||
<action>- Criticality: {{criticality}}</action>
|
||||
|
||||
<action>Ask: "Does this structure meet your needs?"</action>
|
||||
<action>Design workflow structure that solves the problem:</action>
|
||||
<action>1. Map trigger to appropriate n8n trigger node</action>
|
||||
<action>2. Design data acquisition steps (API calls, database queries)</action>
|
||||
<action>3. Plan data transformations needed for the outcome</action>
|
||||
<action>4. Implement conditional logic from {{conditional_logic}}</action>
|
||||
<action>5. Design actions to achieve {{desired_outcome}}</action>
|
||||
<action>6. Add error handling based on {{criticality}}</action>
|
||||
<action>7. Plan node connections and data flow</action>
|
||||
|
||||
<action>Present the solution-focused workflow plan:</action>
|
||||
<action>## Workflow Solution for: {{problem_description}}</action>
|
||||
<action></action>
|
||||
<action>**How it works:**</action>
|
||||
<action>[Explain in plain language how the workflow solves the problem]</action>
|
||||
<action></action>
|
||||
<action>**Workflow Steps:**</action>
|
||||
<action>1. Trigger: [When/how it starts] - [n8n node type]</action>
|
||||
<action>2. Get Data: [What data is retrieved] - [n8n nodes]</action>
|
||||
<action>3. Process: [How data is transformed] - [n8n nodes]</action>
|
||||
<action>4. Decide: [Conditional logic if any] - [IF/Switch nodes]</action>
|
||||
<action>5. Act: [Final actions to achieve outcome] - [n8n nodes]</action>
|
||||
<action>6. Handle Errors: [Error strategy] - [Error handling config]</action>
|
||||
<action></action>
|
||||
<action>**Expected Result:**</action>
|
||||
<action>[Describe what happens when workflow runs successfully]</action>
|
||||
|
||||
<action>Ask: "Does this workflow solve your problem?"</action>
|
||||
<action>Present numbered options:
|
||||
1. Yes - Proceed with this structure
|
||||
2. No - Adjust the structure
|
||||
3. Add more details - Provide additional requirements
|
||||
1. Yes - This solves my problem, proceed
|
||||
2. No - Missing something important
|
||||
3. Partially - Needs adjustments
|
||||
4. Explain more - I need clarification
|
||||
</action>
|
||||
<action>WAIT for user selection (1-3)</action>
|
||||
<action>WAIT for user selection (1-4)</action>
|
||||
|
||||
<check if="selection is 2 or 3">
|
||||
<action>Ask: "What changes or additions are needed?"</action>
|
||||
<check if="selection is 2">
|
||||
<action>Ask: "What's missing? What else needs to happen?"</action>
|
||||
<action>WAIT for user input</action>
|
||||
<action>Adjust structure based on feedback</action>
|
||||
<action>Adjust workflow design to include missing elements</action>
|
||||
<action>Repeat this step</action>
|
||||
</check>
|
||||
|
||||
<check if="selection is 3">
|
||||
<action>Ask: "What needs to be adjusted?"</action>
|
||||
<action>WAIT for user input</action>
|
||||
<action>Modify workflow design based on feedback</action>
|
||||
<action>Repeat this step</action>
|
||||
</check>
|
||||
|
||||
<check if="selection is 4">
|
||||
<action>Ask: "Which part needs clarification?"</action>
|
||||
<action>WAIT for user input</action>
|
||||
<action>Provide detailed explanation of that part</action>
|
||||
<action>Repeat this step</action>
|
||||
</check>
|
||||
</step>
|
||||
|
|
|
|||
|
|
@ -29,7 +29,14 @@
|
|||
</step>
|
||||
|
||||
<step n="1" goal="Gather Migration Requirements" elicit="true">
|
||||
<action>Ask Question 1: "Which platform are you migrating from?"</action>
|
||||
<critical>Understand the BUSINESS PURPOSE of the workflow being migrated, not just technical details</critical>
|
||||
|
||||
<action>Ask Question 1: "What does this workflow do? What problem does it solve?"</action>
|
||||
<action>Encourage business context: "Describe the business process, not just the technical steps"</action>
|
||||
<action>WAIT for user input</action>
|
||||
<action>Store in {{business_purpose}}</action>
|
||||
|
||||
<action>Ask Question 2: "Which platform are you migrating from?"</action>
|
||||
<action>Present numbered options:
|
||||
1. Zapier - Migrate Zapier Zaps to n8n
|
||||
2. Make (Integromat) - Migrate Make scenarios to n8n
|
||||
|
|
@ -47,66 +54,59 @@
|
|||
<action>Store in {{source_platform}}</action>
|
||||
</check>
|
||||
|
||||
<action>Ask Question 2: "How will you provide the workflow to migrate?"</action>
|
||||
<action>Ask Question 3: "Why are you migrating to n8n?"</action>
|
||||
<action>Examples: "Cost savings", "More flexibility", "Self-hosting", "Better integrations"</action>
|
||||
<action>WAIT for user input</action>
|
||||
<action>Store in {{migration_reason}}</action>
|
||||
|
||||
<action>Ask Question 4: "How will you provide the workflow details?"</action>
|
||||
<action>Present numbered options:
|
||||
1. Describe it - Explain what the workflow does
|
||||
1. Describe the process - Explain what happens step by step
|
||||
2. Provide export file - Upload/paste workflow export file
|
||||
3. Provide screenshots - Share workflow screenshots
|
||||
4. Provide documentation - Share workflow documentation
|
||||
4. Combination - Multiple sources
|
||||
</action>
|
||||
<action>WAIT for user selection (1-4)</action>
|
||||
|
||||
<check if="selection is 1">
|
||||
<action>Ask: "Please describe what the workflow does (trigger, actions, logic)"</action>
|
||||
<check if="selection is 1 or 4">
|
||||
<action>Ask: "Describe the workflow step by step:"</action>
|
||||
<action>- What triggers it?</action>
|
||||
<action>- What data does it process?</action>
|
||||
<action>- What actions does it take?</action>
|
||||
<action>- What's the final outcome?</action>
|
||||
<action>WAIT for user input</action>
|
||||
<action>Store in {{workflow_description}}</action>
|
||||
</check>
|
||||
|
||||
<check if="selection is 2">
|
||||
<check if="selection is 2 or 4">
|
||||
<action>Ask: "Please provide the workflow export file path or paste the content"</action>
|
||||
<action>WAIT for user input</action>
|
||||
<action>Store in {{workflow_file}} or {{workflow_content}}</action>
|
||||
</check>
|
||||
|
||||
<check if="selection is 3">
|
||||
<action>Ask: "Please share the workflow screenshots and describe the flow"</action>
|
||||
<check if="selection is 3 or 4">
|
||||
<action>Ask: "Please share the workflow screenshots and describe what each part does"</action>
|
||||
<action>WAIT for user input</action>
|
||||
<action>Store in {{workflow_description}}</action>
|
||||
<action>Store in {{workflow_screenshots}}</action>
|
||||
</check>
|
||||
|
||||
<check if="selection is 4">
|
||||
<action>Ask: "Please provide the workflow documentation"</action>
|
||||
<action>WAIT for user input</action>
|
||||
<action>Store in {{workflow_description}}</action>
|
||||
</check>
|
||||
|
||||
<action>Ask Question 3: "What is the trigger for this workflow?"</action>
|
||||
<action>Present numbered options:
|
||||
1. Webhook/HTTP Request - Triggered by incoming HTTP requests
|
||||
2. Schedule/Cron - Runs on a schedule
|
||||
3. Form Submission - Triggered by form submissions
|
||||
4. Database Change - Triggered by database events
|
||||
5. Email - Triggered by incoming emails
|
||||
6. Service Event - Triggered by external service (Slack, Google Sheets, etc.)
|
||||
7. Not sure - Will determine from workflow details
|
||||
</action>
|
||||
<action>WAIT for user selection (1-7)</action>
|
||||
<action>Store selection in {{trigger_type}}</action>
|
||||
|
||||
<action>Ask Question 4: "What integrations/services does this workflow use?"</action>
|
||||
<action>Ask: "Please list all services (e.g., Slack, Google Sheets, HubSpot, etc.)"</action>
|
||||
<action>Ask Question 5: "What services/integrations does this workflow connect to?"</action>
|
||||
<action>Ask: "List all services (e.g., Slack, Google Sheets, HubSpot, custom APIs, etc.)"</action>
|
||||
<action>WAIT for user input</action>
|
||||
<action>Store in {{integrations_used}}</action>
|
||||
|
||||
<action>Ask Question 5: "How complex is the workflow?"</action>
|
||||
<action>Ask Question 6: "Are there any pain points or issues with the current workflow?"</action>
|
||||
<action>Examples: "Slow execution", "Unreliable", "Missing features", "Hard to maintain"</action>
|
||||
<action>Present numbered options:
|
||||
1. Simple - Linear flow with 3-5 steps
|
||||
2. Medium - Some conditional logic, 6-10 steps
|
||||
3. Complex - Multiple branches, loops, 11-20 steps
|
||||
4. Very Complex - Advanced logic, 20+ steps
|
||||
1. No - Works fine, just migrating platform
|
||||
2. Yes - Describe the issues
|
||||
</action>
|
||||
<action>WAIT for user selection (1-4)</action>
|
||||
<action>Store selection in {{complexity}}</action>
|
||||
<action>WAIT for user selection (1-2)</action>
|
||||
<check if="selection is 2">
|
||||
<action>Ask: "What issues should we fix during migration?"</action>
|
||||
<action>WAIT for user input</action>
|
||||
<action>Store in {{issues_to_fix}}</action>
|
||||
</check>
|
||||
|
||||
<action>Ask Question 6: "What should the migrated workflow be named?"</action>
|
||||
<action>WAIT for user input</action>
|
||||
|
|
|
|||
|
|
@ -29,6 +29,8 @@
|
|||
</step>
|
||||
|
||||
<step n="1" goal="Gather Requirements" elicit="true">
|
||||
<critical>Understand WHY the user wants to modify the workflow, not just WHAT to change</critical>
|
||||
|
||||
<action>Ask Question 1: "Which workflow file do you want to modify?"</action>
|
||||
<action>Present numbered options:
|
||||
1. Provide file path - Specify exact path to workflow JSON
|
||||
|
|
@ -57,39 +59,43 @@
|
|||
<action>Store temp file path in {{workflow_file}}</action>
|
||||
</check>
|
||||
|
||||
<action>Ask Question 2: "What type of modification do you need?"</action>
|
||||
<action>Present numbered options:
|
||||
1. Add new nodes - Add functionality to existing workflow
|
||||
2. Modify existing nodes - Change node parameters or configuration
|
||||
3. Remove nodes - Delete nodes from workflow
|
||||
4. Change connections - Modify how nodes are connected
|
||||
5. Update error handling - Add or modify retry/error logic
|
||||
6. Optimize workflow - Improve performance or structure
|
||||
7. Multiple changes - Combination of above
|
||||
</action>
|
||||
<action>WAIT for user selection (1-7)</action>
|
||||
<action>Store selection in {{modification_type}}</action>
|
||||
|
||||
<action>Ask Question 3: "Please describe the changes you want to make"</action>
|
||||
<action>Ask Question 2: "What problem are you trying to solve by modifying this workflow?"</action>
|
||||
<action>Examples: "It's not handling errors properly", "Need to add Slack notifications", "Missing data validation"</action>
|
||||
<action>WAIT for user input</action>
|
||||
<action>Store in {{changes_description}}</action>
|
||||
<action>Store in {{problem_to_solve}}</action>
|
||||
|
||||
<check if="{{modification_type}} includes adding nodes">
|
||||
<action>Ask: "What nodes do you want to add? (describe functionality)"</action>
|
||||
<action>WAIT for user input</action>
|
||||
<action>Store in {{nodes_to_add}}</action>
|
||||
</check>
|
||||
<action>Ask Question 3: "What's currently not working or missing?"</action>
|
||||
<action>Encourage specific details about the issue or gap</action>
|
||||
<action>WAIT for user input</action>
|
||||
<action>Store in {{current_issue}}</action>
|
||||
|
||||
<check if="{{modification_type}} includes modifying nodes">
|
||||
<action>Ask: "Which nodes do you want to modify? (provide node names or descriptions)"</action>
|
||||
<action>WAIT for user input</action>
|
||||
<action>Store in {{nodes_to_modify}}</action>
|
||||
</check>
|
||||
<action>Ask Question 4: "What should the workflow do after these changes?"</action>
|
||||
<action>Focus on the desired behavior and outcome</action>
|
||||
<action>WAIT for user input</action>
|
||||
<action>Store in {{desired_behavior}}</action>
|
||||
|
||||
<check if="{{modification_type}} includes removing nodes">
|
||||
<action>Ask: "Which nodes do you want to remove? (provide node names)"</action>
|
||||
<action>Ask Question 5: "Are there any specific nodes, integrations, or logic you want to change?"</action>
|
||||
<action>Examples: "Add a Slack node after approval", "Change the IF condition to check status", "Remove the delay node"</action>
|
||||
<action>WAIT for user input</action>
|
||||
<action>Store in {{specific_changes}}</action>
|
||||
|
||||
<action>Summarize understanding:</action>
|
||||
<action>- Problem: {{problem_to_solve}}</action>
|
||||
<action>- Current Issue: {{current_issue}}</action>
|
||||
<action>- Desired Behavior: {{desired_behavior}}</action>
|
||||
<action>- Specific Changes: {{specific_changes}}</action>
|
||||
|
||||
<action>Ask: "Does this capture what you need?"</action>
|
||||
<action>Present numbered options:
|
||||
1. Yes - Proceed with modifications
|
||||
2. No - Let me clarify
|
||||
</action>
|
||||
<action>WAIT for user selection (1-2)</action>
|
||||
<check if="selection is 2">
|
||||
<action>Ask: "What needs clarification?"</action>
|
||||
<action>WAIT for user input</action>
|
||||
<action>Store in {{nodes_to_remove}}</action>
|
||||
<action>Update relevant variables</action>
|
||||
<action>Repeat summary and confirmation</action>
|
||||
</check>
|
||||
</step>
|
||||
|
||||
|
|
|
|||
|
|
@ -29,6 +29,8 @@
|
|||
</step>
|
||||
|
||||
<step n="1" goal="Gather Optimization Requirements" elicit="true">
|
||||
<critical>Understand the REAL PROBLEMS the user is experiencing, not just generic optimization goals</critical>
|
||||
|
||||
<action>Ask Question 1: "Which workflow do you want to optimize?"</action>
|
||||
<action>Present numbered options:
|
||||
1. Provide file path - Specify exact path to workflow JSON
|
||||
|
|
@ -57,30 +59,50 @@
|
|||
<action>Store temp file path in {{workflow_file}}</action>
|
||||
</check>
|
||||
|
||||
<action>Ask Question 2: "What aspects do you want to optimize?"</action>
|
||||
<action>Ask Question 2: "What problems are you experiencing with this workflow?"</action>
|
||||
<action>Examples: "Takes too long to run", "Fails frequently", "Hard to understand", "Doesn't handle errors well"</action>
|
||||
<action>WAIT for user input</action>
|
||||
<action>Store in {{problems_experienced}}</action>
|
||||
|
||||
<action>Ask Question 3: "What's the business impact of these problems?"</action>
|
||||
<action>Examples: "Delays customer responses", "Wastes team time", "Causes data issues", "Costs money"</action>
|
||||
<action>WAIT for user input</action>
|
||||
<action>Store in {{business_impact}}</action>
|
||||
|
||||
<action>Ask Question 4: "What would 'better' look like for this workflow?"</action>
|
||||
<action>Focus on desired outcomes: "Faster execution", "More reliable", "Easier to maintain", "Better error recovery"</action>
|
||||
<action>WAIT for user input</action>
|
||||
<action>Store in {{desired_improvements}}</action>
|
||||
|
||||
<action>Ask Question 5: "Are there specific areas you want me to focus on?"</action>
|
||||
<action>Present numbered options (can select multiple):
|
||||
1. Performance - Improve execution speed and efficiency
|
||||
2. Error Handling - Add or improve error handling and retries
|
||||
3. Code Quality - Improve node configuration and data transformations
|
||||
4. Structure - Improve workflow organization and readability
|
||||
5. Best Practices - Apply n8n best practices and patterns
|
||||
6. Security - Improve credential handling and data security
|
||||
7. All - Comprehensive optimization review
|
||||
1. Performance - Speed and efficiency
|
||||
2. Reliability - Error handling and retries
|
||||
3. Maintainability - Code quality and structure
|
||||
4. Security - Credential and data handling
|
||||
5. All - Comprehensive review
|
||||
6. Let you decide - Analyze and recommend
|
||||
</action>
|
||||
<action>WAIT for user selection (1-7 or multiple)</action>
|
||||
<action>WAIT for user selection (1-6 or multiple)</action>
|
||||
<action>Store selections in {{optimization_focus}}</action>
|
||||
|
||||
<action>Ask Question 3: "Are there specific issues or pain points?"</action>
|
||||
<action>Summarize understanding:</action>
|
||||
<action>- Problems: {{problems_experienced}}</action>
|
||||
<action>- Business Impact: {{business_impact}}</action>
|
||||
<action>- Desired Improvements: {{desired_improvements}}</action>
|
||||
<action>- Focus Areas: {{optimization_focus}}</action>
|
||||
|
||||
<action>Ask: "Does this capture your optimization needs?"</action>
|
||||
<action>Present numbered options:
|
||||
1. No - Just general optimization
|
||||
2. Yes - Describe specific issues
|
||||
1. Yes - Proceed with analysis
|
||||
2. No - Let me clarify
|
||||
</action>
|
||||
<action>WAIT for user selection (1-2)</action>
|
||||
|
||||
<check if="selection is 2">
|
||||
<action>Ask: "Please describe the issues (slow execution, errors, etc.)"</action>
|
||||
<action>Ask: "What needs clarification?"</action>
|
||||
<action>WAIT for user input</action>
|
||||
<action>Store in {{specific_issues}}</action>
|
||||
<action>Update relevant variables</action>
|
||||
<action>Repeat summary and confirmation</action>
|
||||
</check>
|
||||
</step>
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue