Epicor Kinetic

Epicor Kinetic is the manufacturing ERP behind a meaningful slice of the mid-market industrial customer base myai works with — sales orders, jobs, parts, BOMs, BAQs, all sitting in a system that's historically been hard to query from anywhere outside Epicor's own UI. The integration changes that: Kinetic becomes a queryable source for canvases, functions, and chats, with full support for both the SaaS cloud and on-premise deployments.

What you can do

• Pull operational data into a chat — "show me jobs running behind schedule across all plants" returns a structured table from live Kinetic state.
• Run Business Activity Queries — the custom BAQs your team has already built become reusable from chat and from automations, without a separate BAQ runner.
• Read across the manufacturing object model — sales orders, jobs, parts, BOMs, inventory, receipts, customers, vendors, all through the same integration credential.
• Update Kinetic records from automations — a function can update a job status, log an inventory transaction, or create a quote from an upstream signal.
• Cross-source operational views — Kinetic data alongside HubSpot CRM or Fabric warehouse data in a single canvas.

How to connect

Two deployment paths, chosen at credential setup:

• SaaS (Cloud) — OAuth 2.0 client-credentials flow. Provide the Kinetic instance URL, Client ID, and Client Secret from the Epicor Identity Server.
• On-Premise — HTTP Basic Authentication against the Kinetic application server with the credentials of a service user.

Both paths surface the same REST v2 OData endpoints behind the integration, so functions written against one deployment generally work against the other.

Connect Epicor Kinetic in myai

Common use cases

• Daily ops digests — a scheduled function reads open jobs, late orders, and inventory anomalies, summarizes them, and posts to the production lead's chat.
• Custom BAQ surfacing — your existing BAQs become first-class data sources in canvases and apps, without anyone re-implementing them in SQL.
• Cross-system reporting — Kinetic operational data joined with corporate-level Fabric or OneStream data for the multi-brand executive view.

Reference

• Connection model: OAuth 2.0 client-credentials (SaaS) or HTTP Basic (on-prem)
• API surface: Epicor Kinetic REST v2 OData
• Scope: ~24 operations spanning sales orders, jobs, parts, BOM, customers, vendors, BAQs, inventory, and receipts
• Both SaaS and on-prem deployments supported via the same integration; auth model differs per deployment