Integration · Docs and data
AI agents for Adobe Experience Manager
List, search, read, create, update and publish Content Fragments and list their models on an AEM as a Cloud Service author environment, through the OpenAPI-based AEM Sites API, with an OAuth Server-to-Server credential.
- Actions
- 7
- Read
- 4
- Write
- 3
Actions
What your agents can do in Adobe Experience Manager
7 actions. Each one is a tool your agents can call and a step your workflows can run.
Read 4
Look things up. Nothing changes.
List Content Fragments
Lists Content Fragments under a DAM folder (like /content/dam/wknd/en), up to 50 at a time, as items.
Search Content Fragments
Finds Content Fragments matching a filter, newest change first, up to 50 at a time, as items (like List Content Fragments) and a cursor.
Get a Content Fragment
Reads one Content Fragment by its ID: title, description, path, status, model, fields (each with name, type, multiple and values), variations, tags and etag (needed to update it).
List Content Fragment models
Lists the Content Fragment models, as items: each with its id (what Create a Content Fragment needs), name, path, description, status and, unless summary is set, its fields.
Write 3
Create, change or send.
Create a Content Fragment
Creates a Content Fragment from a model in a DAM folder.
Update a Content Fragment
Replaces a Content Fragment's title, description and field values.
Publish Content Fragments
Publishes up to 50 Content Fragments, by ID or by path, to the publish tier (live) or the preview tier.
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Enter the sign-in details Adobe Experience Manager gives you for its API.
What you enter
- Client ID
- Client secret
Settings
- Author environment
- Scopes
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your Adobe Experience Manager data
Ask a question in plain words. The agent can list Content Fragments, search Content Fragments or get a Content Fragment in Adobe Experience Manager, then answers with what it found.
- 02
Let an agent update Adobe Experience Manager
Have the agent create a Content Fragment or update a Content Fragment in Adobe Experience Manager as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Share what it finds in Slack
Give one agent Adobe Experience Manager and Slack: it can list Content Fragments in Adobe Experience Manager and post a summary to a Slack channel in the same run.
Works well with
More Docs and data tools
- Google Sheets3 actionsAdd rows to a Google Sheets spreadsheet, read a range of cells, and write over a range, signed in with the person's own Google account.
- Google Docs3 actionsCreate Google Docs documents, read their text, and add text to the end of them, signed in with the person's own Google account.
- Notion4 actionsAdd pages to Notion databases, append text to pages, query databases and search the pages shared with an internal integration.
- Confluence4 actionsCreate, read and search Confluence Cloud pages on your Atlassian site, signed in with an email address and an API token.
- Airtable4 actionsCreate, update, list and read records in Airtable bases that a personal access token can reach.
- Docusign3 actionsSend documents for signature from a Docusign template, check an envelope's status and list recent envelopes, as the person who connects.
FAQ
Adobe Experience Manager and MyDeepAgents
Can MyDeepAgents connect to Adobe Experience Manager?
Yes. The Adobe Experience Manager connector has 7 actions: 4 read and 3 make changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Adobe Experience Manager?
Enter the sign-in details Adobe Experience Manager gives you for its API. You'll need: Client ID and Client secret. The connection also asks for: Author environment and Scopes. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in Adobe Experience Manager without asking?
Only if you let it. Each of the 3 actions that change data can be set to wait for a person's approval before it runs.
Can I use Adobe Experience Manager in workflows as well as agents?
Yes. Every Adobe Experience Manager action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Adobe Experience Manager to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.