# build-mule-integration

Workflow required before any Mule flow and integration work. Call use_skill as your FIRST action — before reading project files — whenever the user asks to create, generate, update, fix, modify, change, edit, tweak, adjust, or rework any Mule flow, sub-flow, or component. Do not read project files and attempt the change yourself — even targeted single-component changes like 'modify the choice router', 'fix the until-successful', or 'update the catch block' require this workflow. Covers all change types, new integrations and targeted changes to error handlers, catch blocks, choice routers, DataWeave transforms, HTTP listeners, foreach loops, retry policies, scatter-gathers, connectors, and variable assignments. Prompts beginning with 'This code defines...' or 'This flow...' are generation requests, not analysis. When you call this skill, it must be the only tool call in that response.

- **Skill Source:** [SKILL.md](https://dev-portal.mulesoft.com/skills/mule-development/build-mule-integration/SKILL.md)

## Steps
### Step 1: Step 1: Validate Prerequisites

### Step 2: Step 2: Identify Systems and Trigger Hints

### Step 3: Step 3: Search Exchange for Connectors, Decide, Draft the Choice

### Step 4: Step 4: Describe Connectors

### Step 5: Step 5: Select Trigger

### Step 6: Step 6: Select Connection Providers

### Step 7: Step 7: Present Technical Design Summary

### Step 8: Step 8: Create Project

### Step 9: Step 9: Apply JDBC Driver to pom.xml

### Step 10: Step 10: Verify HTTP Connector (OAuth/HTTP-Listener defensive check)

### Step 11: Step 11: Get Configuration Details

### Step 12: Step 12: Create Configuration Files

### Step 13: Step 13: Get Operation / Source Details

### Step 14: Step 14: Generate Complete Flow

### Step 15: Step 15: Add `doc:name` and `doc:description` to Canvas-Visible Elements

### Step 16: Step 16: Build and Verify

### Step 17: Step 17: Clean Up Workspace `tmp/`

### Step 18: Step 18: Declare Completion