Slack Feed

Hi @James K.k

The biggest win is usually reducing database operations, not just reducing Flow elements.

I’d bulkify the Flow around collections, eliminate Get Records/DML inside loops, and query only the fields/records actually needed. If the volume or logic still pushes governor limits, I’d move that part to Apex and let Flow handle the orchestration.

Hi @Mark Walmart​ in therms of resources there is not much to be honest:

• since Salesforce acquired Slack you can check https://trailhead.salesforce.com/search/learning?keywords=slack - you will need a free account
• main resource is still 'Slack Certified' platform https://www.slackcertified.com/: I would start with 'Slack Skills Badges' and if you have resource I definitely recommend 'Slack Prep Course' https://www.slackcertified.com/page/slack-certified-admin - it's really great
• I also recommend requesting Enterprise Grid Sandbox with this form https://docs.google.com/forms/d/e/1FAIpQLSe9tIHOq1bZVq5xlzymvPGFbqsv2aLFgg04SOi5KfzKbJYBAA/viewform or by joining 'Slack Developer Program' https://api.slack.com/developer-program - in general each Slack certificate is very Enterprise oriented so in case of Admin cert you will have a big number of questions relating to Enterprise Analytics, Settings, Security etc
• And last but not least joining 'Slack Community Forum', 'Slack Community Workspace' and if possible 'Slack Champion Network' - for the last one you need to work on a paid workspace to join

This is a standard multi-tenant integration problem, and the fix is to decouple "receiving the Slack event" from "which customer org owns it":

1. One shared gateway endpoint, not tied to any single customer's org — this can be a lightweight middleware/integration layer (or even a Salesforce org dedicated to this purpose) that owns the single Slack Request URL and does nothing except receive and route events.
2. A mapping table (Slack team_id → customer org connection details: instance URL, auth credentials/Named Credential reference) that the gateway looks up on every incoming event. Slack always sends team_id in the payload, so this is your routing key.
3. Outbound callout to the correct org, authenticated per customer — typically via a Named Credential (or OAuth JWT flow) configured per tenant, so the gateway calls each customer's org as an external system rather than the customer's org receiving Slack traffic directly.
4. Verify the Slack signature per request against the shared signing secret before you even look at the payload — since one endpoint now serves multiple tenants, this check is what prevents cross-tenant spoofing.

If you don't want to stand up separate middleware, you can implement the gateway as a small Salesforce org (or a lightweight Apex REST service in whichever org you already control) whose only job is to receive, authenticate, look up the tenant, and forward — keeping the actual business logic entirely inside each customer's own org. The two things that matter most in this shape (a single inbound entry point fanning out to multiple external systems based on a routing key) are keeping the routing/credential mapping data out of code (custom metadata or a protected custom object) and validating the source signature before any routing decision. 

Hey Maksimilian, 

 That error is the Apex SDK for Slack telling you your message-event handler threw an unhandled exception — it's coming from your Apex code, not Slack itself. That's also why it only happens on inbound Slack messages: sending from Salesforce never touches that handler, so nothing throws.

Turn on debug logs for the integration user and post one test message — the log will show the exact line that's null.

Usual causes:

• Message subtypes (bot messages, edits, thread replies, channel_join) hit the same handler but don't carry the same fields, so event.getUser()/getText() comes back null if you assume every message looks the same.
• A SOQL lookup by user/channel ID returning no rows, then grabbing [0] before checking.

Fix is null-guarding the handler itself — no need to touch scopes or event subscriptions. Happy to look at the handler class if you want to share it. 

Hi Muhammad, yes — there's an official ChatGPT app for Slack, built by OpenAI on Slack's platform. 

How to add it: 

1. In Slack, go to Apps 

2. Open the Slack Marketplace and search for "ChatGPT" (or install directly from the official listing) 

3. Click Install / Add to Slack 

4. Sign in with your ChatGPT account when prompted, then click Connect ChatGPT to link the two 

Once connected, it shows up in your sidebar and you can chat with it, summarize threads/messages, and ask it questions right from Slack. 

What you'll need: 

- A Slack workspace that allows third-party app installs (a workspace admin may need to approve it) 

- A paid Slack plan 

- A ChatGPT account — a paid plan (Plus/Pro/Business/Enterprise) is generally required to actually use ChatGPT's features inside Slack, though the Slack app itself is free to install 

A couple of notes if you're on a team/company workspace: it can only see messages and files you're already authorized to view, and if you're not the workspace admin you may need someone with admin rights to approve the install first. 

Reference: