What's the workflow used for？ Leverage this Kling API (unofficial) provided by PiAPI workflow to streamline virtual try-on video creation. This tool is designed for e-commerce platforms, fashion brands, content creators and content influencers. By uploading model and clothing images and linking PiAPI account, users can swiftly generate a realistic video of the model sporting the outfit with a 360° turn, offering an immersive viewing experience. Step-by-step Instruction For basic settings of virtual try-on, check API doc to get best practice. Fill in your X-API-Key of your PiAPI account in Preset Parameters node. Upload the model photo and provide target clothing image urls. Click Test Workflow to generate virtual try-on image. Get the video output in the final node. Param Settings If you want to change into a dress, input the model_input URL and the dress_input URL in the parameters. If you want to change into separates, input model_input URL, upper_input URL and lower_input URL in Preset Parameters. Use Case Input images： Output Video The output demonstrates that the model is wearing the clothing from the specified image and showcases a rotating runway-style view.
Tags
Related workflows
See all General Automation→Sync Shopify customers with Cegid Y2 on create or update
Quick overview This workflow receives Shopify customer create/update webhooks and syncs the customer record to CEGID Y2 by creating the customer when missing or updating the existing customer when CEGID reports a duplicate. How it works Receives a POST webhook from Shopify when a customer is created or updated. Builds a CEGID Y2 customer payload with identifiers, tax/currency details, and the default store/workspace settings. Formats the customer address and chooses whether to send individual or company contact details based on whether a company name is present. Sends the assembled payload to CEGID Y2 to create the customer. If CEGID returns a “customer already exists” error, extracts the existing CEGID customer ID from the error message and sends a PATCH request to update that customer in CEGID. If the create request fails for any other reason, stops the workflow and surfaces the CEGID error. Setup In Shopify, create a customer webhook for create/update events and point it to this workflow’s webhook URL, matching the allowed shop domain. Add CEGID Y2 HTTP Basic Auth credentials and ensure the API user has permission to create and update customers. Update the CEGID API base URL, wo
Proxy OpenAI-style chat completions to Gemini with async webhooks
Quick overview This workflow exposes an OpenAI-compatible /v1/chat/completions endpoint in n8n that forwards requests (including optional file attachments) to a configurable LLM HTTP provider, supporting both synchronous replies and asynchronous processing via a callback URL. How it works Receives a POST request on /v1/chat/completions via a webhook, accepting JSON or multipart form-data with optional binary file uploads. Converts any uploaded files into OpenAI-style message content (images as image_url data URLs and other files as text entries) and merges them into the last user message. Prepares a job ID, extracts optional callback and provider override settings (URL and headers), and keeps the original request body for later use. If a callback URL is provided, immediately returns HTTP 202 with the job ID, then sends the request (without callback/provider fields) to the configured LLM provider endpoint. Formats the provider response (or error) into a completion payload with a status code and posts the result to the callback URL with job metadata. If no callback URL is provided, sends the request to the LLM provider synchronously and returns the provider response (or error) to the
Send SAP Business One order and invoice alerts via WhatsApp Cloud API
Quick overview This workflow polls SAP Business One every 15 minutes for newly updated Sales Orders and AR Invoices and sends a formatted alert for each document via the WhatsApp Cloud API, using an n8n Data Table timestamp to prevent duplicate notifications between runs. How it works Runs every 15 minutes on a schedule. Reads the last-checked timestamp from an n8n Data Table and falls back to 15 minutes ago if no value exists. Logs in to the SAP Business One Service Layer and queries the Orders and Invoices OData endpoints for documents updated after the last-checked date. Normalizes the returned records, labels each one as a Sales Order or AR Invoice, and combines them into a single stream. For each new document found, formats a WhatsApp text message with key fields like document number, date, customer, total, currency, and comments. Sends the message through the WhatsApp Cloud API (Meta Graph) and then logs out of SAP Business One. Upserts the current timestamp back into the Data Table so the next run only alerts on newer documents. Setup Provide your SAP Business One Service Layer URL and credentials (CompanyDB, UserName, Password) in the SAP login request and ensure the Orders