#Slack Developers18 personnes en discutent

We don’t have a custom Apex Slack app: no .slackapp / SlackApp metadata, no class extending Slack.EventDispatcher, and Apex Slack App User Setup is empty (no System User / Unmapped User row). The only Slack Apex in the org is SDO demo code (Slack Mission Control: org link / bundles), which is not subscribed to message events.

The ephemeral error comes from the first-party Salesforce app in Slack (Messages tab, “Sending messages to this app has been turned off”), on every message typed in Slack. Salesforce -> Slack does not trigger it.

So there is no handler where we can null-check getUser() / getText(), and we can’t remove message from Event Subscriptions — that app isn’t ours on api.slack.com.

If the same NPE string is also used when Salesforce’s own inbound handler throws, that would explain it. Any idea how to stop or debug that without a custom SlackApp?

This is a good point about the challenge of testing Slack + Salesforce integrations at enterprise scale. With an 8-member sandbox limit, using a combination of focused integration tests, representative test users, and staged UAT seems like a practical way to identify issues before production.

For smaller customization needs during UAT, tools such as espaço invisível para copiar e colar can also be useful when testing how different text formats, usernames, or messages behave across Slack and other platforms.

Hey Sebastien, 

Not a bug in your API usage, this is a genuine gap. The canvases.edit rename operation with title_content updates the canvas's underlying title, but Slack's channel canvas tab has a separate, independently-set "tab name" property. That tab name gets set once (typically when the canvas is first added to a tab) and doesn't automatically re-sync to the canvas title afterward, which matches exactly what you're seeing: manually clearing the tab name forces it to re-sync, but API-based title renames don't propagate to it. 

I couldn't find any Slack API method (canvases.edit, canvases.sections.lookup, conversations.canvases.create) that exposes or resets the tab name specifically, only the canvas title itself. So this looks like a genuine limitation, not something you're missing, there's no documented API method for touching the tab name independently. 

Worth filing this as a bug/feature request via Slack's developer support, since the manual "clear the tab name" workaround you found is really a UI-only re-sync trigger that has no API equivalent yet. 

Reference:

From what I've been seen so far, SlackCRM on Business+ V2 appears to require both the appropriate Slack subscription and compatible Salesforce licensing, but the publicly available documentation on the setup process and limitations seems quite limited.

For anyone planning a deployment, I would recommend verifying:

• Required Slack and Salesforce license types
• Admin permissions and authentication requirements
• Supported integration features on Business+ versus Enterprise Grid
• Sandbox and testing limitations
• Data retention, storage, and email-related constraints

If anyone from Slack or someone who has already implemented SlackCRM in production could share the official documentation or real-world experience, it would be extremely helpful for the community.

Hi there! Great questions, happy to help clarify what's available with the customer management feature in the new version of Slack Business+. 

Slack's built-in CRM tools let you build contact records, log customer interactions, and collaborate with your team — all within Slack. Under the hood, it relies on Salesforce Free Edition, which is automatically created when you set up a contact list.  

End-to-end setup process

• Click your profile picture → Preferences → Salesforce → Create New Salesforce Org
• This must be done by a Workspace Owner

Step 2 — Create your contact list 

• Import from Gmail, a CSV file, or build from scratch
• Access via: Home tab → Salesforce section in the sidebar → All Contacts

Step 3 — Assign access 

• Go to Admin → Manage Salesforce Organizations → select your org → Users tab → Add users to Salesforce org
• Up to 100 people can be granted access
• Permission levels are available via a drop-down menu

Key capabilities

• Log customer interactions (calls, emails, meetings) directly from a contact record 
• Share contacts in DMs or channels 
• Auto-sync Google Calendar and email events via Einstein Activity Capture 
• Customize contact fields (add priority, status, and more) 

Known limitations / constraints 

• Access is capped at 100 users
• Runs on Salesforce Free Edition — advanced Salesforce features/configurations beyond what's described in the help article are not part of this offering 

For the full setup walkthrough, check out the official help article: Manage customer contacts in Slack