Skip to main content
After you connect your Adobe Experience Manager (AEM) account, the following nodes become available in Profound Agents. Use them to find, read, create, and update AEM Content Fragments. All operations run against the connected AEM Author environment and use the permissions assigned to the OAuth credential’s technical account.

Available nodes

List Content Fragments

Retrieve Content Fragments from the connected Author environment.

Required inputs

  • AEM Instance — the connected Author environment

Optional inputs

  • Folder — limits the list to an approved folder below /content/dam
  • References — controls whether linked fragments are returned and hydrated
  • Limit — number of results to return; the default is 25 and the maximum is 50
  • Cursor — a pagination cursor from a previous List or Search node’s output, used to fetch the next page of results
  • Projection — use summary when you need summary data only

Output

The output contains the matching Content Fragments and, when more results are available, a pagination cursor for the next page.

Key concepts

AEM Instance

The connected AEM Author environment. Select it before choosing a model, folder, or fragment.

Content Fragment Model

The AEM schema that defines a fragment’s fields, types, required values, and allowed content. The model must be enabled and allowed by the destination folder’s policy.

DAM paths

Content Fragment folders use repository paths below /content/dam. Folder permissions and policies control which content Profound can read or change.

Content Fragment ID

AEM API operations identify a Content Fragment by UUID. Profound’s picker displays searchable fragment information and supplies the UUID to the node.

ETag

An ETag is a unique identifier for a specific version of a Content Fragment’s data. Pass it from a Get Content Fragment node to the Update Content Fragment node to prevent the workflow from silently overwriting a change made after the fragment was read.

Pagination

List and Search nodes return up to 50 fragments per request. When the output contains a cursor, provide it to the next List or Search node to retrieve the next page of results.

Hydrated Content Fragment

A Content Fragment that contains its full field values, rather than only basic IDs and URLs.

References

References control how linked fragments are included. Hydrated and all-reference modes can return larger responses, so use them only when the workflow needs linked content.

Troubleshooting

A folder, fragment, or model picker is disabled or empty

Select an AEM Instance first. If the picker stays empty, verify that your OAuth credential’s technical account can read the corresponding model, folder, or fragment. Learn more in the setup troubleshooting guide.

Search returns an invalid-query error

Restore the Folder filter to /content/dam or add another filter. When using Raw Query, include a non-empty JSON object and use Adobe-supported filter and sort fields.

Create node reports an unknown field or invalid value

Select the model and use Structured format when possible. If you have to use Raw JSON format, make sure each key matches the AEM model field name and provide a value with the model’s expected type and cardinality.

Update node reports that there are no changes

Enter at least one Title, Description, or model field value. Empty inputs preserve the current content.

Update node reports a conflict

The fragment changed after AEM issued the ETag. Run the Get Content Fragment node again, review the latest content, then apply the update with the new ETag.

A node returns a permissions error

Confirm that the technical account’s service group has permission for that exact operation and DAM path. Read access can succeed while Create or Update remains blocked. To add permissions for specific folders and files in your AEM environment, follow Adobe’s Product Profile and Services user group permission management guide.

Only the first page of results is returned

Use the cursor returned by the List or Search node as the next request’s Cursor. Each page can contain no more than 50 results.

Additional resources