These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
Integrations
Connect customer, engineering, production and finance work with clear ownership.
Start with the information each team needs to exchange and the action that should follow. Agree the direction, source owner, identity mapping and failure handling for each connection during implementation. The website does not establish that a particular provider connector is installed or an endpoint is ready to use.
- Customers and commercial documents
- Customer and contact recordsin and out
- Quotes and customer messagesQuotes · in and out
- Order handoverProducts · in
- Engineering and production
- Engineering documentsin and out
- Shop-floor capturein and out
- Quality resultsin
- Supply, delivery and finance
- Supplier documentsBills · in and out
- Shipment statusin and out
- Bank activityin and out
- Financial and reporting exportsout
- Agents
- Your agentWorks within the permissions you assign
Customers and commercial documents
- Customer and contact records. Map external identifiers to the chosen account and contact model, with entity and access scope preserved. Duplicate messages or imports must not create another customer, opportunity or accepted order.
- Quotes and customer messages. Keep the exact document revision, permitted recipient and actual delivery result. A prepared or submitted message is different from successful transmission or customer acceptance.
- Order handover. Carry accepted products, quantities, net prices and dates into the reviewed order. External sales stages and forecasts cannot bypass the required order decision or create duplicate manufacturing demand.
Engineering and production
- Engineering documents. Exchange the applicable drawings, specifications and revision references through the agreed document workflow. An incoming file does not activate a new bill of materials or routing or replace released instructions without review.
- Shop-floor capture. Agree how authorized people or configured capture services report actual operation time, material use and output. Keep stable event identity, current work scope and correction history. Duplicate reports cannot receive the same output again.
- Quality results. Retain the required plan version, source quantity, measurement and decision. Imported results remain subject to the appropriate acceptance checks and independent release; a message does not clear a hold by itself.
Supply, delivery and finance
- Supplier documents. Match purchase acknowledgments, arrivals and bills to the approved commitment and accepted receipt quantities. Preserve unresolved differences rather than manufacturing a successful receipt or match from a transport response.
- Shipment status. Keep booking or label information separate from actual dispatch and the confirmed shipment quantity. Agree which evidence is authoritative before an external event can affect stock or order fulfillment.
- Bank activity. Distinguish an instruction, rejection, uncertain response and actual settlement. Retain reservations while an outcome is unknown, and reconcile before retrying an action that may already have happened.
- Financial and reporting exports. Keep entity, period, currency, document and source identities with the exported data. The local ledger remains reconciled to its own subledgers; an export does not establish automatic group consolidation or statutory filing.
How connections are governed
service accounts, audit, pausingUse restricted service identities and recheck the current action and field permissions. Stable economic keys and content checks distinguish a repeat from a conflicting request. Changed revisions invalidate stale unexecuted instructions, while completed events retain their history. Migration uses reviewed opening balances and nonposting detail so historical orders, production, shipments and cash are not replayed as new work. Test ordinary actions and representative failures before enabling each connection.
The API is one more client of the same interface. AI assistants and API →
# Example work after configuration
$ curl -s erp.ai/skill.md
› Summarize this customer's current opportunity and quote history.
› Show the accepted order changes awaiting Sales Manager review.
› Explain the material shortage behind this planned work order.
› Show the engineering revision and quality requirements for this job.
› Summarize the terminal output still awaiting the required acceptance.
› Prepare the eligible invoice quantities for Finance Manager review.
› Trace the remaining work-in-progress cost and reported variance.