Claude Adobe Journey Optimizer connectorWhat Claude can do in your Adobe Journey Optimizer account.
The Claude Adobe Journey Optimizer connector exposes 7 tools, and all 7 only read. That means 0 tools that write and 0 left undocumented. Below: what Claude can inspect in your campaigns and journeys, what this beta does not touch, and which settings decide what it sees.
Verified Trustpilot reviews · AI, automation & growth agency
Why plug Journey Optimizer into a chat
Journey Optimizer answers a lot of questions, but each one sits behind a different screen. With the connector on, you type the question and Claude opens the campaign, the journey or the channel setup for you, then explains what it found in plain sentences. Adobe states that every tool of this server only reads.
Find what is stuck before the send date. A CRM manager asks which campaigns are live and which stopped: ajo_list_campaigns filters by status (draft, live, stopped, completed), and ajo_get_campaign then opens one to show audience, schedule, channel and content settings.
Explain a journey to someone who did not build it. ajo_get_journey returns the branches, conditions and actions of one journey, so Claude can walk a new teammate through it step by step.
Check a channel before you reuse it. ajo_list_channel_configurations covers email, push, WhatsApp, direct mail, web and more, filtered by name, status or type, which helps when a sender setup looks wrong.
What it will not do: in this beta, Adobe states that creating, updating or deleting objects is not supported, so Claude cannot launch, pause or fix a campaign for you. Nothing runs on its own either. Claude reads only when you ask, during the conversation. For another Adobe connector, see the Claude adobe-workfront connector.
The words you will meet
Five terms, one line each.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can look into it while it answers you.
- Tool
- A single named capability the connector gives Claude. Claude picks which ones to call by itself; the directory lists them by name.
- Authorization
- Adobe's own sign-in screen, where you grant the access Claude will use. Each person grants it once and can take it back.
- Approval
- The confirmation Claude waits for before a step that changes an account. It appears in the chat, right when it is needed.
- MCP
- The open standard connectors are built on: the piece that lets an assistant like Claude query an outside service such as Adobe.
Set up the Claude Adobe Journey Optimizer connector
- 01
Open the connector list
In Claude's settings, go to Customize, then Connectors, and search for Adobe Journey Optimizer. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it first; members then sign in one by one.
- 02
Sign in on the Adobe side
Press Connect on its row. The sign-in window that opens belongs to the service, not to Claude. If the connection breaks later, Disconnect and connect again, or withdraw the access from the service account.
- 03
Read what you authorize
Go through the authorization screen before you accept. That screen, not Claude, sets what the access covers. It can sound broader than what Claude does day to day; per-action approval stays the default rule in Claude.
The 7 tools, all on the reading side
Adobe Journey Optimizer gives Claude 7 tools: 7 that read your account, 0 that change something in it.
Every tool below reads. Adobe's page says so for the whole server, and four of them also have their own line in Adobe's documentation. Names stay exactly as Claude displays them.
- 7 read
What Claude reads (7)
7 toolsSeven tools that consult your Journey Optimizer data without changing anything.
ajo_list_sandboxes
Adobe classes it with the rest of the server as read-only, yet no line of its documentation says what it returns. We therefore stay with that classification and add nothing to it.
ajo_list_campaigns
Pulls the list of your marketing campaigns and can narrow it by status: draft, live, stopped or completed. Claude gets an overview it can count, sort or summarize for you.
ajo_get_campaign
Opens a single campaign by its ID and brings back its full setup: audience targeting, schedule, channel and content settings. Claude can then read it back to you or flag what looks odd.
ajo_list_journeys
Covered by Adobe's statement that every tool of this server is read-only. Adobe's tool table, however, has no row under this exact name, so what the list contains is not documented.
ajo_get_journey
Retrieves one journey by ID with everything that shapes it: its branches, the conditions on each path and the actions it triggers. Claude turns that structure into a readable walkthrough.
ajo_list_channel_configurations
Returns channel configurations filtered by name, status (draft, active, archived, deactivated) or channel type, across email, push, WhatsApp, direct mail, in-app, web, LINE and others.
ajo_get_loyalty_challenges
Falls under the read-only rule Adobe gives for the whole server. Adobe's documentation describes no output for it, and nothing else on its page matches this name.
Approvals and who controls access
With seven reading tools, there is nothing here that sends, edits or deletes. The approval rules still matter, because they decide what a connector may ever do in your organization.
By default, Claude pauses and asks before any action it would take on an account for you. On Team and Enterprise, owners choose whether members may skip that prompt for some actions, and they can limit a connector organization-wide, for example to reading only; no member overrides that from their own account. Claude also inherits the rights of the person who connected: Adobe says you need at least View permissions on the objects you query, so what you cannot open in Journey Optimizer stays out of reach.
Plans: what is published and what is not
Plan availability for this connector is published nowhere. None of the 819 directory sheets lists plans, and this one is no exception.
The general rule from Anthropic: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner turns a connector on for the organization before members can connect. For this connector's current state, check its sheet in the official directory. Only Adobe documents it; no Claude help article covers it.
What this beta leaves out
A connector is not an automation. Claude calls these tools while it answers you; nothing fires when a journey stops or a campaign goes live.
Read-only here is what the sheet shows today, not a lifetime promise: an administrator can open actions that no public sheet lists. The partner badge is not a security audit, and Anthropic warns on every sheet that it neither chooses a publisher's tools nor guarantees how they behave. Adobe adds its own warnings: the server is in beta, its documentation is not final, and it recommends testing in a sandbox before production. For the other platforms we cover, start from the Integrations hub.
How many tools does the connector really expose?
- Claude directory sheet ↗2026-10-017 tools, including ajo_list_sandboxes and ajo_get_loyalty_challenges.
- Adobe Experience League ↗2026-09-13Ten tools by display label, including a journey visualizer, configuration resources and marketing actions that the sheet does not show.
What this page followsThe two lists do not match. We follow the directory sheet, read most recently, for what Claude exposes; the real list shows in Claude once the connector is on.
Need help connecting Adobe Journey Optimizer to Claude?
A person reads every message.
