Prompt Builder versus Flow automation
Key Takeaway
Flow connects to Prompt Builder in two directions. A template-triggered prompt flow gathers and processes data for a prompt template before the LLM sees it. The Prompt Template action lets a flow run a prompt template as a step and use the generated response.
Prompt Builder is where you create, test, revise, customize, and manage prompt templates. A prompt template sends Salesforce data to a large language model (LLM) to generate text, such as a sales email or a field summary. Through prompt templates, Prompt Builder adds generative AI to users' daily work.
Merge fields and grounding
Each prompt template pulls CRM data into the prompt through merge fields. A merge field can reference any of these:
- Record fields
- Flows
- Apex
- Data 360 DMOs
- Related lists
Grounding a prompt template with merge fields gives the LLM context, so its responses are personalized and based on accurate, up-to-date data.
Sensitive data, such as personally identifiable information, stays in Salesforce and isn't shared with the LLM. The zero-retention agreement in the Einstein Trust Layer means that anything shared with the LLM isn't stored or used for training.