Salesforce Agentforce
Give Salesforce Agentforce agents your ERP, databases and legacy systems through engini tools, and call Agentforce agents from workflows.
Book a demo
Salesforce Agentforce for AI agents and workflows.
engini lets your Agentforce agents act beyond Salesforce: give an agent engini tools through MCP or an external service, and it can read orders and invoices in NetSuite or SAP, check stock in a database behind your firewall, or open a ServiceNow incident, with only the tools you allow and every call on record. The other way round, a workflow can start a session with an Agentforce agent through the Agent API, send it a message and use its answer. Connect from Agentforce, from your code, or build in Workflow Studio.
Cursor, your code
audit log

in engini
What a workflow can do with Agentforce. And what your Agentforce agent can do through engini.
These tools let a workflow or another agent talk to an Agentforce agent. What an Agentforce agent can do outside Salesforce is the toolset you give it in engini.
Converse
Send a message to an Agentforce agent and wait for its answer.
Hold a longer conversation with the agent, one message at a time.
Close the session.
Triggers
There are no Agentforce triggers. An Agentforce agent calls engini tools when it needs them, and a workflow calls the agent when it needs an answer. For record changes in Salesforce, use the Salesforce triggers.
Connect your AI agent to Salesforce Agentforce. Four ways in, one set of permissions.
Claude, ChatGPT, Cursor
Create an MCP server in engini with your Salesforce Agentforce connection and only the tools you choose. Add its address to your client and sign in through engini. There is no key to copy.
MCP client setup →Python and TypeScript
Hand your agent a toolset of Salesforce Agentforce tools. The SDK gives OpenAI and Anthropic models the tools in the format they expect and runs the ones they pick.
SDK guide →For coding agents
The engini CLI connects Salesforce Agentforce and runs its tools from a terminal, with machine-readable output, so an AI coding agent can drive it without getting stuck.
CLI guide →Any language
Every Salesforce Agentforce tool is an endpoint. Call it with exact inputs from a scheduled job or a sync, with no model in the loop.
API reference →.cursor/mcp.json. Claude Code: claude mcp add.// .cursor/mcp.json: Cursor, connected to Salesforce Agentforce through engini
{
"mcpServers": {
"engini-salesforce-agentforce": {
"url": "<your engini MCP server address>"
}
}
}
Create the MCP server in engini with your Salesforce Agentforce connection and the tools this agent may use, then paste its address. The client signs in through engini on first use. Claude, VS Code and other clients take the same address: see the MCP client setup guide.
Each request runs through the Salesforce Agentforce tools in the agent's toolset or MCP server. If a tool is not allowed, the agent cannot call it.
What teams build with Agentforce and engini. Agents in Salesforce that reach every system.
Case answers from the ERP
An Agentforce service agent reads the order, shipment and invoice for a case from NetSuite or SAP through engini, and answers the customer. Its toolset holds read tools only.
Quotes with real stock
An Agentforce sales agent checks availability and pricing in the ERP before it drafts a quote.
Hand-offs to other teams
An Agentforce agent opens a ServiceNow incident or a Jira issue from a case, with the case details, through engini.
Your agent as a step
A workflow sends an inbound email to an Agentforce agent, takes its answer and continues in the ERP.
Every integration runs both ways, so any of these flows can also run in reverse. These are examples, not the limit: any flow between Salesforce Agentforce and another system engini connects is available.
You decide what each agent may do in Salesforce Agentforce. engini enforces it on every call.
Only the tools you allow
A toolset lists the Salesforce Agentforce tools an agent may call and the connection each one uses. Give one agent read tools only and another the write it needs. engini refuses any call outside the toolset.
Scoped when you set them up
An MCP server exposes only the connections and tools chosen when it is created, and engini shows who uses each server.
Whose permissions apply
Connect a person's own Salesforce Agentforce account and engini acts as that person, with their Salesforce Agentforce permissions. Use a shared integration account and it acts as that account. Every run is recorded under the user who started it.
Kept out of prompts
Your agent never needs your credentials: engini stores them and adds them when it runs each call, so keys stay out of prompts and tool inputs.
Every call on record
Every call lands in History and the audit log, which you can export or stream to your SIEM.
Test before production
Workspaces keep teams apart, and development, staging and production environments keep a test agent away from live data.
engini as the agent's tools, or the agent as a step.
As tools: create an MCP server or toolset in engini with the connections and tools an Agentforce agent may use, and add it to the agent as an MCP server or an external service. The agent sees only those tools, engini keeps the credentials, and every call is recorded.
As a step: give engini access to the Salesforce Agent API through a connected app. A workflow or another agent can then start a session with the Agentforce agent, ask it a question and use the answer.
Connect Salesforce Agentforce in three steps. Then decide what each agent may do.
Sign in to Salesforce Agentforce
For tools, create an engini MCP server or toolset and add it to the Agentforce agent. For the other direction, create a connected app with the Agent API scope and add an Agentforce connection with it.
Choose the tools
Add the connection to an MCP server or a toolset with only the tools each agent needs.
Build or ask
Use the connection as a step in a workflow, or ask your agent to work in Salesforce Agentforce from Claude, ChatGPT, Cursor or your own code.
Salesforce Agentforce and engini. Straight answers.
Can an AI agent write to Salesforce Agentforce, or only read?
Both. engini has tools to start sessions with an Agentforce agent and send it messages. What the agent can change outside Salesforce is set by the engini tools you give it. Whether a given agent may use them is up to you: give it a toolset or an MCP server with read tools only, and it cannot call the rest.
How is this different from the Salesforce page?
The Salesforce page is about agents and workflows working with Salesforce records. This page is about Agentforce agents reaching systems outside Salesforce through engini, and workflows talking to those agents.
Can an Agentforce agent reach systems behind our firewall?
Yes. Systems inside your network connect through the engini On-Prem Agent, which opens every connection itself, so there are no inbound ports.
Who controls what the agent may do?
You do, in engini. Each Agentforce agent gets a toolset or MCP server with only the tools it should use, and engini refuses everything else.
Does the agent act as me in Salesforce Agentforce?
Each tool call runs with the engini connection behind it and is recorded under the user. Through the Agent API, engini talks to the agent as the connected app's user.