How to Build Your First Agentforce Agent (Free Dev Org)

Written by Desere Balicog Acedo · Published October 16, 2026 · Facts verified October 16, 2026

• No computer science degree required
• Built for 3+ years of professional experience
• Everything here runs in a free Developer Edition org

Three of our guides tell you to go build a small Agentforce agent. None of them show you how, and that gap is why most career changers never do it. You read what Agentforce actually is, you agree it matters for 2026 hiring, then you close the tab because nobody handed you the first click. By the end of this guide you will have a working agent in your own practice org, built with features that cost nothing.

In this guide

1. Why building one agent beats reading about ten
2. Step 1: Get the free org and know its limits
3. Step 2: Turn on the three switches, in order
4. Step 3: Decide what your agent is actually for
5. Step 4: Build the agent, the topic, and the actions
6. Step 5: Test it, break it, and fix the instructions
7. Step 6: Turn it into portfolio and interview material
8. Questions people ask

Why building one agent beats reading about ten

Hiring managers here read the same resumes you are writing. Nearly all list Trailhead progress. Very few say "I built an agent that answers a specific business question, and here is the decision I made when it gave a wrong answer."

What building proves that reading does not:

• You can navigate Setup: enabling features in the right order is half of real admin work.
• You can scope a problem: an agent with one clear job is a design decision, not a tutorial step.
• You can debug a vague failure: when an agent picks the wrong action, nothing turns red. You have to reason about it.

Worth saying out loud before you start: building one small agent does not make you an Agentforce specialist, and it will not substitute for the Agentforce Specialist certification if a posting asks for it. What it does is move you from the pile of people who can describe Agentforce to the much smaller pile who have opened the builder.

Step 1: Get the free org and know its limits

Sign up on the Salesforce Developer Edition signup page, which offers the platform environment for free. Salesforce documents this edition as Developer Edition with Agentforce and Data Cloud. You do not need a credit card and you are not starting a countdown clock on a trial.

The constraints that matter, from Salesforce documentation:

• 150 LLM generation requests per hour: per the Salesforce Help article Get Started with Developer Edition with Agentforce and Data Cloud, this is the published cap. It is a rate limit, not a credit balance.
• 45 days of inactivity: the termination note in that same Help article says Salesforce may terminate on notice if no user has accessed the developer services for forty five days. Log in occasionally and your work survives.
• Agentforce Vibes has a separate allowance: the coding assistant gets 110 requests or 1.5 million tokens, whichever comes first, as a one time allocation. Different product, different number, and the two get mixed up constantly.
• No free Flex Credits: published Agentforce pricing covers paid orgs. Nothing in Salesforce documentation grants a credit allowance in Developer Edition.

Step 2: Turn on the three switches, in order

This is where most people stall, because the documentation is not consistent. One Salesforce page says Agentforce and Data Cloud come pre enabled in the new Developer Edition; the Salesforce Help article for that same org says they are not and gives an enablement sequence. Rather than bet on either, check first and enable what is missing.

The sequence from the Salesforce Help article:

• Data Cloud first: it has to be provisioned before the generative AI layer will work. You will also want the Data Cloud Admin permission set with the default data space enabled.
• Einstein Generative AI second: Setup, Quick Find, Einstein Setup, then turn on Einstein.
• Agentforce third: the current Trailhead path is Setup, Quick Find, Salesforce Go, Agentforce Studio, Get Started, Turn On, Confirm. Refresh the browser afterward or the new menus will not appear.
• Then create the agent: only after all three are on.

You need Lightning Experience, which is standard in a new org. If a menu described above is missing, the usual cause is a stale browser session rather than a missing license.

One more thing to get right at the start: build on the Agentforce Employee agent type. The older "Agentforce (Default)" agent stopped receiving new features in June 2025 and is not available in new environments, so following a 2024 tutorial will send you looking for a screen that no longer exists.

Step 3: Decide what your agent is actually for

Open a notebook before you open Setup. An agent without a defined job produces the kind of demo that impresses nobody: it answers everything vaguely and nothing usefully.

Pick a job with these properties:

• One audience: an internal employee asking about one process, not every customer asking about everything.
• A question with a real answer: "what is the status of this request" beats "tell me about our company".
• One thing the agent can change: creating a record or sending an alert gives you an action to wire up.
• A domain you already know: an onboarding request agent, an equipment request agent, a shift swap agent. Your existing expertise is the differentiator here.

Write three sentences: who talks to the agent, what they ask, and what the agent does about it. Those sentences become your topic description, and a sharp topic description is most of what makes an agent behave.

Step 4: Build the agent, the topic, and the actions

Agent Builder is available here: Salesforce lists Developer Edition among the supported editions for Agentforce, alongside Enterprise, Performance, and Unlimited.

Build in this order:

• Create the agent: choose the Employee agent type, name it after its job rather than after yourself, and give it a short role description.
• Add one topic: paste your three sentences into the description, and write the instructions as rules the agent must follow, not as a summary of what it does.
• Add a standard action: start here, because it works immediately. Note that which standard actions appear depends on the licenses in the org, so your list may differ from a tutorial screenshot.
• Add one Flow action: build a simple autolaunched Flow that creates a record, then expose it to the agent as an action.

The constraint that trips people up: Apex and Flow actions accept primitive data types only as inputs. No lists, no objects. Design a Flow that takes a collection and the action will misbehave without explaining itself. Keep the first Flow to one or two text or number inputs.

Salesforce also publishes design guidance worth respecting even in a practice org: a recommended maximum of 10 actions per subagent and 10 subagents per agent, a 60 second timeout on agent actions, and truncation of action output longer than 65,000 characters.

Step 5: Test it, break it, and fix the instructions

Use the conversation preview in Agent Builder. Ask your agent the question it was built for, then deliberately ask three it was not.

What to watch, and what each failure teaches:

• It picks the wrong action: your topic descriptions overlap or are vague. Tighten the description, not the instructions.
• It invents an answer: it had no grounded data. Either ground it or instruct it to say it cannot help.
• It refuses something it should handle: your instructions are too restrictive, a common overcorrection.
• It stalls: check the 60 second action timeout and whether your Flow is waiting on something.

Keep a log of each failure and what you changed; it is evidence of how you think. Worth being straightforward about the ceiling here: the Agentforce Testing Center, the proper tool for systematic test runs, appears in Trailhead exercises that require a special org with sample data, and we could not confirm it in a plain Developer Edition signup. Manual testing in the preview panel is what you can rely on.

Step 6: Turn it into portfolio and interview material

An agent nobody sees is a hobby. Spend one more evening making it legible to a hiring manager, as you would with any portfolio project built without work experience.

1. Write a one paragraph problem statement: who struggled, with what, and how often.
2. Record a two minute walkthrough showing one successful conversation and one handled edge case.
3. Screenshot your topic description and your Flow, annotating why each input is a primitive type.
4. Add one resume line naming the agent's job and the actions you wired, not the word Agentforce on its own.

Blazer2Role sells the coaching and courses described here. We do not guarantee job placement, and if you want a second opinion on whether your project reads clearly to a hiring manager, email support@blazer2role.com and ask what to send.

Still deciding where Agentforce sits against the rest of the platform? Our guide on which Salesforce skill to learn first puts Flow, Data 360, and Agentforce in order for job seekers, and Einstein versus Agentforce clears up the naming confusion in job descriptions.

Questions people ask

Is Agentforce free to use?
Agentforce is included in the free Developer Edition org, which is built for learning and development rather than production. Production use is covered by Salesforce commercial pricing. Salesforce publishes a cap of 150 LLM generation requests per hour for Developer Edition, so you can build and test freely but not run anything at scale.

Do I need to know Apex to build an Agentforce agent?
No. You can build a working agent with standard actions and a Flow action, both of which are point and click. Apex actions are available in Developer Edition if you want them, but they are not required for a first agent, and a Flow action demonstrates the same skill to most hiring managers.

How long does it take to build your first Agentforce agent?
Budget two evenings. The first covers signup and the three enablement steps, which involve waiting on provisioning. The second covers the agent, one topic, and two actions. Testing and fixing instructions usually takes longer than building, which surprises most people the first time.

What is the difference between a Developer Edition org and a Trailhead Playground?
A Trailhead Playground is itself a Developer Edition org, preloaded with sample data and a package that validates badge challenges. Several Agentforce badges require a specific promo org with Agentforce sample data, obtained from a link inside the unit. A plain signup from developer.salesforce.com has neither the sample data nor the challenge package.

Will a Developer Edition org expire?
The signup terms state that Salesforce may terminate the org if no user has accessed it for 45 days. Logging in every few weeks is enough to keep it. Save anything you cannot afford to lose outside the org as well, since a practice environment is not a backup.

Does building an agent replace the Agentforce Specialist certification?
No. They answer different questions for an employer. The certification shows you studied the platform in a structured way; a built agent shows you can make decisions inside it. If a posting names the certification, the project will not substitute for it, though it will give you better answers during the interview.