Pratique du Shadowing: Connect Slack to Salesforce with Hosted MCP Servers | Salesforce Headless 360 Decoded - Apprendre l'anglais à l'oral avec YouTube
C1
⏸ En pause
What if users could work on Salesforce records and trigger business processes all through a single Slack conversation without opening Salesforce?
78 phrases
Si les phrases sont trop courtes ou trop longues, cliquez sur Edit pour les ajuster.
1
What if users could work on Salesforce records and trigger business processes all through a single Slack conversation without opening Salesforce?
2
Today, I'll show you how to configure this in Slack and how to run it in Slack bot and Salesforce-sourced MCP servers.
3
Hi, and welcome to this episode.
4
My name is Philippe Ozil.
5
I'm a developer advocate at Salesforce.
6
We'll start with why Slack is the engagement layer for Salesforce,
7
then we'll walk you through how to configure Slackbot to connect with Salesforce's MCP servers,
8
and finally, we'll look at some real-world use cases.
9
Slack is the work OS where most teams collaborate, so it feels natural to extend it to avoid context switching between apps.
10
center of this experience is slackbot a single ai interface for every conversation file channel
11
and apps across your organization slack could already integrate with third-party systems
12
but what's new now is
13
that slackbot can seamlessly work with any mcp server such as the sessos hosted mcp servers
14
and this is precisely what we'll focus on in this video in case you missed the other episodes of this series, the Model Context Protocol or MCP is an open standard
15
that lets AI agents interact with external tools and data sources from various vendors.
16
Cessos exposes a set of hosted MCP servers giving any MCP compatible client secure governed access to work with records
17
and execute actions directly from the Cessos orgs.
18
With the standard servers, you can perform CRUD operations on Cessos records, Access Tableau, Data360 and much more.
19
And beyond the standard servers, developers can also expose specific business logic by building custom MCP servers with custom tools such as Apex Actions,
20
Flows, Apex REST Endpoints, Name Queries, Agent Force Agents, and Prompt Builder Templates.
21
Setting up Slackbot to work with self-assisted MCP servers is very simple.
22
There are no URLs to copy, no OAuth configuration, and no external client app to set up.
23
This requires zero custom code.
24
The entire setup lives in the Slack admin UI and it takes just a few steps as I will demo next.
25
Before getting started, we'll need a few things that I won't demonstrate in this video for the sake of time.
26
You need a paid Slack plan, at least one Salesforce org already connected to Slack,
27
Slack org or workspace admin access, a Salesforce administrator access, one or more active Salesforce hosted MCP server.
28
Now that we've cleared the prerequisites, let's get to the setup.
29
First, I'll navigate to the MCP server configuration page in Slack.
30
The path to this page depends on your plan.
31
In this video, I'm using an enterprise grid.
32
The layout is the same for enterprise plus.
33
You navigate to your organization name, then tools and settings, organization settings,
34
Salesforce, and then finally, MCP servers.
35
For Business Plus and Enterprise Select, the flow is a bit different as you can see here.
36
Once you're on the MCP server configuration page, let's add your server.
37
You click Add MCP server.
38
Choose the server you want to add from the list of active Salesforce hosted MCP servers, like for example, S-Objectall, Data360, or any other custom servers.
39
Click add, then review the tools the server exposes.
40
Click next.
41
If you're on Enterprise Grid or Enterprise Plus, you'll need to select which workspaces the server will be available in before proceeding.
42
Now that your servers are added, you can figure who can access them.
43
Either everyone from your org, specific people or groups, or no one for now.
44
This is useful if you want to enable the server later.
45
Your MCP server is now active and Slackbot can use it on behalf of anyone with access.
46
Salesforce MCP servers in Slackbot are permission-aware by design.
47
Your Slack user is mapped to your Salesforce user.
48
Your Salesforce user has a profile and possibly some permission sets and sharing rules that control your access.
49
In particular, which MCP tools you have access to.
50
Every action Slackbot takes respects the user access and adheres to the standard Salesforce security model.
51
In other words, users only see and act on what they're allowed to in Salesforce.
52
Slack admins can adjust access, update permissions, or remove the server entirely from the Slack organization admin UI at any time.
53
Security is also handled at the Slack user level with prompts to prevent accidental use of MCP tools.
54
must explicitly approve the use of a tool before slackbot can execute an action on their behalf now
55
that you know how security works let's look at some practical examples
56
for today's demo we'll use northern trail outfitters a fictitious outdoors gear vendor
57
imagine a northern trail outfitters sales rep but has a call in an hour with one of their customers Alpine trackers.
58
Instead of opening Salesforce, navigating to the account page and cross-referencing opportunities, cases, and activities to prepare the case,
59
they just ask Slackbot one thing.
60
Run a health check on the AlpineTracker's account.
61
Slackbot uses a tool from the standard SObjectAlt MCP server to identify the account based on its name.
62
It then calls a custom health check tool that uses a flow.
63
The flow retrieves additional data from related cases,
64
opportunities and activities to calculate a health score based on precise business rules
65
The health check indicates that the Alpine Tracker's account is at risk because of an unresolved critical support case
66
Once the sales rep reviews the Alpine Tracker's account health, they ask Slackbot to help plan for the customer meeting
67
Slackbot uses another custom tool to identify the meeting stakeholders from the Salesforce contacts related to the account
68
and creates an activity record to prepare for the meeting.
69
All of this happened directly in Slack without contact switching or opening multiple tabs.
70
That's it for today!
71
You've seen how Slackbot uses Salesforce hosted NCP servers to interact
72
with your Salesforce org directly from Slack where your team is already working.
73
You've learned how to configure Slackbot and you saw some practical examples of running custom business processes directly from Slack.
74
Now it's your turn to connect Slackbot to your Salesforce org.
75
Try configuring MCP servers to power your own team's workflows and leverage Slack as your engagement layer.
76
Thank you for watching, I hope that you've enjoyed this video.
77
Make sure to like and subscribe to our channel and let us know in the comments if you found it useful.
78
See you in the next episode!
Télécharger l'application
Everything you need to speak fluently
AI PronunciationScore every sentence
IPA PracticeMaster every sound
VocabularyBuild your word bank
Vocab GameLearn while playing
À propos de cette leçon
Vous vous entraînez en anglais avec "Connect Slack to Salesforce with Hosted MCP Servers | Salesforce Headless 360 Decoded" en utilisant la technique du Shadowing.
Qu'est-ce que la technique du Shadowing ?
Le Shadowing est une technique d'apprentissage des langues fondée sur la science, développée à l'origine pour la formation des interprètes professionnels. Le principe est simple mais puissant : vous écoutez de l'anglais natif et le répétez immédiatement à voix haute — comme une ombre suivant le locuteur avec un décalage de 1 à 2 secondes. Les recherches montrent une amélioration significative de la précision de la prononciation, de l'intonation, du rythme, des liaisons, de la compréhension orale et de la fluidité.