AgentforceBuilder | Salesforce Trailblazer Community

Does Agentforce Analytics in Agentforce Studio require a Data Cloud license

We are evaluating Agentforce Analytics in Agentforce Studio and would like to understand the licensing requirements. Is a Data Cloud license

required to use Agentforce Analytics, or can it be used with standard Agentforce licenses? If Data Cloud is required, which specific Data Cloud permissions, editions, or features are needed?

#Agentforce #AgentforceBuilder #Analytics

4 réponses

Mudasir Munawar
Aujourd’hui, à 09:20
There is a request from an internal team at the organization to send a report extract from Salesforce to a shared network drive within the organization for a bot to pickup. Is there a way to automate this within Salesforce?

Ajouter un commentaire

Rédiger une réponse...

0/9000

28 sept., 16:10

Need Guidance on Agentforce Use Case Technical & Functional Solution Design Preparation (End-to-End)

Hello Trailblazers,

I am preparing an Agentforce Solution Design for a client and would like guidance from experienced architects and consultants on how to approach the design comprehensively.

The use case may involve Employee Agent, Coworker Agent, and Out-of-the-Box Salesforce Agents

, Flex Prompt Template and I want to ensure I am covering all important aspects from business requirements through implementation, licenses, Flex Credit model, governance, and deployment.

Any sample templates, reference designs, or lessons learned from real implementations would be greatly appreciated.

Thank you in advance for your guidance! 🚀

#Agentforce #SalesforceAI #Solution Architects #AgentforceBuilder #Enterprise Architecture

2 réponses

Digbijaya Paikaray (CONFIDENTIAL)
Hier, à 08:35
Hey Jiyaulla,

Here’s how I would approach the solution design:

1. Agent Boundaries & Routing
Split by persona: Don't build one monster agent. Keep Employee Desk (IT/HR Q&A via Knowledge), Coworker (sales/service reps on record pages), and OOTB Service Agent in clean, separate buckets.

Topics & Hand-offs: Limit each agent to 4–6 tightly scoped Topics. Write explicit "When to use" instructions so the reasoning engine doesn’t cross wires. Always map human escalation via Omni-Channel, carrying the chat summary over.

2. Actions & Grounding (The Engine)
Actions: Use Autolaunched Flows for standard CRM updates and Invocable Apex for external API lookups. Keep JSON outputs short; feeding raw multi-page payloads burns tokens and slows reasoning down.

Flex Prompt Templates: Stick to a 4-part prompt: Role, Grounded Context, Guardrails (what NOT to do), and exact Output Format.

Knowledge & Data Cloud: If grounding with PDFs or policies, ensure your Data Cloud search indexes chunk properly. Watch Field-Level Security—if the running agent user can’t see the field, the LLM hallucinates.

3. Trust, Guardrails & Security
Einstein Trust Layer: Decide upfront if PII needs data masking and where audit logs get retained.

Hard Refusals: Put explicit negative prompts inside each topic (e.g., "Never disclose salary bands; route user to Workday").

4. Licenses & Consumption Reality Check
Cost control: Agentforce bills per conversation, and custom prompt calls burn credits. Don't use the LLM for things a simple Flow lookup or formula can solve deterministically.

Token limits: Heavy record grounding causes latency spikes. Keep grounding payloads minimal.

5. ALM & Deployments (Where Projects Trip Up)
Metadata API: Topics, Actions, and GenAiPromptTemplate deploy through standard DevOps pipelines (Copado, Flosum, SFDX).

Manual Post-Deploy: Playbooks always break here. You must manually:
Assign permissions and FLS to the Agent Execution User.
Activate the Agent version in Target Org.
Validate Data Cloud search index syncs.

Ajouter un commentaire

Rédiger une réponse...

0/9000

23 sept., 15:11

Issue with Detecting Topic/Subagent Pre-Arrival Guest - Service Agent with Customization Challenge

1) I am assuming this error message means there is an issue with my Pre-Arrival Guest Experience Subagent. Screenshot below reads "The custom topic Pre-Arrival Guest Experience is not detected. Ensure the topic meets the requirements."

2) I followed all the instructions, so is this a connection to trailhead issue or a subagent requirements issue? It's tough because a lot of the challenge direction language is outdated.

Any advice would be greatly appreciated!!

Issue with Detecting Topic/Subagent Pre-Arrival Guest - Service Agent with Customization Challenge

#Trailhead Challenges #Agentforce #AgentforceBuilder

1 réponse

Keiji Otsubo
23 sept., 20:54
Hi ,

It was some issue with the API name which did not change when I changed the label name.

https://trailhead.salesforce.com/trailblazer-community/feed/0D5KX00000amP6T0AU

Ajouter un commentaire

Rédiger une réponse...

0/9000

20 août, 10:55

Setup with Agentforce

Just wrapped up the Setup with Agentforce Quest and honestly, it's changed how I think about doing admin work in Salesforce.

What stood out most was how it handles permission and access troubleshooting — instead of manually digging through profiles, permission sets, and sharing rules to figure out why a user can't see something, I just asked and got a clear answer. That alone saves a ton of time.

I also liked that it doesn't just make changes on its own — it shows a preview first and waits for confirmation, so I always know exactly what's about to happen before it happens.

Would recommend every admin try this Quest — it genuinely makes day-to-day Setup work easier.

#Agentforce #Salesforce Developer #AgentforceBuilder #SetupWithAgentforce #SFSweepstakes

Ajouter un commentaire

Rédiger un commentaire...

0/9000

14 août, 16:38

Unable to Find Agent Request in Agentforce – “Deploy an Agent in Slack”

Hi Trailblazers,

I’m currently working on the Trailhead module “Deploy an Agent in Slack.”

As part of the exercise, I’m trying to find the Agent Request under Tools & Settings → Organization Settings → Salesforce →Agentforce. However, when I open Agentforce, the Needs Review tab shows “0 requests” and “No requested agents.”

I have attached a screenshot showing what I’m seeing.

Could someone please help me understand:

Why is the Agent Request not appearing?
Is there any additional setup or permission required?
Do I need to complete any specific step in the Trailhead module before the request appears?

Any guidance would be greatly appreciated. Thank you!

Unable to Find Agent Request in Agentforce – “Deploy an Agent in Slack”

#Salesforce #Trailhead #Slack #AgentforceBuilder

1 réponse

Keiji Otsubo
19 août, 20:59
Hi ,

Please check this article.

https://trailhead.salesforce.com/trailblazer-community/feed/0D5KX00000gR8cp0AC

Ajouter un commentaire

Rédiger une réponse...

0/9000

15 août, 02:02

Help me to fix the error ,

#Agentforce #AgentforceBuilder

1 réponse

Kundan Kumar Jha (Infosys)
15 août, 06:53
Hey Karthick,

The errors in your second screenshot tell you exactly what's wrong:

"Action input 'Guests' in 'Create_Experience_Session_Booking' has primitive type 'number' and does not require 'complex_data_type_name'"
"Action input 'startDate' in 'Get_Sessions' has primitive type 'date' and does not require 'complex_data_type_name'"

Basically, someone (or the auto-generation) set a complex_data_type_name on these two inputs, but that field is only meant for object or list[object] type inputs. Since Guests is a number and startDate is a date, both primitive types, that field should be empty for them.

Fix:
1. Open the Create Experience Session Booking action, find the Guests input parameter, and clear out the complex_data_type_name value, leave it blank
2. Do the same for the startDate input in the Get Sessions action
3. Save, then check the Problems panel again, the 2 warnings under it are worth reviewing too but the 3 errors should clear once these two inputs are fixed

These usually come from the action being generated off a Flow or Apex class where the parameter metadata got mismatched. If you're pulling these actions from a Flow, double check the Flow's input variable data types match what's expected (number/date, not a record/object type) before regenerating the action.

Reference:
https://help.salesforce.com/s/articleView?id=ai.agent_actions_flow.htm&language=en_US&type=5

Ajouter un commentaire

Rédiger une réponse...

0/9000

1 août, 19:38

Set Up Service Assistant challenge fails: 'We can't find the agent named Agentforce Service Assistant' - New Builder only

I'm working on the "Set Up Service Assistant" challenge in the Agentforce Service Assistant module. The challenge validator says it can't find the agent named 'Agentforce Service Assistant', but the agent exists in the org with:

Agent Name: Agentforce Service Assistant
Developer Name: Agentforce_Service_Assistant
Type: Service Agent
Status: Active

The legacy Agentforce Builder is not available in this playground (it redirects to the new Builder). I created the agent using the new Builder with the "Agentforce Service Assistant" template. The validator still fails.

Has anyone solved this? Is there a specific step needed when using the new Builder?

Set Up Service Assistant challenge fails: 'We can't find the agent named Agentforce Service Assistant' - New Builder only

#Trailhead Challenges #AgentforceBuilder

2 réponses

Simon Mort (VISEO)
4 août, 07:59
I had the same issue, you can start with the new builder but then you need to select Agentforce Service Assistant, not the Agentforce Service Agent and it will revert to the classic builder once you make that selection. I chose Agentforce Service Agent initially and it failed validation but I rebuilt it using the Agentforce Service Assistant option and it validated successfully.

Ajouter un commentaire

Rédiger une réponse...

0/9000

28 juil., 15:44

Has anyone worked on the "Configure and Activate Your Sales Coaching Agent" module as part of the "Become an Agentblazer Innovator 2026" track? I'm finding it very difficult; the real issue is that the course instructions are designed for a playground using the old version of Agent Builder, whereas the playground provided by the module uses the new version. Consequently, many things don't match up, making it impossible to complete the module successfully.

Ajouter un commentaire

Rédiger un commentaire...

0/9000

21 mai, 16:31

We added Agentforce support to Power BI Connector for Salesforce

Dear Trailblazers,

We just shipped Agentforce integration for our Power BI Connector for Salesforce, and wanted to share it here in case it's useful for anyone building Salesforce reporting workflows with Power BI.

Power BI Connector for Salesforce is an AppExchange app that lets you define datasets inside Salesforce, selecting objects, fields, and filters, and then load them into Power BI via Power Query. No row limits, incremental refresh, standard Salesforce permissions respected.

The value of adding Agentforce here is that you no longer need to know the Salesforce data model upfront to build a useful dataset. You describe what you want to report on and the agent handles the schema decisions.

The integration adds an Agentforce subagent that works in two modes:

Advisory — Ask it things like "What Salesforce objects and fields should I use to build a sales pipeline report?" and it recommends objects and fields with reasoning, without creating anything.
Creation — Ask it to "Build me a Power BI dataset for lead conversion by source this quarter" and it walks through object selection, field preselection, optional SOQL filters, asks for confirmation, then creates the data source and hands you the Power Query formula to paste into Power BI Desktop.

Setup is currently manual: three Actions, a Subagent, and an Agent configured in Salesforce Setup. A dedicated AppExchange extension is in the works that will replace the manual flow.

We added Agentforce support to Power BI Connector for Salesforce Dear Trailblazers, We just shipped Agentforce integration for our Power BI Connector for Salesforce, and wanted to share it here in cas