Features by connector
Pick a connector to see exactly what Claude can read and write — and filter by plan tier to see which capabilities are included in Solo or unlock at Team+. Every tool is a slice of real work you can hand off in plain English and review before it lands in the system of record.
Your SyteLine shop floor and back office, answerable in plain English
Infor SyteLine / CloudSuite Industrial is an ERP for manufacturers. This connector speaks the ION API Gateway and IDORequestService, so Claude can read item master and inventory, customers and sales orders, vendors and purchase orders, jobs (with materials + routings), bills of materials, and financials. It's self-describing — Claude can list the tenant's data objects and query any of them — read-only, with encrypted credentials.
The whole ERP, answerable
Inventory, sales and purchase orders, jobs, BOMs, and financials — read across all of it without clicking through SyteLine form by form.
Self-describing — no schema homework
The connector lists the tenant's data objects and their fields, then reads any of them, so Claude finds the right data even when you don't know the table names.
Your ION API service account, encrypted
Connect with the standard Infor ION API credentials file; it's stored encrypted and used only to mint a short-lived session token.
Plan tiers gate capability areas, not API access scope. For pricing, see the Pricing page.
Capabilities
0 workflow areas in Solo plan. Click any capability to expand its “what you can ask” examples and the underlying tool names. Use the sidebar to jump.
Limits and roadmap
What the Infor SyteLineconnector can't do today, and why. We update this when things change.
Not in the vendor's API
Capabilities the vendor handles through admin UI or internal endpoints rather than the documented public API.
- Gated API docs. Infor's IDO/ION API docs live inside the customer tenant. The connector is self-describing (list_objects/describe_object) so it discovers the schema at runtime rather than depending on published docs.
On the roadmap
Technically possible but not yet prioritised. Email product@cohesive360.com if any of these would change your decision to roll out.
- Writes (creating/editing orders, jobs). v1 is read-only. Write tools need per-tenant validation of required fields + business methods and are a later, deliberate phase.
Safeguards built into the connector
Defensive behaviours we put in the client because the underlying systems don't.
Read-only v1
Claude can search and read your ERP data, but cannot create, edit, or delete anything in SyteLine.
Credentials encrypted at rest
Your Infor ION API service-account credentials are encrypted in the vault (AES-256-GCM, per-user) and used only to mint a short-lived bearer token.
Scoped by the service account
Claude sees exactly what the ION API service account is permitted to read — bound by your Infor security.
Full audit trail
Every tool call is logged with the tool name and outcome.
What Infor SyteLine via Cohesive360 is not
Honest boundaries — what Claude through this connector cannot guarantee.
Cohesive360 is a facilitation channel between Claude (Anthropic) and your Infor SyteLinetenant. Claude's responses are Anthropic's output; the underlying data is the vendor's system of record. We transport requests and responses; we do not generate, review, or validate Claude's output, and we do not operate the vendor's API.
Claude can be wrong. It can misread a record, misinterpret a date, draft against the wrong matter, or summarise incorrectly. Treat every draft as a draft — review it before you accept it, particularly anything that affects a deadline, a client communication, or a matter already in motion.
The vendor can be unavailable. The API can rate-limit, return errors, or reject requests for reasons specific to your tenant configuration. When that happens, Claude will tell you — but we have no control over when or why the vendor refuses a call.