Create Agentforce Agent
sf_create_agentCreates an Agentforce agent shell in Salesforce, initiating the first step toward building a functional agent with actions, topics, and a connected planner.
Instructions
Creates an Agentforce Agent (Einstein Copilot) shell in Salesforce. THIS IS STEP 1 OF A 5-STEP SEQUENCE — calling this tool alone produces a non-functional agent shell. You MUST continue calling tools in this exact order without stopping: (0) FIRST create the backing flows (sf_create_flow, flowType=AutoLaunchedFlow, status=Active) and/or Apex classes (sf_create_apex_class with @InvocableMethod) for each capability. (1) THIS TOOL — sf_create_agent. (2) sf_create_agent_action — one call per flow/apex. (3) sf_create_agent_topic — group actions into topics; pass all action API names in the 'actions' array. (4) sf_create_agent_planner — wire topics to the agent. DO NOT report completion to the user until sf_create_agent_planner succeeds. Do not ask the user for confirmation between steps — proceed through all steps autonomously. On the first call (no plannerName), this tool probes whether the org can create custom agent actions at all before creating the shell — if it can't, this call fails with no shell created, rather than leaving an orphaned Bot with no planner/topic/action once step 2 turns out to be unreachable. Active Agentforce permission set licenses do NOT guarantee this probe passes — those are a separate signal, confirmed live to be an unreliable one. Pass skipActionCapabilityCheck:true only for a topics-only agent (no custom actions planned) or when you already know the answer.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tone | No | Communication tone for agent responses | Neutral |
| label | Yes | Agent display label shown to users, e.g. 'Sales Assistant' | |
| company | No | Company name for the agent's context | |
| persona | No | Agent persona/role description, e.g. 'A knowledgeable sales expert who helps close deals'. Deployed as the BotVersion <role>. | |
| agentName | Yes | Agent API name — letters and numbers only, NO underscores (Salesforce rejects underscores in Bot developer names). Max 40 chars. e.g. 'SalesAgent', 'SupportBot'. Used in all subsequent calls (sf_create_agent_topic, sf_create_agent_planner). | |
| description | No | Agent description | |
| plannerName | No | API name of the GenAiPlannerBundle to attach this agent to. Normally omitted on the first call (the planner does not exist yet) — after sf_create_agent_planner succeeds, call this tool again with the same agentName plus plannerName to complete the agent→planner link. This tool is idempotent, so re-running it updates the existing agent. | |
| skipActionCapabilityCheck | No | Skip the pre-flight probe for GenAiFunction (custom agent action) support. The probe exists to fail fast before creating an orphaned agent shell in orgs that can't create custom actions — set this true only if you already know the agent needs topics/instructions with no custom Flow/Apex-backed actions, or already know the probe's answer from a prior call. |