12.2 AgentExchange: Extending an Org with the Agentforce Marketplace
Key Takeaways
AgentExchange is Salesforce's trusted marketplace for Agentforce components, launched March 4, 2025 with more than 200 launch partners and hundreds of ready-made listings.
Listings include agent actions, topics, prompt templates, and agent templates, plus full agents and partner solutions — many security-reviewed by Salesforce.
Listings are browsable in the AgentExchange storefront and surfaced directly inside Agent Builder, so components can be installed without leaving the build flow.
Since April 2026 the new AgentExchange unifies AppExchange, AgentExchange, and Slack Marketplace discovery. Evaluate the listing type, compatibility, permissions, and data flow rather than treating them as separate exclusive catalogs.
Supported autolaunched flows, prompt templates, invocable Apex, and supported APIs can be converted into agent actions instead of purchased.
AgentExchange: Extending an Org with the Agentforce Marketplace
The SU '26 blueprint asks candidates to identify common scenarios for extending an org using AgentExchange. AgentExchange is Salesforce's trusted marketplace for Agentforce components. It launched on March 4, 2025 with more than 200 launch partners and hundreds of ready-made listings, many of them security-reviewed by Salesforce.
Current marketplace context: In April 2026 Salesforce combined AppExchange, AgentExchange, and Slack Marketplace into the new AgentExchange. The catalog spans traditional apps, agents, and experts across Salesforce and Slack. Older materials distinguish AppExchange apps from the original AgentExchange agent building blocks; that is useful history, not an exclusive separation of today's storefronts. Check the actual solution type and dependencies.
What You Can Install
| Listing Type | What It Provides | Example |
|---|---|---|
| Agent action | A ready-made step an agent can execute, often wrapping a partner API | A carrier's live shipment-status lookup |
| Topic | A packaged scope of work the agent is allowed to handle | An Order Status topic with actions attached |
| Prompt template | A reusable, tested prompt with merge fields | A case-summary drafting prompt |
| Agent template | A preassembled agent starting point with topics and actions wired | A customer-service agent skeleton |
| Full agents and partner solutions | Complete deployable offerings from partners | An industry-specific agent from an ISV |
Note
Many listings are security-reviewed by Salesforce, but review status is surfaced per listing — confirm it before installing, exactly as you would on AppExchange.
Validate the Installed Solution
Discovery inside Agentforce Builder does not mean every listing can be installed or activated without administrator work. Review required packages, edition, agent licenses, connection credentials, action inputs/outputs, and permission assignments. A reviewed shipment action can still fail when a carrier endpoint is unavailable. Add a timeout/fallback response and verify that the agent does not invent a shipment status after an API error. For a refund action, require explicit policy checks in Flow or Apex and test duplicate requests; instructions alone do not enforce a refund ceiling.
Build a small acceptance matrix before production use: authorized versus unauthorized user, missing input, a successful lookup, no matching record, an external timeout, and a repeat request. Inspect the action's actual data transfers and upgrade process. A template can shorten implementation, but does not prove suitability for the company's data or workflow.
Official Source Check
Checked October 19, 2026: New unified AgentExchange (April 2026).
Where You Browse and Install
AgentExchange is browsable in two places. The AgentExchange storefront is the public catalog, and — more importantly for app builders — listings are surfaced directly inside Salesforce's agent-building tools, so a team working in Agent Builder can search, review, and install a component without leaving the build flow. Discovery and installation happen where the work happens, which shortens the path from idea to working agent. For example, while wiring an Order Status topic, an admin can search for a shipment-tracking action, read its review status and documentation, and install it mid-session — then continue configuring the topic. The marketplace behaves less like a separate website and more like a parts bin that sits inside the workshop.
You May Already Own the Building Blocks
The quiet trap on this objective is assuming every capability must be purchased. You can turn existing org assets into agent actions: supported autolaunched flows, prompt templates, invocable Apex, and supported API integrations can all be exposed as actions an agent calls. An org with a mature refund flow does not need a partner listing to let an agent process refunds — it needs to convert the flow it already has.
Tip
Before shopping the marketplace, inventory what the org already automates. The cheapest, safest agent action is frequently the flow that has run reliably in production for two years.
Install versus Build: The Decision Framework
| Factor | Favor Installing from AgentExchange | Favor Building a Custom Action |
|---|---|---|
| Time-to-value | Install, configure, and test this sprint | Build, test, and harden on your own timeline |
| Maintenance | Partner ships updates through the listing | Your team owns every change |
| Logic fit | Standard, industry-common process | Proprietary rules with no market equivalent |
| Data sensitivity | Data flows to a reviewed partner integration | Data must stay entirely in-org |
| Review posture | Security-reviewed listing already available | Internal security review only |
Scenario Walkthroughs
Scenario 1 — Standard partner capability. A retailer's service team wants its agent to answer where is my order? using a carrier's tracking system. The carrier publishes a security-reviewed agent action on AgentExchange. Installing it and attaching it to an Order Status topic delivers partner-maintained status updates in days — faster time-to-value than building and maintaining a custom API integration, and upgrade availability and installation depend on the listing's package/distribution model and customer policy.
Scenario 2 — Proprietary logic and sensitive data. The same retailer calculates refunds with a proprietary severity matrix and touches payment fields governed by strict compliance rules. Here a custom action built from an existing flow is justified: the logic has no market equivalent, and the action's deterministic record logic is owned by the org. Review grounding, prompts, service processing, and any external integrations separately.
Scenario 3 — Start from a template, then customize. The team also wants agents to draft case summaries in the company voice. A reviewed prompt template listing provides a tested starting point; the team customizes wording and guardrails rather than prompting from scratch. Because the template ships with proven prompt structure, effort goes into voice and policy instead of prompt mechanics.
Best Practices & Common Exam Traps
- Match the scenario to the solution: the unified AgentExchange includes apps and agentic components; choose the listing type and implementation that meet the requirement.
- Off-the-shelf wins on time-to-value and partner-maintained updates; custom wins on proprietary logic and data sensitivity. The exam rewards recognizing which force dominates a scenario.
- Installation does not require leaving Agent Builder — listings surface inside the agent-building tools.
- Not everything must be bought. Supported autolaunched flows, prompt templates, invocable Apex, and supported APIs can become agent actions.
- Security review is per listing — verify it rather than assuming every item is reviewed.
A service team wants its Agentforce agent to answer shipment-status questions using live data from a national carrier. The carrier publishes a security-reviewed agent action on AgentExchange, and the team builds its agent in Agent Builder. What is the strongest recommendation?
Build a custom Apex action that calls the carrier API, because partner listings cannot be extended after install
Buy the carrier's full managed app on AppExchange, because AgentExchange lists only prompt templates
Skip the action entirely and paste tracking URLs into the agent's instructions for the model to fetch
Install the carrier's reviewed agent action from within Agent Builder and attach it to an Order Status topic
An app builder is choosing a partner solution in October 2026. Which statement describes the current Salesforce marketplace?
AppExchange sells managed packages only and AgentExchange excludes all traditional apps.
The new AgentExchange unifies AppExchange, AgentExchange, and Slack Marketplace discovery; inspect the solution type and dependencies.
The marketplace replaces sandbox testing and permission review.
AgentExchange is only a private catalog populated from the org's own flows.
Universal Containers already runs a battle-tested autolaunched flow that issues refund credits. A new Agentforce agent should handle refund conversations end to end, and a stakeholder proposes buying an equivalent refund action from a partner. What should the app builder recommend?
Rebuild the refund logic as Apex so the agent can call it, retiring the flow to avoid duplication
Purchase the partner listing, because agents can only call actions that originate on AgentExchange
Convert the existing flow into an agent action so the agent calls the org's own tested refund logic
Keep the flow and the agent fully separate, requiring staff to run refunds manually outside the conversation
Sections you finish are checked off in the contents.