Certinia
Connect AI agents and workflows to Certinia on Salesforce: projects, timecards, resources, sales and payable invoices, journals and billing.
Book a demoCertinia for AI agents and workflows.
engini lets your AI agents and workflows work in Certinia, the professional services and financial management suite built on Salesforce: read projects, milestones, timecards and resource requests, enter timecards and expenses, read and post sales and payable invoices, post journals, and start a workflow when records change. Services firms connect delivery and finance in Certinia to payroll, the data warehouse and every system outside Salesforce. Connect from Claude, ChatGPT or Cursor over MCP, from your code, or build in Workflow Studio.
Cursor, your code
audit log
in engini
What your agent can do in Certinia. Every tool is one you allow or leave out.
The Certinia tools in engini, grouped by what they change. Read tools are safe to hand out widely. Write and delete tools go only to the agents that need them.
Read
Read projects with budgets, status and margin.
Read time and expenses by resource and project.
Read staffing.
Read billing, payables and the ledger.
Write
Enter time and expenses.
Ask for a resource on a project.
Bill a client and post it.
Enter supplier invoices and journals.
Any endpoint
Call any Salesforce or Certinia API, with the sign-in added for you.
Triggers
Projects, timecards or invoices added or changed.
A trigger starts a workflow, and a workflow can include an AI agent step. In Code, a trigger delivers the event to your own endpoint.
Connect your AI agent to Certinia. Four ways in, one set of permissions.
Claude, ChatGPT, Cursor
Create an MCP server in engini with your Certinia 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 Certinia 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 Certinia 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 Certinia 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 Certinia through engini
{
"mcpServers": {
"engini-certinia": {
"url": "<your engini MCP server address>"
}
}
}
Create the MCP server in engini with your Certinia 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 Certinia tools in the agent's toolset or MCP server. If a tool is not allowed, the agent cannot call it.
What teams build on Certinia. Agents and workflows, across systems.
Utilization people can see
Timecards and assignments from Certinia land in Snowflake or Power BI next to revenue, so leaders see utilization by practice.
Payroll and expenses in the ledger
Payroll from ADP or Workday and expenses from Expensify post as Certinia journals and payable invoices.
Timecards on time
Every Friday, consultants missing time get a Slack message, and managers see who is still out.
Project health on request
An agent in Claude answers budget, burn and staffing questions by project. Its toolset holds read tools only.
Every integration runs both ways, so any of these flows can also run in reverse. These are examples, not the limit: any flow between Certinia and another system engini connects is available.
You decide what each agent may do in Certinia. engini enforces it on every call.
Only the tools you allow
A toolset lists the Certinia 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 Certinia account and engini acts as that person, with their Certinia 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.
Connect Certinia in three steps. Then decide what each agent may do.
Sign in to Certinia
Add a Certinia connection by signing in to the Salesforce org where Certinia is installed, with a user that holds only the Certinia permission sets the workflows need.
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 Certinia from Claude, ChatGPT, Cursor or your own code.
Certinia and engini. Straight answers.
Can an AI agent write to Certinia, or only read?
Both. engini has tools to enter timecards and expenses, request resources, create and post sales invoices, and enter payable invoices and journals. 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 connection?
Certinia lives in Salesforce, so its data sits in Salesforce objects. This page adds named Certinia tools, such as posting a sales invoice or entering a timecard, on top of the same Salesforce sign-in.
Does the agent act as me in Certinia?
It acts as the Salesforce user behind the connection, with that user's Certinia permission sets. Every run is recorded under the person who started it.
Can a change in Certinia start work?
Yes. Scheduled triggers check for new or changed projects, timecards and invoices. A workflow can include an AI agent step.
What if the tool I need is not listed?
Use Send API Request to call any Certinia API endpoint through the same connection, and give it only to the agents that need it.