Platform
Connect your ERP
Connect ERPNext, Zoho, SAP or Tally to your IoTReady workspace: what you need from the ERP, where you enter it, and what stays out of sight.
Your ERP is the system of record. IoTReady captures what happens on the floor and posts the result back, so the two stay in step. Before anything moves, the workspace needs a connection to the ERP: its address and a way to sign in.
An administrator makes the connection once, under Integrations in the admin area of your workspace. You can also ask the Engineer, the AI built into IoTReady Engine, to do it.
Which systems
| System | What you give the workspace |
|---|---|
| ERPNext | The address of your site, an API key and an API secret |
| Zoho (CRM, Books or Inventory) | Your data centre, a client ID and secret, then you sign in with Zoho |
| SAP (S/4HANA, ECC, Business One) | The base URL of the OData or REST service, a user name and password, and the SAP client number |
| Tally (Tally Prime) | Where Tally’s HTTP interface is reachable, a user name and password |
Other systems go through the same documented APIs. Write to [email protected] if yours isn’t listed.
Make the connection
- Open Integrations and choose your system. The form asks only for what that system needs.
- Give the connection a name. Apps and rules refer to it by that name, so keep it
short, like
erp. - Fill in the details from the table above. Credentials are typed on this page and nowhere else.
- Save. For Zoho, press Sign in and approve access on Zoho’s own page.
Where do the credentials come from?
- ERPNext. In ERPNext, open your user menu, then My Settings > API Access, and generate keys. The secret is shown once. Use a user that has only the permissions the workspace needs.
- Zoho. Create a Server-based Application in the Zoho API console for your region and copy its client ID and secret. The connect page shows the redirect address to register there.
- SAP and Tally. A service user you create for this, with only the access the workspace needs.
What the Engineer does and doesn’t see
You can ask the Engineer to connect your ERP. It helps you pick the system and fills in the parts that aren’t secret, like the site address, and then sends you to the page to type the credentials yourself.
A key, password or secret never goes through the Engineer or into a chat. It’s stored encrypted, and the workspace never shows it again. Saving the form again with a blank credential keeps the one already stored.
What happens next
The connection is the first step. What moves across it - receiving a GRN into the ERP, pulling items and purchase orders into the workspace - is set up on top of it, by installing an app that uses the connection or by describing the flow to the Engineer.
Start with one flow and watch it for a few days before you add the next. The adoption guide says why.
Help
Write to [email protected].