Integration · ERP
AI agents for Infor CloudSuite (ION API)
Run M3 API (MI) transactions, read SyteLine (CSI) IDOs and check the signed-in user in Infor CloudSuite through the ION API Gateway, as a backend service with a service account.
- Actions
- 2
- Read
- 1
- Write
- 1
Actions
What your agents can do in Infor CloudSuite (ION API)
2 actions. Each one is a tool your agents can call and a step your workflows can run.
Read 1
Look things up. Nothing changes.
Get the signed-in user
Reads the service account's user in Infor OS (Mingle): name, email and the person it maps to.
Write 1
Create, change or send.
Run an M3 API transaction
Runs one M3 API (MI) program transaction through M3's REST v2, like CRS610MI GetBasicData (a customer, CUNO), CRS610MI LstByNumber, MMS200MI GetItmBasic (an item, ITNO), OIS100MI GetOrderHead.
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Enter the sign-in details Infor CloudSuite (ION API) gives you for its API.
What you enter
- Client ID (ci)
- Client secret (cs)
- Service account access key (saak)
- Service account secret key (sask)
Settings
- Tenant (ti)
- ION API address (iu)
- Token address (pu + ot)
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your Infor CloudSuite (ION API) data
Ask a question in plain words. The agent can get the signed-in user in Infor CloudSuite (ION API), then answers with what it found.
- 02
Let an agent update Infor CloudSuite (ION API)
Have the agent run an M3 API transaction in Infor CloudSuite (ION API) as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Share what it finds in Slack
Give one agent Infor CloudSuite (ION API) and Slack: it can get the signed-in user in Infor CloudSuite (ION API) and post a summary to a Slack channel in the same run.
FAQ
Infor CloudSuite (ION API) and MyDeepAgents
Can MyDeepAgents connect to Infor CloudSuite (ION API)?
Yes. The Infor CloudSuite (ION API) connector has 2 actions: 1 reads and 1 makes changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Infor CloudSuite (ION API)?
Enter the sign-in details Infor CloudSuite (ION API) gives you for its API. You'll need: Client ID (ci), Client secret (cs), Service account access key (saak) and Service account secret key (sask). The connection also asks for: Tenant (ti), ION API address (iu) and Token address (pu + ot). Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in Infor CloudSuite (ION API) without asking?
Only if you let it. Its one action that changes data can be set to wait for a person's approval before it runs.
Can I use Infor CloudSuite (ION API) in workflows as well as agents?
Yes. Every Infor CloudSuite (ION API) action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Infor CloudSuite (ION API) to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.