Does Agentforce Require Data Cloud?

No fully implemented Data Cloud programme is required for every Agentforce grounding path. Data 360 must still be provisioned and enabled for all Agentforce use.

Trailhead's Explore Data 360 and Agentforce module states that Data 360 must be provisioned and enabled for all Agentforce use, and that Agentforce Data Library and Einstein Trust Layer do not work without Data 360. Salesforce Help for SFDX deploy prerequisites lists Data Cloud Setup, then Enable, as a required toggle before you can deploy an agent. Enabled is not implemented.

What you can do once Data 360 is provisioned and enabled, without standing up an implemented Data Cloud programme:

• Read org objects through record context and merge fields
• Ground on standard, custom, and external objects
• Call Flow, Apex, prompt templates, and MuleSoft

What Salesforce's Agentforce guide still treats as integral to Data 360:

• RAG
• Data Library
• Agent Analytics
• Digital Wallet

Neither "Agentforce always requires paid Data Cloud" nor "Agentforce never needs Data Cloud" is accurate. Those two claims collapse provisioned into implemented.

GPTfy's position on the same question is No Data Cloud required: Data Context Mapping on existing objects, 4-layer masking, and no Data Cloud SKU. Side-by-side architecture lives on the GPTfy vs Agentforce comparison. This page answers the requirement question only.

For the product explainer, see What is Agentforce?. For the Data Cloud glossary entry, see Data Cloud.

Query Salesforce objects directly when the customer and transactional data the agent needs already live on those objects. Trailhead's Review Options to Ground an Agent With Data lists standard objects, custom objects, external objects, Flow, Apex, prompt templates, and MuleSoft as valid grounding paths without an implemented Data Cloud programme. Record context and merge fields cover in-record values.

Use Data Cloud as the source of context when the work is RAG, Data Library, Agent Analytics, or Digital Wallet. Salesforce's Agentforce guide calls Data 360 integral for those. Trailhead is explicit that Agentforce Data Library and Einstein Trust Layer do not work without Data 360.

Related: Snowflake RAG demo.

Provisioned and enabled is a tenant and a toggle. Implemented is the Data Cloud programme you run as a data layer.

The architect decision guide describes a connected Data 360 tenant. That is provisioned. The Enable toggle is the gate on deploy. Neither of those is an implemented Data Cloud programme.

If standard and custom objects already hold the customer and transactional data, ground there.

On Agentforce, that means record context, merge fields, and the Trailhead list: standard objects, custom objects, external objects, Flow, Apex, and prompt templates. MuleSoft is on that list when the data is reached through an integration, not when it is already on the object.

On GPTfy, that means Data Context Mapping on existing objects, with 4-layer masking applied before a prompt is sent. No Data Cloud SKU.

In-org records are not a reason to make Data Cloud the context layer. Use Data Cloud when the job is RAG, Data Library, Agent Analytics, or Digital Wallet.

Use Flow or Apex when the agent is reading or writing Salesforce data the running user can already reach. Custom actions inherit the permissions of the Flow, Apex, or prompt they wrap. Agents respect licenses, field-level security, and sharing.

Reach outside the org when the record is not a Salesforce object. Trailhead lists external objects and MuleSoft as grounding paths that do not require an implemented Data Cloud programme. GPTfy uses Named Credentials for those callouts. See external objects with AI in Salesforce when the table lives outside the org but should behave like one.

An external API does not bypass field-level security. The custom action still inherits Flow, Apex, or prompt permissions.

Three Agentforce facts from Salesforce Help (Copilot Trust) are easy to miss:

1. Prompts, responses, and trust signals are stored in Data 360.
2. Data masking is disabled for agents. Einstein Trust Layer masking does not apply to Agentforce agents.
3. Agents respect licenses, field-level security, and sharing. Custom actions inherit Flow, Apex, and prompt permissions, so a loose action can expose more than the agent's object access implies.

"Data Cloud is enabled" is a deploy prerequisite, not proof that masking, RAG, or Data Library are in place.

On GPTfy, in-org masking is 4-layer, and it covers 16 of 18 PHI identifiers. See data masking and the GPTfy security layer.

GPTfy runs with no Data Cloud SKU. It grounds on existing objects with Data Context Mapping and 4-layer masking. That is the approved "No Data Cloud required" position.

Agentforce is not Data-Cloud-free. Data 360 must be provisioned and enabled for all Agentforce use, and Data Library plus Einstein Trust Layer do not work without it. Agentforce is also not blocked until a full Data Cloud programme is live. Object, Flow, Apex, prompt-template, and MuleSoft grounding do not require that programme.

If the question is which architecture fits, use the comparison. If the question is the requirement, this page is the answer.

Book a demo.