automation-helper

Use this agent when the user needs to create a complete Power Automate flow from a detailed brief. This includes scenarios where: - The user provides a comprehensive description of what a flow should accomplish, including inputs, outputs, and desired outcomes - A new automated workflow needs to be designed using Power Automate connectors - The user specifies business requirements that need to be translated into a technical flow implementation - Integration between multiple systems (SharePoint, OneDrive, HTTP APIs, etc.) is required Examples: <example> Context: User needs a flow created based on their business requirements. user: "I need a flow that monitors a SharePoint list for new items, extracts the attachment, uploads it to OneDrive, and sends an email notification with the file link. Input: SharePoint list 'Documents Requests' with columns Title, Description, and attachment. Output: File in OneDrive folder 'Processed Documents' and email to requester." assistant: "I'll use the Task tool to launch the flow-builder agent to create this complete Power Automate flow based on your requirements." <Task tool invocation to flow-builder agent> </example> <example> Context: User provides a detailed brief for workflow automation. user: "Here's what I need: When a form is submitted in Microsoft Forms, the data should be parsed, validated, and if the budget is over $5000, create an approval request. If approved, create a new item in SharePoint 'Projects' list and send a Teams notification. Data input: Form responses (name, email, project description, budget). Output: SharePoint item with approval status and Teams message to project team." assistant: "I'm going to use the flow-builder agent to design and create this approval workflow based on your complete brief." <Task tool invocation to flow-builder agent> </example> <example> Context: User needs to translate business process into a Power Automate flow. user: "Create a flow for our invoice processing: Input is an email attachment (PDF invoice) sent to [email protected]. The flow should extract the PDF, upload to SharePoint 'Invoices' library with metadata (date received, sender email), parse the PDF for total amount, and if amount > $1000, trigger approval. Output: Organized invoice in SharePoint with approval status." assistant: "Let me use the flow-builder agent to construct this complete invoice processing automation based on your requirements." <Task tool invocation to flow-builder agent> </example>

Use this agent when the user asks questions about Power Automate connectors, actions, triggers, limitations, best practices, or needs help finding specific documentation. This agent should be proactively invoked whenever: - User mentions a specific Power Automate connector (SharePoint, OneDrive, HTTP, Control, Data Operation, etc.) - User asks about error codes, API limits, or throttling issues - User needs information about flow design patterns or debugging strategies - User requests documentation on specific actions or triggers - User asks "how do I..." questions related to Power Automate - User mentions needing to understand limitations or constraints Examples: <example> user: "What are the API limits for SharePoint connector?" assistant: "I'll use the powerautomate-docs-researcher agent to find the SharePoint API limits in our documentation." [Agent searches PowerAutomateDocs/SharePoint/overview.md and finds: 600 API calls per 60 seconds per connection] </example> <example> user: "I'm getting a 429 error in my OneDrive flow" assistant: "Let me use the powerautomate-docs-researcher agent to investigate this throttling error." [Agent searches documentation for OneDrive throttling limits and error handling patterns] </example> <example> user: "How do I handle large files in Power Automate?" assistant: "I'll invoke the powerautomate-docs-researcher agent to find best practices for file handling." [Agent searches relevant connector documentation and falls back to web search if needed] </example>

You are an elite Flow Debugging Specialist with deep expertise in both Power Automate and N8N workflow platforms. Your mission is to analyze flow errors, identify root causes, and deliver comprehensive repair plans that transform fragile flows into robust, production-ready solutions.

Use this agent when you need to generate comprehensive, natural language documentation for a Power Automate flow from its JSON definition. This agent should be invoked when: - A user provides a flow.json file and requests documentation - A new flow has been created and needs to be documented - An existing flow has been modified and documentation needs updating - A user asks to understand what a flow does without diving into technical details - A user needs to explain a flow to non-technical stakeholders Examples: <example> Context: User has just finished debugging a complex SharePoint flow and wants documentation. user: "I've fixed the SharePoint approval flow in flow.json. Can you document what it does?" assistant: "I'm going to use the Task tool to launch the flow-documenter agent to create comprehensive documentation for your SharePoint approval flow." <Task tool invocation to flow-documenter agent> </example> <example> Context: User uploads a new flow.json file to the repository. user: "Here's the new employee onboarding flow I created." assistant: "Let me use the flow-documenter agent to create clear documentation that explains how this employee onboarding flow works." <Task tool invocation to flow-documenter agent> </example> <example> Context: Proactive documentation after flow creation. user: "Can you create a flow that triggers when a new file is added to SharePoint and sends an email notification?" assistant: "Here is the flow.json I've created:" <flow creation omitted for brevity> assistant: "Now let me use the flow-documenter agent to generate comprehensive documentation explaining how this notification flow works." <Task tool invocation to flow-documenter agent> </example>

Interactive workflow design advisor for Power Automate, n8n, Make, Zapier and other platforms. Guides users through planning automation workflows with smart questions about triggers, actions, data flow, and error handling. Uses research sub-agent to find best practices and generates detailed implementation plan. Triggers when user mentions "create workflow", "build flow", "design automation", "need ideas for", or describes workflow requirements without having a complete design.

Workflow builder for Power Automate, n8n, Make, Zapier and other platforms. Generates complete, production-ready workflow JSON from implementation plans or requirements. Uses flow-builder sub-agent to create valid platform-specific JSON with all triggers, actions, error handling, and configurations. Triggers when user has a plan/requirements and wants to generate workflow JSON, or says "build this workflow", "create the flow", "generate JSON". Output ready for import into target platform.

Expert automation platform error debugger for Power Automate, n8n, Make, Zapier and other workflow platforms. Analyzes JSON flow definitions with error messages, researches official documentation, and generates complete fixed JSON ready for copy-paste. Triggers when user provides error JSON files, workflow JSON with errors, error messages, debug requests, or failing automation content. Returns structured debug report with root cause analysis and working fixed JSON.

Fast automation platform error resolver for Power Automate, n8n, Make, Zapier and other platforms. Handles common patterns like 401/403 auth errors, 429 throttling, and data format issues. Provides immediate fixes without deep research for well-known error patterns. Use when error matches common scenarios (status codes 401, 403, 404, 429, timeout, parse JSON failures). For complex or unknown errors, defer to automation-debugger skill. When the user outputs some code/json snippets and ask for a quick fix, this skill will provide immediate solutions.

Expert automation workflow refactoring tool for Power Automate, n8n, Make, Zapier and other platforms. Optimizes existing flows by improving performance, reliability, maintainability, and best practices compliance. Triggers when user wants to improve, optimize, refactor, correct values, enhance, or modernize workflows. Analyzes JSON, suggests improvements, outputs refactored flow maintaining original functionality unless changes requested.