> ## Documentation Index
> Fetch the complete documentation index at: https://docs.agentforcemcp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Creative Asset Workflow Automation with ACP

> Streamlining creative asset management and utilization from Adobe Workfront to Marketing Cloud using ACP.

## Scenario

A marketing team uses Adobe Workfront to manage their creative asset development and approvals. Once assets (like images, videos, or copy) are finalized, they need to be efficiently transferred or made available to Marketing Cloud Engagement (MCE) for use in campaigns. This process often involves manual downloads, uploads, and coordination, leading to delays and potential errors. The goal is to automate this workflow using Agentforce agents and ACP.

## Actors

* Creative Team / Project Manager (using Adobe Workfront)
* Marketing Campaign Manager (using Marketing Cloud)
* Agentforce Agent (powered by ACP)

## ACP Components Involved

* **Adobe Workfront Connector:**
  * `workfront_query_projects` (or similar): To find projects or tasks.
  * `workfront_list_documents` (or similar): To list documents/assets associated with a project or task.
  * `workfront_get_document_details`: To retrieve metadata about an asset.
  * `workfront_download_document`: To download an asset.
  * `workfront_get_asset_public_url` (if available/applicable): To get a direct link to an asset.
* **Marketing Cloud Engagement (MCE) Connector:**
  * `mce_upload_asset_to_content_builder` (or similar): To upload assets into MCE Content Builder.
  * `mce_create_content_block` (if creating specific blocks from assets): To create reusable content blocks.
  * `mce_update_email_with_asset`: To incorporate the asset into an email template.
* **(Optional) Generative AI Connector (e.g., Adobe Gen Studio, or other):**
  * `genai_create_image_variant`: To generate variations of an image.
  * `genai_summarize_text`: To create shorter copy from longer text assets.

*(Tool names are illustrative and will depend on the final ACP connector implementation.)*

```mermaid theme={null}
sequenceDiagram
    participant CW as Creative Team (Workfront)
    participant AFA as Agentforce Agent (ACP)
    participant AW as Adobe Workfront
    participant MCE as Marketing Cloud Engagement
    participant MCM as Marketing Campaign Manager
    participant GAI as (Optional) GenAI Service

    CW->>AW: Finalizes Asset (Status: Approved)
    alt Proactive Agent
        AFA->>AW: Periodically queries for approved assets
        AW-->>AFA: Approved Asset(s) details
    else User Triggered
        MCM->>AFA: Instructs to fetch assets
        AFA->>AW: Queries for specific assets
        AW-->>AFA: Asset(s) details
    end

    AFA->>AW: Retrieves asset (download/URL)
    AW-->>AFA: Asset data/link

    opt Asset Transformation
        AFA->>GAI: Sends asset for transformation
        GAI-->>AFA: Transformed asset
    end

    AFA->>MCE: Uploads asset to Content Builder
    MCE-->>AFA: Upload confirmation
    opt Create Content Block
        AFA->>MCE: Creates content block with asset
        MCE-->>AFA: Block creation confirmation
    end

    AFA->>MCM: Notifies asset availability (e.g., Slack)
    MCM->>MCE: Uses asset in campaigns
```

## Workflow

1. **Asset Finalization in Workfront:** The Creative Team finalizes an asset in Adobe Workfront (e.g., an image for an upcoming promotion) and marks its status as "Approved for Campaign."
2. **Agent Notification/Trigger:**
   * **(Option A - Proactive Agent):** An Agentforce agent periodically queries Workfront (using `workfront_query_projects` or a dedicated "approved assets" tool) for newly approved assets.
   * **(Option B - User-Triggered):** A Marketing Manager instructs the Agentforce agent: "Fetch the latest approved assets for the 'Summer Sale' campaign from Workfront."
3. **Asset Retrieval (Workfront):**
   * The agent uses `workfront_list_documents` to find the specific asset(s) based on project name, task, or approval status.
   * It then uses `workfront_download_document` (or `workfront_get_asset_public_url`) to retrieve the asset.
4. **(Optional) Asset Transformation (Generative AI):**
   * If needed, the agent could use a Generative AI connector. For example, if a banner image is retrieved, `genai_create_image_variant` could be used to create versions for different social media platforms. Or, if a long product description is retrieved, `genai_summarize_text` could create a shorter version for an email.
5. **Asset Ingestion into MCE:**
   * The agent uses `mce_upload_asset_to_content_builder` to upload the (potentially transformed) asset into Marketing Cloud Content Builder.
   * Optionally, the agent could use `mce_create_content_block` to create a specific content block (e.g., an image block) using the uploaded asset.
6. **Notification & Availability:**
   * The agent notifies the Marketing Campaign Manager (e.g., via Slack, Email, or a Salesforce Task) that the new asset is available in MCE Content Builder, providing a link or asset name.
   * The asset is now ready to be easily dragged into email templates or used in journeys.

## Key Outcomes & Benefits

* **Reduced Manual Effort:** Eliminates the need for manual downloading from Workfront and uploading to MCE.
* **Faster Campaign Execution:** Assets become available in MCE much quicker, speeding up the campaign creation lifecycle.
* **Improved Consistency:** Ensures the correct, approved versions of assets are used in marketing campaigns.
* **Error Reduction:** Minimizes errors associated with manual file handling.
* **Enhanced Collaboration:** Streamlines the handoff between creative and marketing operations teams.
* **Potential for Intelligent Asset Adaptation:** With an optional Generative AI step, assets can be automatically tailored for different channels or uses.

This use case highlights how ACP can bridge the gap between creative production systems like Adobe Workfront and marketing execution platforms like MCE, creating a more seamless and efficient end-to-end content pipeline.