n8n Workflow: Generate 360° Virtual Try-On Videos for Clothing with Kling API (Unofficial)

This n8n workflow provides a framework for generating 360° virtual try-on videos for clothing items using an unofficial Kling API. It outlines the general steps involved in making API requests, handling responses, and incorporating delays for asynchronous operations.

What it does

This workflow demonstrates a common pattern for interacting with APIs that involve asynchronous processing:

1. Manual Trigger: Initiates the workflow upon a manual execution.
2. Edit Fields (Set): Prepares the data for the API request by setting or modifying fields.
3. HTTP Request (Generate Video): Makes an initial API call to the Kling API to request the generation of a 360° virtual try-on video.
4. Wait: Pauses the workflow for a specified duration to allow the video generation process to complete on the API's side. This is crucial for asynchronous operations.
5. HTTP Request (Check Status): After the wait period, it makes another API call to check the status of the video generation.
6. If: Evaluates the status returned by the API.
   • True Branch: If the video generation is successful, it proceeds to further processing (not explicitly defined in this basic template, but would typically involve downloading the video or updating a database).
   • False Branch: If the video generation is not yet complete or failed, it can be configured to retry or log an error.
7. Switch: (Currently unused in the provided JSON, but typically used for multi-conditional routing based on different API response values or other data.)
8. Sticky Note: Provides a placeholder for comments or instructions within the workflow.

Prerequisites/Requirements

• n8n Instance: A running n8n instance to import and execute the workflow.
• Kling API Access: Access to the unofficial Kling API for 360° virtual try-on video generation. You will need the API endpoint URLs and any necessary authentication details (API keys, tokens, etc.).
• Understanding of Kling API: Knowledge of the Kling API's request format for video generation and its response structure for checking status.

Setup/Usage

1. Import the Workflow:
   • Download the provided JSON content.
   • In your n8n instance, click "Workflows" in the left sidebar.
   • Click "New" or the "+" icon, then select "Import from JSON".
   • Paste the JSON content and click "Import".
2. Configure API Endpoints and Data:
   • Edit Fields (Set): Modify this node to include the necessary data for your Kling API video generation request (e.g., clothing item ID, model ID, desired output format).
   • HTTP Request (Generate Video):
     • Update the "URL" field with the correct Kling API endpoint for initiating video generation.
     • Configure the "Method" (e.g., POST) and "Body" with the data from the "Edit Fields" node.
     • Add any required "Headers" for authentication (e.g., Authorization: Bearer YOUR_API_KEY).
   • Wait: Adjust the "Time to Wait" value based on the typical processing time of the Kling API. Start with a conservative estimate and adjust as needed.
   • HTTP Request (Check Status):
     • Update the "URL" field with the correct Kling API endpoint for checking video status (this might involve a job ID obtained from the initial generation request).
     • Configure "Method" (e.g., GET) and "Headers" for authentication.
   • If:
     • Configure the "Conditions" to evaluate the response from the "HTTP Request (Check Status)" node. For example, you might check if {{ $json.status === 'completed' }} or {{ $json.videoUrl }} exists.
3. Extend Workflow Logic (Optional):
   • True Branch of If Node: Add nodes to handle successful video generation (e.g., another HTTP Request to download the video, a Google Drive node to upload it, a Slack node to send a notification).
   • False Branch of If Node: Add nodes for error handling or retries (e.g., a Loop node to retry checking status after another delay, a Send Email node to alert an administrator).
4. Activate the Workflow: Once configured, activate the workflow by toggling the "Active" switch in the top right corner of the workflow editor.
5. Execute: You can manually trigger the workflow by clicking "Execute Workflow" in the editor for testing. For production, you might connect this to a webhook or a schedule trigger.