Skip to main content

Unlocking AI Potential with LLM Open Connector

About Us
Published by JET BI
07 March 2025
23

Maximize AI potential with the LLM Open Connector for seamless integration


Inroduction

The LLM (Large Language Model) Open Connector bridges the gap between Salesforce and cutting-edge AI models, enabling seamless integration of natural language processing capabilities into your business workflows. With this connector, organizations can harness AI to enhance customer service, automate complex processes, and provide intelligent insights—all within the Salesforce ecosystem. This article explores how the LLM Open Connector works, configuration and practical use cases to supercharge your Salesforce environment with AI-driven solutions.

 

Benefits of Using the Salesforce LLM Connector with a Custom Model:

  • Personalized AI Solutions

Tailor the AI model to your unique business data and use cases.

  • Seamless Salesforce Integration:

Quickly embed AI-driven functionalities into existing Salesforce applications without heavy coding.

  • Secure & Scalable:

Utilize Salesforce’s built-in security, ensuring safe data exchanges while handling large-scale requests.

  • Real-Time Insights:

Get instant AI-generated outputs, enhancing productivity and decision-making.

  • Cost Efficiency:

Reduce development time and focus on business logic rather than complex integrations.

  • Flexibility:

Supports both third-party models and in-house developed models, giving you full control over your AI strategy.


Hands-On Implementation: A Practical Guide to Bringing LLM Open Connector to Life


Before getting started, keep these key requirements in mind:

  • You must have an LLM ready for connection, whether it's from an existing provider or a model you host yourself. It can be proprietary, open-source, or custom-built.
  • The LLM Open Connector is flexible and works with any platform or model, allowing you to choose your preferred provider, inference engine, or hosting solution.
  • The model must be accessible via a standard REST API endpoint and adhere to the Open Connector specification, which follows industry-standard LLM API protocols.
  • The endpoint should support essential foundation model capabilities, particularly chat completions or embeddings.

Our goal was to integrate Eternity Ac's AI clones into Salesforce through the custom LLM Open Connector. 
 

A brief look at our implementation process:

1. We start by selecting Einstein Studio Model Builder in Data Cloud, followed by clicking the Add Foundation Model button:


2. Next, we select the Connect to your LLM:


3. On the next screen, we provide key inputs, including a user-defined name, endpoint URL, private key, and model name. For this example, we’ll use the Eternity Ac model, but any LLM endpoint that follows the Open Connector API specification can be used:

 

4. After successfully connecting the LLM, we now have a foundation model stored in Data Cloud. Next, we click the New Configuration button to create a configured model, making it available in Prompt Builder, the Models API, and more:




5. Next, in the Model Builder Playground, we enter a simple prompt to confirm that our foundation model is functioning correctly:







After successful tests, we save our configuration with a custom name. This name will be used to identify the configured model in Prompt Builder and other areas of the user interface.

Clicking on the name of our newly configured model takes us to its details page. After reviewing the model information, we can select the Create Prompt Template button to generate a new prompt in Prompt Builder for use in Salesforce.



 

Creating a prompt template

  1. In this walkthrough, we'll take on the role of a prompt engineer and craft a basic prompt that provides answers to the questions from Case.Description and posts the results to the Case.Resolution_Summary__c field:




    2. First, we switch the model type from Standard to Custom and select the Eternity Ac model we previously configured using the LLM Open Connector



    In the Preview area we can test the configured prompt, by selecting a test Case and clicking the preview button we will see the result generated by our configured model. After a successful test, the prompt can be activated.

    3. Here's what it looks like from the end user's point of view, the field Resolution_Summary__c has functions as an Einstein Generative AI with defined prompt template:







    This feature enables users to trigger the prompt template with just one click:



     

    Conclusion

    In this post, we demonstrated how to leverage the LLM Open Connector to integrate and save a Eternity AС model endpoint in Model Builder. We then utilized it to create a custom prompt template and connected it to a GenAI text field within the core Salesforce experience. We look forward to seeing the LLMs you integrate and how you use them to enhance generative AI in Salesforce.


Evgeniy Korovin
Head of Engineering for Salesforce Practice
image
Expertise
Question to the expert
image

We have available resources to start working on your project within 5 business days

1 UX Designer

image

1 Admin

image

2 QA engineers

image

1 Consultant

image
Related Articles
All articles
image
Is Salesforce Winning the Public Sector Race?
An analysis of Salesforce's rapid expansion into the U.S. public sector, tracing its path from cautious early government licensing deals in the 2010s through the launch of Government Cloud in 2012, its pivotal role in COVID-19 vaccine rollouts, and its 2025–2026 push into military and intelligence work via Agentforce and Missionforce. The piece covers major 2026 contracts — including a $5.6 billion Army deal, a $1.6 billion VA agreement, and Pentagon Impact Level 5 authorization — alongside real-world case studies like California's REAL ID processing and the UK's NHS back-office operations. It also examines the structural obstacles still facing Salesforce and other vendors in government tech: legacy IT systems decades old, outdated federal procurement rules, budget constraints, and organizational caution around AI adoption, plus the competitive pressure from Palantir, Microsoft, and Oracle in the race for public sector AI spending.
28 August 2026
image
Why Your Salesforce Flows Are Agentforce's Biggest Problem
This article argues that the most underestimated risk in Agentforce deployments isn't data quality — it's the automation layer: years of overlapping Flows, Process Builder processes, Apex triggers, and managed package logic that no one has reviewed end-to-end. It explains why AI agents inherit automation complexity without the tribal knowledge human admins carry, why technical debt only becomes visible after an agent hits it in production, and why a clean demo is no indicator of production readiness. The article closes with a concrete, tool-by-tool inventory approach using Flow Trigger Explorer, Salesforce Optimizer, Setup Audit Trail, Apex Debug Logs, Agent Builder, and Health Check — scoped to the specific processes the agent will actually use rather than the whole org.
23 July 2026
image
How to Wire Multiple Salesforce Projects in One Org Without Breaking Everything
This article maps the real integration patterns that emerge when multiple Salesforce projects — both managed packages and unpackaged code — share a single org. It covers four concrete patterns: attaching custom triggers to package-owned objects, calling global members exposed by managed packages, writing directly into another project's objects, and runtime-guarded reads of package data. It then addresses access control for authenticated and guest users, including the Master-Detail wall and the without sharing elevation pattern. The piece closes with eight concrete risks (compile-time dependencies that block uninstall, upgrade coupling, silent cascade failures, access invisible to admins) and six actionable recommendations for keeping cross-project coupling manageable.
08 July 2026