Test MusVideo Storyboard API Key via HTTP Request

Test your MusVideo Storyboard API key with a single HTTP request (no image/video generation)

This n8n workflow lets you verify your MusVideo storyboard x-api-key authentication by manually sending a sample audio URL, then splitting the returned storyboard into individual scene items you can inspect—without generating any images or videos.

What this workflow does

• Manual trigger: The workflow runs when you execute it manually in n8n.
• Build a test payload: It sets a sample request with an audioUrl, a title, and a visual style prompt (you can optionally replace these values before running).
• POST to MusVideo storyboard endpoint: It sends a POST request to create a storyboard with scenes (the source notes scenes up to 15 seconds per scene) and returns the full HTTP response.
• Split the response into per-scene items: Using body.data.scenes, it outputs one n8n item per scene, exposing fields such as startTime, duration, imagePrompt, videoPrompt, and lyrics.

Use cases

• API key verification: Confirm your MusVideo x-api-key is accepted before integrating storyboard generation into a production pipeline.
• Prompt inspection: Review returned scene prompts (image/video) and lyrics to validate your request and expectations.
• Integration debugging: Quickly see the raw storyboard HTTP response and scene-level parsing results when troubleshooting n8n automations.

Technical details

• Authentication: Create an HTTP Header Auth credential that sends your MusVideo API key as x-api-key: mv_live_....
• n8n nodes used: Manual Trigger, Set, Sticky Note, HTTP Request, and Split Out.
• Response handling: Splits body.data.scenes into scene items for easy downstream automation or inspection.