AI agent for Adobe Experience Platform: schemas, datasets and audiences
Adobe Experience Platform connects on its own card with an OAuth Server-to-Server credential and one sandbox. The agent reads sandboxes, XDM schemas, datasets and audiences, creates audiences and schemas with your approval, and holds data ingestion, dataflows, destinations, merge policies and deletes for a person.
Connecting Adobe Experience Platform
- 1In Adobe Developer Console open a project (or create one), add the Experience Platform API API and choose OAuth Server-to-Server. In Adobe Admin Console add that credential to the Experience Platform product profile it should use — the profile decides what it may read and change.
- 2Give that profile the permissions the agent needs: Sandboxes (which sandboxes it reaches), Data Modeling (schemas and field groups), Data Management (datasets), Profile Management (audiences and merge policies), Identity Management (namespaces).
- 3Open Integrations → the Adobe Experience Platform card → Connect. Paste the project JSON or type the Client ID, secret and IMS Organization ID (it ends in
@AdobeOrg). - 4Press Test connection (the sandbox list and one schema-registry read), pick the sandbox, and Save connection.
openid, AdobeID, read_organizations, additional_info.projectedProductContext, session. One connection works in one sandbox; a call can name another sandbox the credential reaches.What the agent does in Experience Platform
- Sandboxes: lists the production and development sandboxes the credential reaches.
- Schemas: XDM schemas of the tenant or the global container, with their class and version; any Schema Registry read with the right Accept header set for you.
- Datasets: name, schema, tags and last batch.
- Audiences: segment definitions with their PQL expression, evaluation (batch, streaming, edge), merge policy and status.
- Anything else documented under data/ through the Experience Platform read gateway — catalog, identity, flow service status.
What it changes — and what waits for a person
- Ordinary changes follow your approval setting (by default each waits for your approval card): a new audience, a schema or field group, an identity namespace, dataset tags.
- Always a person: data ingestion (data/foundation/import), dataflows and destinations (flow service), merge policies, Profile system jobs, Query Service statements, and every delete. Activating an audience to a destination is a dataflow, so it waits for a person.
- Refused: sandboxes, access control, privacy and data-hygiene jobs, and the Catalog's multi-request root (each change is sent and judged on its own).
What we measured with a real Adobe organization
- The sandbox list wants its trailing slash (
data/foundation/sandbox-management/404s without it) — set for you. - Schema Registry has its own Accept headers (a list wants xed-id, one resource xed); a plain JSON Accept answered 400. The read tools send the right one per path.
- A schema was created, changed with a JSON Patch, read back and deleted; a field group created and deleted (2026-11-11).
- The product profile decides the rest: datasets answered 403 without Data Management, audiences and merge policies 401 "RBAC Unauthorized" without Profile Management, and Query Service 403. The tools name the missing permission.
Things to ask
- "Which schemas in our prod sandbox use the Individual Profile class?"
- "List the streaming audiences and their PQL expressions."
- "Which datasets have not received a batch in the last 7 days?"
- "Create an audience of profiles in the US who bought in the last 30 days — show me the PQL first."
Frequently asked questions
- Does Agent Planners support Adobe Experience Platform?
- Yes. Experience Platform is its own integration: connect it with your own Adobe OAuth Server-to-Server credential and a sandbox, and the agent reads schemas, datasets and audiences and proposes audiences and schemas for your approval.
- Can the agent activate an audience to a destination?
- Only with a person's approval, every time: activation is a dataflow, and moving data into or out of Experience Platform waits for a person on every lane.
- Why do datasets or audiences say missing permissions?
- The credential's Experience Platform product profile lacks Data Management (datasets) or Profile Management (audiences, merge policies). Add the permission in Adobe Admin Console and press Test connection.
- Can it touch sandboxes or privacy jobs?
- No. Sandboxes, access control, privacy and data-hygiene jobs are refused on every lane — they stay in Adobe.