Reading about Agentforce is one thing — actually building an agent is where it clicks. You don't need to write a line of Apex to get a basic agent running. Here's the step-by-step process using Agentforce Builder.
Step 1: Set Up the Agent
Start by giving your agent a descriptive name — something like "Order Status Agent" — which auto-generates its API name. You'll also write a short description of your company/use case and assign a user profile that determines what data and objects the agent is allowed to touch. Think of this as the agent's permission boundary before it ever runs.
Step 2: Define Topics
Topics are the foundation of what an agent can do. Each topic covers one area of responsibility — for example, "Check Order Status" or "Process a Return." For every topic you define:
A name for the topic.
A description of when the agent should use it.
A scope that specifies exactly what questions or tasks it covers — and, implicitly, what it doesn't.
A new agent starts with just one topic. You add more as you extend what it can handle.
Step 3: Write Instructions
Instructions are scoped, plain-language guidance for how the agent should behave within a topic — which actions to call, in what order, and how to handle edge cases or guardrails. This is the closest thing to "programming" the agent's judgment, and it's worth being specific: vague instructions produce unpredictable agents.
Step 4: Configure Actions
Actions are what the agent actually does when it decides to act — looking up a record, updating a field, sending an email. You can use Salesforce's pre-built actions, or create custom ones with Flow Builder (or Apex, for more complex logic) and expose them to the agent.
Step 5: Test Before You Trust
Agent preview lets you type in realistic prompts and watch how the agent responds — which topic it picks, which actions it calls, and whether it stays inside its intended scope. This step matters more than it sounds like: it's where you catch an agent confidently doing the wrong thing before a customer does.
Step 6: Activate
Once testing looks solid, activating the agent in Agentforce Builder makes it live. From there, most teams keep iterating — adding topics, tightening instructions, and expanding actions — rather than treating "activated" as "finished."
Conclusion
The pattern to remember: Agent → Topics → Instructions → Actions → Test → Activate. It maps loosely to how Flow Builder relates to Salesforce Flow — a guided, visual way to assemble something that would otherwise take a lot of custom code. Next in this series: why the data you feed an agent matters as much as how you build it.
Sources: Salesforce Ben — Complete Guide to Creating an Agent in Agentforce, Salesforce Developers — Agentforce Workshop.
Image: Wikimedia Commons (Public domain)

Comments
Post a Comment