Coworker for content management content-management-coworker-skills

On this page: Discover the CX Enterprise Coworker content management tools available in Adobe Journey Optimizer — to browse, create, update, clone, and publish content templates, fragments, landing pages, and journey/campaign inline content — with detailed guidance, example prompts, and best practices.

Learn more:

Content Management tools content-management

AVAILABILITY
Content Management is available for all customers who have access to Coworker.

Journey Optimizer users are able to discover and manage content assets — content templates, fragments, landing pages, and journey/campaign inline message content — directly from Coworker using natural language prompts. It lets you go from “tell me about my content” to “go build, update, and publish it,” without leaving the conversation. This capability is powered by 15 read and write-capable MCP tools for Journey Optimizer content.

Key use cases

  1. Browse and inspect content

    • List available content templates, fragments, or landing pages, and retrieve their structure, metadata, and status.
    • Retrieve the inline message content configured on a journey or campaign action node.

    Sample prompts:

    • “List my email content templates.”
    • “Show me the fragments available for my summer campaign.”
    • “Get the details of landing page page-123.”
    • “What content is configured for the email variant of the action node in campaign camp-789?”
  2. Create content templates

    • Create a new content template for any channel.

    Sample prompts:

    • “Create an email template named Summer Sale with this HTML content.”
    • “Create a new SMS template called Flash Alert.”
  3. Update content templates

    • Fully replace the content of an existing template.

    Sample prompts:

    • “Update template abc-123 with this new HTML body.”
  4. Create, update, clone, and publish fragments

    • Create a new HTML or expression fragment.
    • Update an existing fragment’s content or metadata.
    • Clone an existing fragment under a new name.
    • Submit a draft fragment for publication.

    Sample prompts:

    • “Create an HTML fragment named Promo Banner with this markup.”
    • “Update fragment frag-456 to change its name to Promo Banner V2.”
    • “Clone fragment abc-123 as Promo Banner - Summer (Variant B).”
    • “Publish fragment frag-456.”
  5. Update inline message content

    • Replace one channel variant on a campaign or journey action node’s inline message.
    • List the channel variants defined on a journey or campaign action node.

    Sample prompts:

    • “Update the email variant of the action node in campaign camp-789 with this new content.”
    • “What channel variants are defined on this action node?”

In scope

The following capabilities are supported by Content Management:

  • List and get content templates: Browse content templates and retrieve their structure and metadata.
  • List and get fragments: Browse content and expression fragments and retrieve their details.
  • List and get landing pages: Browse landing pages and retrieve their metadata and page content.
  • Get campaign/journey inline content: Retrieve the inline message content configured on a campaign or journey action node, including multi-lingual variants.
  • Create content templates: Create a new template for any channel.
  • Update content templates: Fully replace the content of an existing template.
  • Create, update, clone, and publish fragments: Create new fragments, update existing ones, clone a fragment under a new name, and submit a draft fragment for publication.
  • Update inline message content: Replace a channel variant on a campaign/journey action node’s inline message, including multi-lingual variants, and list the channel variants defined on an action node.

Out of scope

The following functionalities are currently not supported:

  • Full-text search across templates or fragments
  • Template or fragment validation (orphaned references, broken links, deprecated components)
  • Creating or publishing landing pages
  • Deleting content templates, fragments, or landing pages

Prompting best practices

  1. Reference IDs when known: Provide the template, fragment, landing page, or campaign/journey ID when asking to get, update, clone, or publish a specific asset.
  2. Be explicit about the channel: When creating a template or fragment, specify the channel or content type (email, HTML fragment, expression fragment).
  3. Confirm before publishing: Review a fragment’s content after creating or updating it before asking Coworker to publish it.
  4. Provide complete replacement content: Update operations replace content in full, so include the complete HTML body or variant content in your prompt.
AI Knowledge Reference

This section contains structured knowledge intended to support interpretation, retrieval, and question answering related to this topic.

For complete understanding, this information should be combined with the documentation on this page. Neither source is intended to stand alone; the page describes the feature, while this section provides additional context that helps disambiguate terminology, intent, applicability, and constraints.

  • TL;DR: This page documents the CX Coworker Content Management tools in Adobe Journey Optimizer, which use 15 read and write-capable MCP tools to discover, create, update, clone, and publish content templates, fragments, landing pages, and journey/campaign inline message content through natural language prompts.

Intents

  • Browse and inspect content templates, fragments, landing pages, and campaign/journey inline message content.
  • Create a new content template or fragment for a channel.
  • Update an existing content template, or update, clone, or publish a fragment.
  • Update a channel variant of a campaign or journey action node’s inline message content.
  • Learn which content management capabilities are not supported, such as deletion or full-text search.

Glossary

  • Content Management tools (product-specific): CX Coworker capability, powered by 15 read and write-capable MCP tools, that discovers and manages content templates, fragments, landing pages, and journey/campaign inline message content using natural language prompts.
  • Fragment: an HTML or expression content asset that can be created, updated, cloned, or published through Content Management tools.
  • Inline message content: the channel variant content configured on a journey or campaign action node, retrievable and updatable through Content Management tools.

Guardrails

  • Content Management is available for all customers who have access to CX Coworker.
  • Update operations replace content in full — provide the complete HTML body or variant content in the prompt.
  • Content Management tools do not support full-text search across templates or fragments, template or fragment validation (orphaned references, broken links, deprecated components), creating or publishing landing pages, or deleting content templates, fragments, or landing pages.

Terminology

  • Do not confuse: “content templates” (create and update, full-channel assets) are managed differently from “fragments” (create, update, clone, and publish) and “inline message content” (update a channel variant only) — each has its own set of supported operations on this page.

FAQ

  • How many MCP tools power Content Management in CX Coworker? 15 read and write-capable MCP tools.
  • Can Content Management tools delete a content template, fragment, or landing page? No, deleting content templates, fragments, or landing pages is not supported.
  • Can Content Management tools create or publish a landing page? No, creating or publishing landing pages is not supported.
  • Can a fragment be cloned under a new name? Yes, cloning an existing fragment under a new name is a supported capability.
  • What should I do before asking Coworker to publish a fragment? Review the fragment’s content after creating or updating it, before asking Coworker to publish it.
recommendation-more-help
journey-optimizer-help