The same content, built for copying
This is the Agentforce Action Blueprint in browser form. The architecture, the five Custom Actions, the system prompts and the Apex are identical to the PDF — what changes is how you get at them.
A PDF is the right format for reading an argument end to end. It is the wrong format for lifting a forty-line Apex class out of the middle of page four, which is what most people actually want from this material.
Prompts and Apex, one click each
Every system prompt and every code block has a copy button. That matters more for Agentforce than for most reference material, because system prompts are whitespace- and wording-sensitive in ways that survive a clipboard copy and do not survive a PDF text selection.
Apex invocable scaffolds copy the same way, ready to paste into a developer console.
The boundary, shown side by side
The interactive version presents the central architectural point more directly than the document can: what the LLM decides versus what your code decides, laid out next to each other for each action.
That boundary is the whole discipline of deploying Agentforce safely. Seeing it as a split view rather than as prose tends to make it land faster.
Pick the format that fits the task
Both versions are in the vault and both are free. Read the PDF if you are evaluating whether the architecture is right for you; open the tool if you have already decided and are building.
Nothing you do in the tool is transmitted anywhere — it runs entirely in your browser.
What’s inside
- Navigate the five Custom Actions without scrolling a PDF
- Copy system prompts straight to the clipboard
- Copy Apex invocable scaffolds directly into your org
- Side-by-side view of what the LLM decides versus what your code decides
- The same source material as the PDF — pick whichever format you work in
