Agentforce setup in the org

Shivanath Devinarayanan · Updated

On this page

Enable Einstein Generative AI, then Agentforce. Stand up one Connected App. Create and activate a Service Agent. Test in Agent Studio before anything in the network calls it.

The paid offer for the first governed production agent, talked to in Slack, is First Agent in Production . Follow the org steps here, then hire through First Agent in Production. Agent versus human-screen, API versus computer-use, lives on AI Integration & Automation . Org and license work before agents lives on Salesforce Optimization .

Enable, then the app, then the agent

Turn on Einstein Generative AI, then Agentforce. The order matters. The agent runtime is not useful if generative AI is not enabled in the org.

One Connected App. OAuth client-credentials is the machine path. Name the Run As user. That name is who the machine is, on the record. Per-user identity comes next, on identity . Client-credentials remains the default when per-user identity is not required. That fact stays on the identity page, not hidden in a footnote.

Create and activate a Service Agent. Wire the connection. Test in Agent Studio before a broker, a Slack surface, or a scheduled job calls it. Optional: a Get Current User flow so later identity tests have something to assert. Wrapping Agentforce as a peer is agent-to-agent , after the first agent exists.

How to hire

Hiring starts with a governed production agent on one documented job, then a consultation.

Start at First Agent in Production , then book a consultation .

SHIVANATH DEVINARAYANAN · SALESFORCE MVP HALL OF FAME ·

SD

SHIVANATH DEVINARAYANAN · SALESFORCE MVP HALL OF FAME ·

SD

Stand up the first production agent

Hiring starts with a governed production agent on one documented job, then a consultation.

Home · About · Services · Portfolio · Success Stories · Writing · News · Events · Contact · Tools I use · Media kit · Privacy Policy