#Slack6 personnes en discutent

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!  

Complete the Connection in Slack 

Sign Your Slack User into Salesforce from Slack > A modal in your left navigation says Bring Salesforce data into Slack. Click

.  

I am unable to get this option in slack. 

🌱 Everyone starts somewhere with AI 

The new AI Foundations Trail on Trailhead is a welcoming starting point for anyone looking to learn the basics of AI, data, and automation. 

Designed for beginners, this trail makes it easy to start exploring AI with approachable, hands-on learning that helps you confidently build the foundational skills you need to succeed today. 

In this trail you will learn about:

📊 Data Literacy: Explore, understand, and communicate with data. 

⚙️ Automation Logic: Learn about autonomous workflows.

⚖️ Responsible AI: remove bias from your data and algorithms 

🤖 Agentforce: A first look at building with autonomous agents.

No pressure. No expertise required.  

Get started with AI now! 

#Trailhead  #Agentforce  #Salesforce  #Agentblazer  #AI  #Salesforce Developer  #Salesforce Admin

Hi All, 

I am simply trying to send a slack channel message whenever an opportunity moves to closed won stage.  

I have an opportunity record trigger asycn flow that simply runs down the 'run async' path and has a decision check on the opportunity stage. If closed won, it runs down to Send Slack Message action and I have populated the required fields, slack app, slack workspace, executive action as, slack conversation id, and the slack message. 

However, during debug in my developer sandbox, I keep getting the error message:  

" 

We couldn't run action

Hide Error

Info

Error

An error occurred. Try again, or contact Salesforce Customer Support and provide this error ID: 1299900440-35892 (820288246)

Inputs

slackAppIdForToken = A03269G3DNE

slackWorkspaceIdForToken = T0AUVR7GZ62

userIdForToken = null

slackConversationId = C0AUUNER0PP

slackBotName = null

slackMessage = {!tt_SlackClosedWonNotification} (Hello team, A new opportunity has been marked Closed Won. Here are the details: Opportunity: Test Contract Type Account: 001WG00001AjV6DYAV Owner: Amount: Type: New Business)

viewApiName = null

recordId = {!$Record.Id} (006WG00000sl8HZYAY)

slackMessageTimestamp = null 

" 

Am I doing something wrong? The details appear to be grabbing the correct values from my test opportunity? Perhaps my slack conversation id is incorrect? 

Thanks in advance.  

-Roman 

Hi everyone 👋

Slack and Salesforce are both critical to how we operate day to day, and honestly they’ve been great for collaboration. We were early adopters of the Slack Sales Elevate integration, which is now rolled into Slack Business+ and Enterprise+. Over time, we’ve seen teams naturally shift away from email-heavy workflows and start using Slack as a true collaboration platform — which has been awesome.

One of the biggest wins for us has been being able to pull Salesforce objects directly into Slack and keep opportunity-specific context inline while collaborating. That said, we recently ran into a question around related lists and how they behave inside Slack vs. Salesforce.

Specifically: 

 Some related lists associated with an object (in our case, Quotes) show up in Slack, while others do not — even though they clearly exist on the object layout in Salesforce.

I thought I had a decent grasp on how this was supposed to work, but the screenshots attached show a pretty clear delta between:

• Related lists visible on the Quote object directly in Salesforce
• Related lists rendered inside Slack via Sales Elevate

We’ve already confirmed the obvious:

• Object- and record-level permissions are correct
• The related lists are present on the Salesforce page layout
• This isn’t a case of simply forgetting to add/remove a related list in Salesforce

One challenge we’ve run into with this integration is the lack of deep documentation when troubleshooting edge cases like this. At times it feels a bit like a black box — you configure it, hope it works, and if it doesn’t, there’s not much guidance on why.

So my question to the group:

• Does anyone know what specifically governs which related lists are eligible to appear in Slack?
• Are there object-type, relationship-type (lookup vs. master-detail), or UI API constraints that affect this?
• Is this driven by Lightning Record Pages, classic layouts, or something else entirely?

Any insight, gotchas, or “learned this the hard way” experiences would be hugely appreciated. Thanks in advance 🙏 

Hi Everyone, 

I wanted to share a workaround in case anyone is trying to complete the TDX Quest 2026 and gets stuck on the Quick Start: Slackbot for Sales Planning

badge. 

If the primary email address associated with your Trailhead account is already connected to an active Slack org, the challenge may fail. 

Based on what I observed in Trailhead profile settings under Connected Accounts, the provisioning process appears to use the primary email address on the Trailhead profile instead of the connected account email intended for the challenge

. If that primary email address is already tied to an active Slack workspace or org, Slack Playground creation may fail and return this error: 

“We had an issue creating your Slack Playground. Please refresh the page and try again.” 

I also found that after the initial failure, updating the admin user email address in the Salesforce Playground org did not

resolve the issue. The module still failed during challenge validation, which suggests the original email association may still be referenced somewhere in the Slack Playground or validation flow. 

Workaround that worked for me:

1.  Create a brand new Gmail account 
2.  Create a brand new Trailhead account using that same email address 
3.  Start the Quick Start: Slackbot for Sales Planning module over from the beginning 
4.  Create a brand new Slack Playground and Salesforce Playground environment where the Trailhead and Slack email identities are a 1:1 match 
5.  Complete the badge. 
6.  Manually merge your Trailhead accounts afterward to complete your TDX Quest. 

I hope this helps anyone else who gets stuck in this strange little identity swamp. Happy Friday!