The channel connector framework uses Spring Boot to connect an external channel, such as Twitter or Slack, to the Salesforce Einstein Bot. The framework uses the Einstein Bots SDK and sets up the dependencies like caching, authentication, and metrics using a Spring auto-configuration.
note: For SDK and channel connector framework updates, see the API Release Notes.
The channel connector framework provides these features.
-
Auto-configuration
- : The Spring beans are auto-configured using the
application.properties.
- : The Spring beans are auto-configured using the
-
Authentication mechanism
- : If all OAuth properties (
sfdc.einstein.bots.oauth.*) are configured in the application properties, theAuthMechanismobject of the Einstein Bots SDK is configured to use the JWT Bearer OAuth flow.
- : If all OAuth properties (
-
Caching mechanism
- : If
sfdc.einstein.bots.cache.redis-urlis included in the application properties, the SDK uses Redis cache, otherwise, the in-memory cache is implemented.
- : If
-
Basic and session-managed bot clients
- : If you configure all required properties in
application.properties, bothBasicChatbotClientandSessionManagedChatbotClientare available with default configurations.
- : If you configure all required properties in
-
Bot health indicator
- : The Spring’s health indicator
BotsHealthIndicatoris auto-configured to check the bot’s runtime health status.
- : The Spring’s health indicator
-
Custom implementation support
- : You can provide your own implementation of Spring beans instead of using the default one.
-
Metrics
- : The framework uses the Spring Micrometer library to collect the metrics. You can publish the metrics to all popular monitoring systems, such as New Relic, Prometheus, and Graphite, using Spring Micrometer.