Problem
We are integrating AI-generated content, such as summaries and key points, into our stories through the Draft API using additional_properties. However, these properties are not natively available as editable fields in Composer, and external updates are not synchronized when a story is open for editing. This creates a risk of overwriting changes made by editors.
Existing Planning and Metadata fields are already used for established editorial purposes and are not suitable for storing this additional AI-generated content.
Requested enhancement
We would like Composer to support configurable custom metadata fields that can be displayed and edited directly in the Planning or Metadata tabs and synchronized through Draft API syncing when external processes update them.
This would allow us to integrate AI-generated content into our editorial workflow without repurposing existing fields or risking data loss during concurrent editing sessions.
Expected benefits
Support AI-generated summaries, key points, and other structured editorial data.
Allow editors to view and manage this content directly in Composer.
Synchronize external Draft API updates with open Composer sessions, including appropriate notifications and conflict handling.
Reduce the risk of overwriting editorial changes and enable safer integrations with external services.
This capability would provide a flexible and reliable way to extend Composer for new editorial use cases without requiring changes to existing fields or workflows.
Guest
