Using Claude Code with Noukai
Full walkthrough of AI-assisted flow building — from natural language to working integration.
Claude Code (and other AI assistants) can build Noukai flows from natural language descriptions, then integrate the API call into your codebase.
Two Approaches
The fastest way to get started. No server configuration needed.
Describe What You Want
Tell Claude Code what pipeline you need:
"I want a pipeline that takes customer support tickets, classifies the intent, and generates a draft response based on the intent category"
Claude will guide you through:
- Creating the flow in the web UI
- Setting up blocks and prompts
- Integrating the API call into your code
- Configuring environment variables
What Happens Under the Hood
When you ask Claude to build a flow via MCP, here's the exact sequence of tool calls:
Integration Code
After building the flow, Claude inserts the API call into your project:
Example Prompts
| You Say | Claude Does |
|---|---|
| "Create a sentiment analysis pipeline" | Creates flow with one LLM block, prompt for sentiment classification |
| "Add error handling to my support flow" | Reads existing flow, adds a validation block |
| "Make my flow return JSON with specific fields" | Sets output schema on the final block |
| "Update the prompt in my translator to be more formal" | Calls update_block_draft with revised text |
| "Deploy the latest version" | Calls publish_version then set_production_version |
| "Add a loop that processes each item separately" | Wraps target blocks in a loop over the array field |
Troubleshooting
| Issue | Solution |
|---|---|
| Claude doesn't know about Noukai | Add noukai-prompt.md to context or verify .mcp.json |
| "401 Unauthorized" on tool calls | API key expired or revoked — create a new one |
| "Flow not found" when calling slug | Flow isn't published yet, or slug has a typo |
| "Connection refused" | Check that NOUKAI_API_URL is correct |
| Claude creates blocks in wrong order | Use get_flow_structure to check, then move_block to fix |