Draft from a structured content record.
Create from structured facts and review proposed changes.
Start creating in Chat ↗Draft from one structured source
Illustrative coffee blend record: select the fields the product description should use.
Choose the record
Open the collection, inspect the current name, origin and approved details, then select that record as visible context for the writing request.
Review the result
Check the saved description against those fields. A generated suggestion to change the record is a separate proposal to review before saving.
The draft and the record are different artifacts
If the source changes before a reviewed run, refresh and inspect the current revision rather than assuming the old fields still apply. See Content context or collection management.
See an example workflow
An illustrative example. Review current inputs, settings and the quote in your workspace.
- StartSelect the exact current coffee-blend record.
- Request or actionChoose Writing and request a description from its fields.
- ReviewCheck name, origin and price against the selected record.
- Saved resultA saved description; the record remains separate.
- ContinueReview any proposed record edit before saving it.
Example AskGL request
Write a two-sentence description of this blend using only the selected record’s name, origin and approved tasting notes.
Replace sample facts with approved details. Source selection and later review, comparison or packaging happen in the workspace, outside the prompt text.
Continue the workflow
Use Knowledge in chat
Bring relevant guidance into a reviewed request.
Explore ↗Write in chat
Draft text, then continue from the saved document.
Explore ↗Content context
See a selected record used in a reviewed writing request.
Explore ↗Content collections
Learn how structured records and proposed updates stay separate.
Explore ↗Good to know.
Creation notes
Prepare your starting point
Choose the intended current record and inspect its fields before preparation. Ask for a defined draft format from its approved facts. Refresh context if the record changed, and omit missing information instead of requesting a plausible price, date or product claim.
Content recordsReview what you keep
Compare every statement with the selected fields. A proposed record update is its own decision with a save flow; useful generated writing does not authorize changing factual source data. Keep the accepted draft and current record recognizable for the next request.
Knowledge for creationCommon questions
Is every catalog capability enabled?
No. Catalog candidates, registered integrations and currently enabled workspace choices are different. Check support stage and the actual preparation controls.
How should I choose the next tool?
Use the contextual links for the source, artifact or decision you have now. A feature explains a tool, a workflow explains its steps and an output guide explains the saved result.