Skip to main content

Slack Feed

Connect with fellow Trailblazers. Ask and answer questions to build your skills and network.

Hey Trailblazers! 👋 

 

I'd love to get your honest opinion on something that's been on my mind. 

 

When you hit a Salesforce problem you can't quickly solve — a broken flow, a tricky automation, a report that won't behave — what do you actually do? 

 

Do you: 

🔹 Post on this community and wait for replies? 

🔹 Google it and dig through Stack Exchange? 

🔹 Open a Salesforce support ticket? 

🔹 Ask a colleague? 

🔹 Hire a consultant? 

 

I'm specifically curious about: 

1. How long does it typically take you to resolve a problem you're stuck on? 

2. Has a Salesforce issue ever cost your team real time or money while waiting for a fix? 

3. What's the most frustrating part of finding expert help when you need it fast? 

 

No agenda here — I'm genuinely researching the day-to-day challenges admins face and would love real answers from people in the trenches. Drop your experience in the comments, even if it's just a sentence or two. Every response helps! 🙏 

 

#Salesforce Admin #TrailblazerCommunity #Slack Community #Salesforce Developer

2 comments
  1. Today, 1:46 PM

    These are my go-to's:

    • Search Trailhead and post iif I don't find anything
    • Google it 
    • Search the Salesblazer Community in Slack, post there if I don't find anything
    • Talk with my consultant
0/9000

Would like to see if this functionality already exists and, if not, can it be added: Ability for us to "feature" a workflow in a channel, creating a persistent button in the channel - without that button replacing the message field?

  

Use Case: 

95% of the channel users will be sending messages regularly most of the time & we don't want them to all have to find/click a "Send a Message" button off to the side in order to send things regularly, but it is very useful to have the persistent button somewhere.  

(P.S. 

Using the "/" command is not an option

 bc it requires the user to try to find the correct workflow they need, even if they don't know a workflow exists for the thing they want. I want people to be able to come to the channel with the intention to type a message to request a certain thing, but then see the button to make a request there & click that instead - Without adding extra steps to the vast majority of users who will just need to type a message regularly for other use cases) 

 

Potential Solution: 

Maybe there could be an option to add the persistent button somewhere on the message field's format bar? I attached a pic as an example - maybe the blue, yellow, & green boxes are buttons to different featured workflows.  

Creating a persistent button in the channel for Featured Workflows - without that button replacing the message field?

 

Please reach out if you are looking for any more info on this! 

1 answer
  1. Khyati Mehta (SmartBridge) Forum Ambassador
    Oct 31, 2025, 12:27 PM

    Hello Amelia, 

     

    As far as I know, Slack doesn’t provide a native way to create a persistent button in a channel that triggers a workflow without replacing or affecting the message field. Buttons added through messages or apps are tied to those messages and aren’t permanently pinned to the composer area. Your use case — featuring key workflows without disrupting regular messaging — is a great idea but isn’t supported at this time. A potential workaround is to pin a message in the channel containing workflow buttons or shortcuts, making it easily accessible at the top. Alternatively, you could build a Slack app home tab or a custom shortcut in the message composer. Your suggestion about adding buttons to the message format bar would indeed enhance usability, and it’s worth submitting as a feature request to Slack’s feedback channel. Hope this helps!

0/9000
3 answers
0/9000

I have created a Slack Workflow to create Support tickets in Salesforce for our customer accounts.  As part of the workflow, I log the form details used to start the workflow into a Google Sheets file and post a message to the Slack channel the workflow is being used in.  One of the questions on the form we're using is to provide the Account (dropdown).  The Account Name shows as normal when filling out the form, but when the details are logged to the Google Sheet or the message to the channel, it displays the Account ID, not the Account Name.  Is there any way to change this? 

 

#Slack Community

5 answers
  1. Apr 11, 4:15 PM

    Hi @Justin Pauly

     

    Great question - you're actually very close 😊

    The step you’re looking for is "Read a Record" — that's what acts as the lookup to convert the Account ID into the Account Name.

    Here’s how you can set it up:

    1. After your form step, click + Add Step -> Salesforce -> Read a Record
    2. Select Object = Account
    3. For Record ID, map it to the Account value coming from your dropdown (this is the ID)
    4. Make sure to include the Name field in the fields to retrieve

    Then, in your Google Sheets step or Slack message, instead of using the original dropdown value, use the output from this step (Account -> Name).

    That will display the Account Name instead of the ID 👍

    Suggestion: You can rename the step to something like "Get Account Name" to make mapping easier later.

    Let me know if you want help with the mapping - happy to walk through it! 

     

    Hope you find this helpful !!!! 😊 

    Thanks and Regards.

0/9000

I have a few channels that are using the email inbox integration, so you can send emails straight to that channel. 

 

It seems like today with some latest updates, the default changed from being hidden to being expanded. It is a horrible default.  

 

How can I change it back to being automatically hidden so I can only expand things one at a time that I am focusing on? 

 

#Slack Basics

2 answers
  1. Apr 13, 7:48 AM

    Really appreciate how active and supportive this community is becoming. It’s actually one of the strongest parts of the Salesforce ecosystem—being able to learn directly from real users and share practical experiences makes a big difference compared to just reading documentation.

    Posts like this really help new learners understand real-world use cases and challenges, not just theory. Always good to see knowledge being shared in such a collaborative way.

0/9000

I’m building a Slack app with Agents & AI Apps enabled. 

 

In the app’s History tab, threads appear to be ordered by the timestamp of the first message / parent thread creation, not by the most recent reply

 

That creates a bad UX for my use case:

  • an old thread gets a new reply
  • the thread does not move back to the top
  • active conversations get buried under older threads

I’ve looked through:

  • Agents & AI Apps docs
  • assistant thread methods like assistant.threads.setTitle
  • app manifest features.assistant_view
  • app settings / developer console

I haven’t found any option to:

  1. sort History by latest activity,
  2. bump a thread after a new reply, or
  3. configure History ordering in manifest or app settings.

Questions:

  • Is the History sort order currently fixed by Slack client behavior?
  • Is there any supported way to make History sort by latest reply / last activity?
  • Is there any workaround besides creating a brand-new thread instead of replying to an old one?
  • If not supported today, is this on the roadmap?

#Slack Developers

1 answer
  1. Apr 12, 4:25 PM

    Hi @Harold Zhu

     

    No, you can’t change it right now.

    •  The History tab sorting is fixed by Slack’s client (based on thread creation time) 
    •  There’s no setting, API, or manifest option to sort by latest reply or bump threads 
    • assistant.threads.* methods don’t affect ordering 

    Workarounds:

    •  Start a new thread for new activity (most common) 
    •  Or build a custom UI (Home tab / external app) to control sorting 

    As of now, this isn’t configurable and no public roadmap update is available.

     

    If you find this helpful feel free to mark it as Best Answer !!!! 😊 

    Thanks and Regards.

0/9000

Hi everyone,

I'm trying to use a Custom App to feed external legacy system data into Slack AI so that it can generate answers based on our internal documents.

I developed the app using the slack-samples/bolt-ts-search-template as a reference. I successfully implemented the Enterprise Search (Connected Search) functionality. When I use the standard Slack search bar (top of the app), my custom app is successfully triggered, returns the correct JSON data, and the AI summary works perfectly on the search results page.

However, I am facing an issue with the dedicated Slack AI feature (the Ask AI / right-side panel). When I ask the exact same question through the Slack AI chat panel, it completely ignores my custom app. It seems to only search through native Slack messages, files, and canvases, ultimately responding that it cannot find the relevant data.

Is there a specific way, manifest configuration, or routing prompt to force the "Ask AI" feature to query a Custom App when generating answers? Or is this a known limitation of the current Slack AI routing behavior where it prioritizes native Slack data over Connected Search apps in the Ask AI panel?

Any insights or guidance would be greatly appreciated! 

 

 

How to make Slack AI reference Custom App data (Connected Search) in Ask AI?

 

 

image.png

 

 

 

#Slack Developers

1 answer
  1. Apr 11, 5:01 PM

    Hi @Moon Gyun Jeong,

     

    This is a known limitation in Slack AI.

    Connected Search apps work in global search, but Ask AI doesn’t use custom apps - it only pulls from native Slack data.

    No config or prompt can change this currently. 

     

    If you find this helpful feel free to mark it as Best Answer !!!! 😊 

    Thanks and Regards.

0/9000

Hey everyone — has anyone else noticed an "Added by [App Name]" label suddenly showing up on messages sent by their Slack apps?

Our customers started reporting this recently on messages from our app (Rattle). The label appears on every individual block/attachment/button row within a single message, not just once at the top or bottom. It's also showing up retroactively on old messages, so it's clearly a Slack client-side rendering change, not something on our end.

A few things we're trying to figure out:

  • When did this roll out? We can't find it in the official changelog.
  • Is it affecting all apps or just certain ones?
  • Is there any developer control over this?

If anyone has heard anything from Slack about this or found documentation, would love to know. Our customers are asking us to remove it, but since it's not something we're sending in the payload, we can't really do anything about it on our side.

Thanks! 

 

#Slack Developers

1 answer
  1. Apr 10, 6:25 PM

    Hi @Mohit Mangal

     

    Yes - this looks like a

    Slack UI-side change, not something coming from your app payload.

    •  No control for developers to remove it 
    •  Applied at block/message rendering level 
    •  Appears to be a silent rollout (not clearly documented yet) 

    So unfortunately, there’s nothing you can change from the app side right now. 

     

    If you find this helpful feel free to mark it as Best Answer !!!! 😊 

    Thanks and Regards.

0/9000
3 answers
  1. Apr 8, 3:36 PM

    Create Record-Triggered Flow on Opportunity Trigger: When record is created Add Action: Create Slack Channel Set channel name = Opportunity Name Save & Activate

0/9000

Slack supports markdown rendering (https://docs.slack.dev/reference/block-kit/blocks/markdown-block) which is great! I noticed recently that it even handles syntax highlighted code blocks rendering, which is another great enhancement. But while using this block for message rendering, it does not handle indented code blocks (specifically by 4 spaces ;)), which is an issue, because it completely breaks the message.    Is that a known bug? I played around with some workarounds. I can dedent the codeblocks with no problem, but then the rest of a message is still indented and renders as an auto code block.. etc. Fixing something basically offsets something different. Indented code blocks are valid markdown so I don't understand what is the issue.    I would appreciate if this is not a good place to discuss this, where should i reach out?    Thanks in advance!    #Slack Developers    #Slack Community

5 answers
  1. Mar 14, 1:09 PM

    Slack’s markdown block currently does not fully support indented code blocks (4 spaces), even though they are valid in standard Markdown. It mainly supports triple backtick code blocks instead. If you want to report or discuss it, you can raise it in the Slack Developer Community or Slack API support channels.

0/9000