Integrations
Works with the systems you already run
Epic One connects to your ERP and CRM and puts every record a user is allowed to see one question away. From the first day, not after a rollout.
ERP
Epicor Kinetic
Jobs, quotes, POs, routings, and job costing, live from Kinetic.
E2 JobBoss²
Every order, traveler, and vendor record in JobBoss², instantly askable.
NetSuite
Financials, inventory, and order data straight from NetSuite.
SAP Business One
Production, purchasing, and financials from SAP Business One.
Dynamics 365 Business Central
Business Central data (items, jobs, ledgers) without opening it.
Acumatica
Cloud ERP records from Acumatica, in plain-English answers.
Infor CloudSuite
Manufacturing data from Infor CloudSuite Industrial and beyond.
Sage 100 / Intacct
Accounting and operations data from Sage, on demand.
Global Shop Solutions
Shop-floor and front-office data from Global Shop Solutions.
CRM
Salesforce
Accounts, opportunities, and pipeline from Salesforce.
HubSpot
Contacts, deals, and activity from HubSpot.
Dynamics 365 Sales
Leads and opportunities from Dynamics 365 Sales.
Zoho CRM
Customer records and pipeline from Zoho CRM.
Pipedrive
Deals and pipeline stages from Pipedrive.
Monday CRM
Boards, contacts, and deal flow from monday CRM.
Portals
Web portal logins, too
Not every system your team touches is an ERP or a CRM. If someone on your team logs into a website to check an order or look something up, Epic One can do the same, using that person’s own login, and bring the answer back into the conversation. That includes, but isn’t limited to, supplier portals, distributor portals, and customer portals.
Supplier portals
Order status, lead times, and pricing from a vendor’s site, without anyone logging in by hand to go check.
Distributor portals
Availability, quotes, and account terms from the distributor sites your buyers already use every day.
Customer portals
Order history, shipment status, and open tickets from a customer-facing portal, pulled up on request.
Got a different portal in mind? Name it on the onboarding form and we’ll confirm the connection on your setup call.
Access, scoped by design
Your permissions carry over
Epic One doesn’t get a master key. Each user connects with their own credentials, so a shop-floor lead sees jobs and travelers while the controller sees financials. The same lines your ERP draws today. The full architecture is documented on the security page.
Do we have to change how we use our ERP?+
No. Your ERP stays the system of record and your team keeps working in it however they do today. Epic One connects alongside it and reads what it needs to answer questions and do tasks.
What can each person see?+
Exactly what their own ERP or CRM login can see, and nothing more. Epic One works with each user’s own credentials, so your existing permission setup carries over on day one. Nobody gains access they didn’t already have.
Can Epic One change records in our systems?+
Only through the approval gate. It previews the exact change, a person approves it, then it executes, verifies, and logs the result. Nothing writes to your ERP or CRM without a human saying yes.
Our ERP isn’t on this list. Can you still connect it?+
Often, yes. Tell us what you run when you request your instance and we’ll confirm on the setup call.
Does Epic One work with web portals we log into, not just our ERP or CRM?+
Yes. Supplier portals, distributor portals, and customer portals are common examples, but that list isn’t exhaustive. If your team checks a website for order status or account info, ask about it on your setup call.
Tell us what you run
Name your ERP on the onboarding form and we'll confirm the connection details on a call before anything goes live.