Write the dependency before choosing the interface
Several related outputs are not necessarily a production sequence. A sequence needs the next operation to consume the approved result of the previous operation. Write the required dependency in plain language: create a scene, approve that specific scene, then animate that scene. This is more precise than requesting a collection of product images and videos.
Kittl's Agentic AI help explicitly says sequenced generations are not supported in that version. Flows instead documents connected artboards, mockups and AI image or video boards. Dashboard AI Workflows are curated presets. Creative Agent is another feature and does not currently run named AI Workflows inside its chat.
Choose a route with an observable intermediate result
| Need | Route to evaluate | Evidence required |
|---|---|---|
| Explore an image or video direction | A suitable individual generation | The actual selected result |
| Feed an approved image into a later video | Connected Flows or explicit separate requests | Correct intermediate asset supplied downstream |
| Start from a guided preset | Dashboard AI Workflows | Preset description matches intended deliverable |
Do not skip creative approval between stages
In a fictional teapot campaign, a generated scene contains an attractive but incorrect lid. Connecting that image to animation would carry the error into the next stage. Review the lid, spout, handle and printed mark before approving the image as the motion reference. Connectivity does not establish product fidelity.
Keep an external record containing the source product, approved image version, intended movement and selected video output. If the image changes, decide explicitly whether the video should be regenerated. Do not infer that an existing animation automatically reflects a newly approved still.
Review the assembled deliverable
A generated video board is not necessarily a complete advertisement with captions, accurate voiceover, music rights and a destination-specific export. Plan those remaining steps separately. Compare the final motion with the approved still and the actual product, including any frames where new surfaces become visible.
Stop when the approved intermediate is identifiable and the downstream output passes its own review. This guide describes route selection from current primary documentation; it does not execute Kittl operations or claim that CartVisual supplies a Kittl connection.
Related production decisions
Continue with the adjacent checks when they apply: After Changing Packaging Artwork, Which Downstream Product Images and Videos Must I Regenerate?. Kittl Dashboard Mockups or Linked Artboard Mockups: Which Workflow Should You Start With?.