Skip to main content
Connect Adobe Experience Manager (AEM) to Profound and let Agents find, read, create, and update Content Fragments directly in your AEM as a Cloud Service instance. The integration authenticates with an Adobe OAuth server-to-server (S2S) credential, so Agents work with your content without an individual user login.

​
Why the Adobe Experience Manager (S2S) integration exists

Enterprise content teams manage thousands of structured Content Fragments in AEM. When Profound surfaces a content gap or an outdated claim in AI answers, acting on it means exporting the insight, finding the right fragment in AEM, and editing it by hand. This integration closes that loop: Agents read your existing fragments, create new ones, and push updates back to AEM without leaving Profound.

​
Using Adobe Experience Manager nodes in Profound Agents

Build Agents that audit, refresh, and update AEM content based on Profound insights.
Follow Profound’s  AEM Integration Setup Guide to set up your Adobe Experience Manager (S2S) integration and make AEM nodes available to Agents.
Agent nodes available for Adobe Experience Manager include:
  • List Content Fragments — lists the Content Fragments in a folder of your AEM instance
  • Get Content Fragment — reads the full content of a specific Content Fragment
  • Create Content Fragment — creates a new Content Fragment in your AEM instance
  • Update Content Fragment — updates the content of an existing Content Fragment
Learn more about the nodes, configuration and troubleshooting in the Using Adobe Experience Manager in Agents guide in Profound developer documentation.

​
Example Agent: product FAQ refresh

This Agent keeps your AEM-hosted product FAQs aligned with your current messaging. It writes revised copy back to AEM, then posts a Slack summary so your content team can review and publish the changes.
  1. AEM - List Content Fragments: Point the node at the AEM folder that holds the Content Fragments for the FAQ you want to review. The node returns the fragments with their identifiers.
  2. ​Code node: Turn the output of the previous step into the list the Iteration node can use.
  3. Iteration node: Loop over the list of fragments, run the following steps for each, and return the list of updated AEM Content Fragments
    1. AEM - Get Content Fragment: Read the fragment’s full content.
    2. Prompt LLM node with the Use Knowledge Base option enabled: Compare the fragment’s copy against your Knowledge Base. Return revised copy and a flag indicating whether the fragment needs changes.
    3. Conditional node: If the fragment needs no changes, move on to the next fragment. If it does, continue to the next step.
    4. AEM - Update Content Fragment: Write the revised copy back to the fragment in AEM.
  4. Slack: After the loop finishes, post the list of updated fragments returned by the Iteration node to your content team’s Slack channel so they can review and publish the changes in AEM.
Schedule this Agent to run once or twice a week so your product FAQ content stays current.