Updated June 11, 2026 by Sunny Chauhan, Salesforce Platform Developer II.

In June 2026 Salesforce announced that ISVs can embed the full Agentforce 360 stack as the foundation of their products (Salesforce Newsroom). Before this, Agentforce 360 was a customer feature. Now it's a platform layer ISVs can build agentic apps on top of and commercially distribute. For B2B SaaS companies shipping into Salesforce orgs, this is the biggest capability unlock since Lightning Components became packageable.

Pro Tip

TL;DR - Agentforce 360 is now embeddable by ISVs, allowing partners to build and sell their own AI agents and agentic apps using Salesforce's core agent runtime (Salesforce Newsroom, 2026). - What's new: ISVs get access to Agentforce Builder, Actions, Topics, Prompt Templates, and Agent Templates as packageable components. - Why it matters: You can now distribute commercial agents on AgentExchange the same way you distribute Managed Packages. - Who it's for: ISVs with a product worth invoking via agent (data lookups, workflow triggers, AI-augmented decisions). - What it changes about packaging: 2GP Managed Packages now support Agentforce metadata; legacy 1GP packages do not.

Before June 2026, Agentforce 360 was available only to Salesforce customers. Customers could build their own agents inside their org. ISVs could build agents but only as internal proofs of concept; there was no path to distribute an agent commercially or to embed Agentforce primitives in a Managed Package.

The June 2026 announcement opened the full stack. ISVs can now:

1/ Build agents using the same Agentforce Builder customers use 2/ Package those agents alongside their managed code as part of a 2GP Managed Package 3/ Distribute them on AgentExchange (the rebrand of AppExchange) 4/ Monetize them via the Go-to-Market App

In practical terms, an ISV's product can now ship as a Managed Package + a set of Agentforce components, with the customer's org getting both when they install.

I've watched this pattern play out across the founders we work with at Appnigma. The customer experience for SaaS products inside Salesforce has been: install our Managed Package, navigate to a custom tab, do things in our UI.

Agentforce changes the surface. A customer asks their Agentforce agent "what deals are at risk this quarter," and the agent calls your product's logic (via an Action you packaged), pulls a recommendation, and surfaces it inside the agent conversation. Your product runs without the customer ever opening your tab.

Pro Tip

The big unlock isn't that you can build agents. It's that your product becomes invokable by every agent your customer builds. Discovery happens inside the agent flow, not by navigating to your app.

Agentforce introduces packageable component types that didn't exist in standard 2GP Managed Packages.

You package these the same way you package custom objects and Apex: include them in your 2GP package directory, reference them in sfdx-project.json, and version them like any other managed component.

This is the part most blog coverage misses. Agentforce metadata types are supported only in 2GP Managed Packages, not in legacy 1GP. If you have an existing 1GP package and want to ship Agentforce components, you have to migrate to 2GP first.

→ New ISVs: start in 2GP. The Salesforce CLI workflow handles Agentforce metadata natively. → Existing 1GP ISVs: migrate before adding Agentforce capabilities. See our 1GP to 2GP migration guide. → Don't try to retrofit. Agentforce metadata won't compile into a 1GP package.

The high-level workflow, end to end.

1/ Confirm 2GP packaging. If you're on 1GP, migrate first (guide). 2/ Enable Agentforce in your Dev Hub. Setup → Agentforce → enable. Required to develop agent components. 3/ Design your Actions. Each Action is a unit of logic the agent invokes. Map your product's existing API surface to Actions. 4/ Build Topics. Each Topic groups Actions around a customer-meaningful capability (for example, "deal risk scoring," "meeting prep summary"). 5/ Write Prompt Templates. These are the structured prompts the agent uses to call your Actions with the right context. 6/ Assemble an Agent Template. This is your shippable agent: topics + actions + prompts + agent personality. 7/ Add Agentforce metadata to your `sfdx-project.json`. The CLI handles versioning and packaging. 8/ Create a new package version with sf package version create (existing 2GP workflow; Agentforce types are included automatically). 9/ Promote and submit for Security Review. Agentforce components pass through the standard Security Review ($999 per submission for paid apps). 10/ List on AgentExchange. Use the Partner Console the same way you list a standard Managed Package.

A Series B revenue intelligence product (think: Gong, Avoma) currently ships as a Managed Package. Customers install it and use a custom tab to see meeting analysis. With Agentforce embedded, the same product ships as a Managed Package + an Agent Template.

Now when a customer's sales rep asks their Salesforce agent "what did Bob from Acme talk about in our last call," the agent invokes the ISV's "MeetingSummary" Action (packaged as Apex), pulls the meeting from the ISV's data layer, and answers the rep inside the agent conversation.

The ISV didn't rebuild anything. They wrapped their existing Apex methods as Actions, defined two Topics, wrote three Prompt Templates, and shipped one Agent Template. Their distribution surface doubled overnight.

• [ ] Confirmed package is 2GP (not 1GP) → Yes / No

• [ ] Agentforce enabled in Dev Hub → Yes / No

• [ ] Actions map cleanly to existing product API surface → Yes / No

• [ ] Topics align with customer-meaningful capabilities → Yes / No

• [ ] Prompt Templates tested in scratch org → Yes / No

• [ ] Agent Template tested end-to-end with a sample agent → Yes / No

• [ ] CRUD/FLS enforcement on all Action-backing Apex → Yes / No

• [ ] Updated AgentExchange listing copy to describe agent capability → Yes / No

Appnigma's no-code platform generates 2GP Managed Packages, and as of June 2026 also supports Agentforce component generation. You describe what your agent should do (the topics, the actions the agent should be able to invoke, the prompt grounding), and the platform produces the Actions, Topics, Prompt Templates, and Agent Template alongside your standard package metadata. Same flow as the no-code Managed Package generation we've been shipping; same security-review readiness.

The June 2026 capability that lets ISVs embed Salesforce's full Agentforce 360 stack as the foundation of their commercial products (Salesforce Newsroom). ISVs can build agents and agentic apps using Agentforce Builder, Actions, Topics, Prompt Templates, and Agent Templates, then distribute on AgentExchange.

Yes. You need to be in the Salesforce ISV Partner Program with an active Partner Business Org. Embedding Agentforce is a partner capability, not a customer one.

No. Agentforce metadata types require 2GP. If you're on 1GP, migrate first before adding Agentforce capabilities.

The review process is the same ($999 per submission for paid apps, 4 to 5 weeks officially). Agentforce components pass through the same Security Review as any other Apex and metadata. CRUD/FLS enforcement on Action-backing Apex is still the top failure cause.

Yes. Agent Templates list on AgentExchange like Managed Packages. You can charge for them, ship private offers via the Go-to-Market App, and apply the standard 15% revenue share (or 25% under OEM).

A Managed Package distributes traditional metadata (objects, Apex, LWCs, flows). An Agent Template distributes agent configuration (topics, actions, prompts). Most real ISV products will ship both bundled in one 2GP package: the Managed Package for the core logic and data, the Agent Template as the agent-invokable surface.

Install your in-development 2GP version into a scratch org with Agentforce enabled, then test agent invocations end to end. Salesforce CLI commands work the same way for Agentforce metadata as for traditional metadata.

Sunny Chauhan is the founder and CEO of Appnigma AI, a no-code platform that generates Salesforce AppExchange-ready Managed Packages and now Agentforce components from natural-language prompts. He holds Salesforce certifications in Platform Developer II, Platform App Builder, Administrator, Data Cloud Consultant, and AI Associate. Since launching Appnigma in 2024, his team has helped B2B SaaS companies including Warmly, Hyperbound, Pylon, Seam AI, and Avoma ship native Managed Packages.

Originally published June 11, 2026. Last reviewed June 11, 2026. Capability statements verified against the Salesforce June 2026 Agentforce 360 for builders announcement and the AgentExchange Partner Community guidance current as of the published date.

• What is Salesforce AgentExchange (AppExchange rebrand)

• AgentExchange Builders Initiative ($50M ISV funding)

• AgentExchange Go-to-Market App

• 1GP to 2GP managed package migration

• What is the Salesforce security review

• How to build a managed package without a Salesforce developer

1/ Salesforce Newsroom, Opening Agentforce 360 to Builders, June 2026 2/ Salesforce Ben, AppExchange to AgentExchange unification, April 2026 3/ ChannelE2E, Salesforce broader platform creation options for partners 4/ Salesforce 2GP Developer Guide v66.0 (Spring '26) 5/ Cyntexa, AgentExchange Trends 2026

Which Actions in your existing product would map cleanest to an Agentforce-invokable shape?