Zhipu Qingyan web / app · content and parameter brief
Follow the product controls
Download a template first. The controls below follow official references; labels can change between versions. See the linked product guide if a control differs. Choose a template →
- 01
Start a Qingyan chat
Sign in through chatglm.cn and start a conversation. This route prepares content; a GLM model or API does not itself grant access to your computer folders.
- 02
Provide editable fields
Paste the guide’s editable title, color, image-ratio and caption fields, or attach a readable guide where supported. Ask a production tool to extract unknown fields rather than guessing.
- 03
Fill the field table
Request field name, proposed content and missing-input status. Check required assets and prepare short alternatives for long titles.
- 04
Save and hand off
Keep the original field names in the final content table. Transfer it with the original package and assets to an execution tool, which should validate the actual input format.
Starting brief for 智谱清言 / GLM
Copy this, fill in the bracketed fields, and send it with the package path or readable guide.
Read the complete brief
Using the supplied MotionGit guide, prepare a table of field name, my content, constraints and missing inputs. Preserve actual field names, avoid invented parameters, and produce a complete production handoff. Topic: [fill in] Platform and aspect ratio: [fill in] Target duration: [fill in] Available copy, assets or audio: [fill in / none yet] For now, prepare content. Say if you cannot read a file or run the template; do not claim a rendered result. After approval, deliver the goal, template constraints, final copy, asset map, audio needs and missing items for the production tool.
After approving the copy, continue to production
Collect the goal, template constraints, one final copy version, asset filenames and purposes, audio needs and unfinished items. Give this brief, the original package and actual assets to one of these production tools for a real preview.
How do I review and export after production? →If you get stuck
It invents template parameters
Provide the actual guide and ask it to use only documented fields, labeling other ideas as suggestions. Let the execution tool validate the real contract.
The .motion file is rejected or unreadable?
Paste shareable template instructions and constraints to continue preparing content. Give the original to a production tool with file and command access, and keep packages containing personal keys private.
Full file handoff instructions →Official entries and references
References checked on 2026-10-31. Product homepages establish entry points; the content and handoff workflow is MotionGit guidance. Signed-in controls and availability vary by version, region and account. This is not certification of a full .motion export in every client.