ERP and API integrations
ERP connections need an agreed contract: source system, identities, fields, units, lifecycle mapping, authority, supported actions, and recovery behavior. A generic ERP card does not prove compatibility with your ERP version or interfaces.
PostgreSQL order book
The curated connector supports the reviewed order-book schema, including a creation-event trigger, completion function, and receipt tables. It is not a generic reader for any PostgreSQL database.
- Have the source-system owner provision the reviewed schema and a scoped database user.
- Configure host, port, database, username, and password in the Studio connector. Ensure the managed worker can reach the source database.
- Test the connection. The test checks schema without writing.
- Review object fields, event bindings, work-center codes, and required permissions, then publish.
- Create an authorized test order after publication. Historical orders are not imported automatically.
- Inspect the received order-book record and use the customer-order intake journey to prepare production.
- Review completion reporting and verify its receipt and source-system state.
Optional production details use the reviewed additional fields and routing structures. The routing is an ordered sequential operation list, with destination work-center codes that must resolve. Resolve missing configuration before converting demand to production.
Other HTTPS actions
A connection builder defines the fixed external destination, credentials, typed capabilities, request mapping, response fields, and receipt recovery. Save, test, preview, and publish the appropriate version. Apps, workflows, and Konnie invoke the same configured capabilities under their current permissions.
Use a read action first to verify identity and source projection. For a write, review the selected object, destination, inputs, and external effect. Approval is bound to that intent; editing inputs requires a new eligible review. Required receipt lookup is how a lost write response is reconciled. An uncertain result must not trigger another automatic write.
The current shared action transport uses bounded public HTTPS JSON endpoints. Arbitrary URLs, redirects, private network access through this transport, and unrestricted payloads are not supported. Managed connector workers have their own reviewed connectivity requirements.
Authentication and source authority
Use the configured service identity or granted integration identity. Browser sessions, Edge credentials, integration worker credentials, and external agent grants are distinct. Do not reuse a user's browser token as a permanent ERP credential.
An external identifier is not an Ennea record ID. Preserve both, define the mapping, and decide which source owns each field. Observations show what an external source reported; they do not automatically overwrite authoritative master data.
Reconcile failures
- Validation: correct schema, units, references, or lifecycle mapping before execution.
- Permission failure: inspect actor/service identity and exact scope.
- Pending approval: complete eligible review before dependent steps proceed.
- Unknown write: inspect the original receipt and target system; preserve invocation identity.
- Partial import: reconcile successful records before retrying failed rows.
The product's internal REST routes are not a promise of a universal public API schema or versioning policy. Agree a supported interface with your implementation contact. For external assistant access see External agents; for files see Imports.
Use the PostgreSQL order-book contract for the downloadable DDL, exact fields, fictional source order and expected receipts.