Integrations overview
Integrations connect Ennea to external systems. Availability depends on your deployment, worker configuration, credentials, and permissions. A catalog card or example is not proof of an active connection.
Choose the connection
| Need | Connection path |
|---|---|
| Exchange Online messages and reviewed replies | Microsoft 365 Email in the curated Studio catalog. |
| Existing Konnie Exchange, Gmail, or generic mailbox | Provider configuration in the existing integration area. |
| Teams conversations | Teams settings, when enabled and configured. |
| Read/create repository issues | Curated Gitea connection. |
| Receive order-book demand and return completion | PostgreSQL order book with the reviewed schema. |
| Other business API | A configured, published HTTPS action contract. |
| Machine data / PLC access | Edge Runtime. |
Slack's current configuration screen is a placeholder with disabled saving. Generic ERP cards do not establish vendor compatibility. Ask your implementation contact for the active connector and tested contract.
Set up a curated connection
- Open Operations Studio → Integrations in the intended site/environment with connection-management permission.
- Select the supported connector and enter the required settings. A managed worker must already be provisioned where the connector requires one.
- Enter credentials in the designated secret fields. A saved masked credential is not a value to copy elsewhere.
- Test the connection. Review errors and the external resource actually tested.
- Select the required capabilities and review object/event bindings and source authority.
- Publish the configuration. A saved draft or successful test is not publication.
- Run a small authorized example, inspect activity and receipts, then confirm the target record in both systems where relevant.
Gitea requires the configured repository, connected user, and token permissions for the selected actions. Test a read before reviewing a create-issue action. Keep repository scope and approved inputs explicit.
Execute and monitor
Apps, workflows, and Konnie can use the published capabilities they are authorized to invoke. The configured destination and typed inputs are part of review; a caller cannot choose arbitrary endpoints. When approval is required, dependent workflow steps wait for it.
| Outcome | Next action |
|---|---|
| Awaiting approval | Review the intended external effect. |
| Confirmed result | Inspect returned reference and target state. |
| Failed before execution | Correct configuration or input, then use the allowed retry. |
| Unknown / uncertain | Reconcile the original invocation's receipt before another write. |
| Deactivated / revoked | Ask the administrator to inspect configuration and authority. |
Deactivating a connection does not recall a request already sent to an external system. Resolve in-flight work and preserve receipts when rotating credentials or replacing connections.
See Email, ERP/API, Audit, and Security and deployment.