Parks wants a seasonal copy generator that sends drafts into the department CMS through an API. Which Foundry generative-app approach fits?

Using Foundry connectors so the generative workflow can post drafts to the CMS draft API fits Parks' seasonal copy generator. Generative value in municipal content operations comes from landing drafts where editors already review, schedule, and publish. Connectors bridge the Foundry workflow to the CMS draft endpoint so seasonal event and program copy is created as CMS draft objects rather than stranded in chat transcripts or email threads that bypass editorial workflow. Exposing seasonal copy via a Foundry prompt flow endpoint for the CMS draft API to poll does not post drafts into the CMS; it leaves the CMS to pull copy on demand instead of the workflow pushing drafts straight to the CMS draft API via connectors. Using Foundry model endpoints so the chat workflow can post drafts to the CMS draft API is a model-hosting inference step, not the API integration that posts drafts into the CMS draft API. Using Foundry tracing spans so the observed workflow can post drafts to the CMS draft API is an observability step, not the connector-based posting of drafts to the CMS draft API that Parks needs. Exam caveat: Foundry generative applications often integrate to line-of-business systems through connectors and APIs specifically for draft handoff into existing editorial systems. Operational check: run the seasonal workflow end-to-end and confirm a CMS draft object is created via the connector with expected title, body, and metadata fields; revoke connector permissions and confirm posts fail closed without silent data loss or partial publishes.