No guesswork
Every tool is described from your instance, so agents call the right fields.
Connectors read each instance's live schema, custom objects and fields included. Engini keeps them running, so your team never maintains integration code.
record SalesOrder ├ entity ref ├ tranDate date ├ custbody_region custom └ item[] ├ quantity float └ custcol_margin custom
OracleERP
NetSuiteERP
WorkdayHR
InforERP
ServiceNowITSMEvery tool is described from your instance, so agents call the right fields.
Pick the actions each agent gets. Sensitive writes can require approval by amount, system or action.
REST, GraphQL or SOAP, with OAuth 2.0, JWT or API keys. Engini stores and refreshes the credentials.
Start workflows from real-time webhooks or high-frequency polling.
The same toolsets through MCP, SDK, CLI or REST API, and on the no-code canvas.
The On-Prem Agent makes outbound calls only. No inbound ports to open.
1,500+ integrations across ERP, CRM, HR, ITSM, data and messaging.
Browse integrations →Each connector exposes the actions you choose as tools, described from the live schema of your instance, including custom objects and fields.
Agents only see the tools in their toolset, so they call the right fields with the right permissions instead of guessing from generic API documentation.
ERP and other systems of record such as SAP, Oracle, NetSuite, Microsoft Dynamics 365, Workday, Infor, Sage, Salesforce and ServiceNow, plus 1,500+ other integrations across CRM, HR, ITSM, data and messaging.
Yes. The custom connector builder wraps REST, GraphQL and SOAP endpoints and supports OAuth 2.0, JWT and API-key authentication.
Engini stores and refreshes the credentials, and the model never sees them.
Engini does. Authentication refresh, API version changes, rate limits and schema changes are handled for you, so your team doesn't maintain integration code.
Add only the actions the agent needs to its toolset, with read and write scoped separately, then set approval rules for sensitive calls by amount, system or action.
Every call is logged with the agent, the person, the arguments and the decision.
Yes. The On-Prem Agent runs inside your network and makes outbound connections only, so agents can reach on-premises databases, SFTP file drops and internal applications without inbound ports.