Skip to main content
Grupo

Agentblazer Community Group

Welcome, Agentblazer! Are you ready to connect with AI leaders and enthusiasts from around the world? You've come to the right place. The Agentblazer Community is the premier destination to skill up on AI, discuss best practices, gain access to Agentforce product experts, showcase your expertise, and supercharge your career.

Trailhead Tuesday!

 

🚀 Agentic AI is evolving — and so are the Agentblazer Status trails! 

 

We've refreshed Champion, Innovator, and Legend with new content to make sure your skills are in step with AI innovation. 

 

Here’s what's new: 

 

⭐️ Champion

  • AI Fluency Fundamentals: Move from AI awareness to applied fluency in everyday work.

 

⭐️⭐️ Innovator

  • Agentforce Grid: Build and link AI prompts to automate end-to-end processes in Agentforce Grid.
  • Introduction to Salesforce Headless 360: Build on Salesforce any way you want, no browser required.
  • Headless 360: Use Conversation to Build an Agent and learn how developers—and any Agentblazer—can build with Salesforce Headless 360.

 

⭐️⭐️⭐️ Legend

  • Agent Analytics and Monitoring: Discover tools to monitor agent performance and improve its outcomes.
  • Agentforce Configuration for Slack: Configure an employee agent and deploy it in Slack.

 

Skill up today 💪

1 comentario
  1. Hoy, 01:29
    Kudos to Salesforce for creating the Agentblazer program! I recently discovered it, and I’m getting value out of reviewing the modules. These modules are instructional for Salesforce professionals and beyond!
0/9000

When should you build one agent vs. many? And what even is Single-Org Multi-Agent Orchestration (SOMA)? 

 

Jennifer W. Lee breaks it all down in this must-read post for anyone designing Agentforce solutions. ✨ 

 

SOMA lets multiple specialized agents work together in one Salesforce org — coordinated by a Super Agent that acts as the unified front door. From the user's perspective, it's one seamless conversation. Behind the scenes, the right agent is handling the right work. 

 

The key question isn't "how many agents can I build?" — it's knowing when a single agent with subagents is enough vs. when your use case calls for SOMA. 

 

A few signals you need SOMA:

  • Your workflows span multiple domains (HR, IT, Facilities, etc.)
  • Context overload is causing your agent to misroute or skip guardrails
  • You need failures isolated so one process crashing doesn't take down the whole experience

 

And a simple gut check from Jen: if you can't describe a subagent's purpose in one sentence without using the word "and" — it needs to be split further. 💡 

 

Read the full post 🤓

3 comentarios
  1. Hoy, 01:27
    Great post! There is so much attention given to low level work, that high level strategic thinking is less common. This is important for anyone to review.
0/9000

The Agentblazer Collection 🗞️

       

What is it? 

The Agentblazer Collection is a weekly post shared in the community with resources from Salesforce related to Agentforce, community-contributed resources, and other exciting items ✨     

     

Community Contributed Resources:

For a resource be considered for a future post of The Agentblazer Collection, please share content with us by using the workflow

 

Featured Resources this Week:

 

Have a great day, Agentblazers!

1 comentario
  1. Hoy, 01:19

    Thank you for sharing @Joel!

    I liked the one about ‘How Salesforce Pilots Its Own Software’

0/9000

Yalla Habibi! 🚨 Grab your Karak, because the Dubai Trailblazer Community’s favorite duo is officially BACK! ☕✨ 

 

Yes, you read that right—whoever was missing Maham, she’s back! The M&M of the Trailblazer Community are reuniting to bring you a hands-on workshop on Salesforce Headless 360 on 8th August

! 💻⚡ 

 

BUT... before we hit the lab, you have mandatory prep work. You need to meet my stitched-together co-host, Frankie!

🧟‍♂️🎙️ 

 

1️⃣ Step 1: Listen to Frankie & me on Spotify: 👉 https://open.spotify.com/episode/1kbLoZ4pwb6tNs3dNymXDK

 

2️⃣ Step 2: Lock in your spot for 8th August: 👉

https://trailblazercommunitygroups.com/j/wqxw5khm34zw2/

 

Don't leave your RSVP to the last minute like Sheikh Zayed Road 6 PM traffic! See you all on August 8th! 🚗💨  

 

@Salesforce Developer Group, Dubai, UAE @Agentblazer Community Group @* Salesforce Developers * @WFD Partner Cohort: TDX2630DaysChallenge @Architect Trailblazers 

2 comentarios
0/9000

📣 Extend Data 360 with Code Extension: New Salesforce Developers YouTube Series 

 

Need custom logic that goes beyond Data 360's native capabilities? Our new YouTube series shows you how to build and debug custom Python code locally, then deploy and monitor it in Data 360 using the Data 360 Code Extension SDK and Claude Code. Follow Salesforce Developer Advocate @Alba Rivas as she walks through the complete development workflow, from local development to production. 

 

🔍 In this series, you’ll learn how to:  

 

🔹 Run custom code securely within Data 360  

🔹 Build custom Python scripts for batch transforms and custom search index chunking using the Data 360 Code Extension SDK and Claude Code 

🔹 Deploy and monitor Data 360 Code Extensions in production 

 

🎥 Watch the full series today: https://sforce.co/4fA1oFo

 

Want more resources for Salesforce Developers?   

 

 📣 Extend Data 360 with Code Extension: New Salesforce Developers YouTube Series Need custom logic that goes beyond Data 360's native capabilities?

1 comentario
0/9000

Hi everyone,

I'm exploring a solution where sales reps receive customer requirements as images, PDFs, Excel files, etc., and manually create Quotes/RFQs in Salesforce. Validation currently depends on 20–25 reference documents (pricing sheets, catalogs, spec sheets) stored on engineers' local machines, which sometimes leads to incorrect quotes.

I'm looking to use Agentforce/AI to:

  • Identify products/parts from customer documents.
  • Validate Quotes/RFQs against the customer's original requirements and flag mismatches.
  • Suggest quote line items automatically.

Constraints:

  • Prefer a configuration-first approach with minimal custom development.
  • Quote-related documents are stored as Salesforce attachments/files, so the agent should be able to analyze them during validation on individual opportunities and related RFQs.

Has anyone implemented something similar? I'd love to hear your experience with Agentforce, Data Cloud vector search/RAG, document ingestion, and where you'd draw the line between Salesforce-native capabilities and custom AI solutions.

Also, if you have any recommended articles, blogs, or learning resources on this topic, I'd really appreciate them.  

Thanks!

2 respuestas
  1. 27 jul, 09:09

    It sounds like you first need to streamline the process so that customers use a standardized way of sending their requests, then think of any kind of CPQ implementation to sort out the product catalog, and only when it's all done and clean, add AI.

0/9000
3 comentarios
0/9000

The Agentblazer Collection 🗞️

       

What is it? 

The Agentblazer Collection is a weekly post shared in the community with resources from Salesforce related to Agentforce, community-contributed resources, and other exciting items ✨     

     

Community Contributed Resources:

For a resource be considered for a future post of The Agentblazer Collection, please share content with us by using the workflow

 

Featured Resources this Week:

 

Hope your day is going well 😊

0/9000
1 respuesta
0/9000

Still running agents on the legacy Agentforce Builder? Here's why it's time to upgrade!

  

A new blog post outlines 5 reasons to move your agents to the new Agentforce Builder with Agent Script. 

 

Here's the quick breakdown:

  • Consistency — Agent Script combines deterministic logic with LLM reasoning so your agents follow business rules every single time, not just most of the time.
  • Speed & Performance — Structured logic paths mean faster responses, lower token consumption, and real results ➡️ Datasite climbed from ~60% to 82% case deflection.
  • Debugging — Purpose-built debug traces let you pinpoint exactly where things went wrong, down to variable state changes.
  • Team Accessibility — Business analysts can build on Canvas in natural language; developers can write in Script view, VS Code, or CLI.
  • Future Innovation — As of July 2026, new agents can only be created in the new builder. Voice enhancements, agent-to-agent orchestration, and new Observability features are all coming here first.

  

Both the new Agentforce Builder and Agent Script are included with your Agentforce purchase — so there's no reason to wait. 

 

👉 Read the full blog post to learn how to upgrade your agents today.

0/9000