Integrations

Exploration scaffold for source systems, data flows, and connector behavior.

Quellinhalt wird angezeigt aus `en-gb` solange diese Sprache noch nicht übersetzt ist.

Exploration scaffold. This page maps the questions and implementation evidence needed to describe Aeptus integrations. It does not confirm that any connector is available in the released product.

Questions to answer

  • Which systems are in scope, and which connectors are released, being tested, or only planned?
  • What data does each integration read or write, and which permissions does it need?
  • How does a customer authorize, review, revoke, and renew access?
  • How often is data synchronized, and how are freshness and source changes represented?
  • What happens when access expires, a sync fails, or a source changes its API?
  • How is each connection isolated to a customer workspace and monitored for errors?

Product and code information needed

  • A connector catalogue with supported versions, objects, fields, and read/write behavior.
  • OAuth scopes or equivalent permissions, credential storage, renewal, and revocation flow.
  • Sync jobs, change tracking, failure handling, logging, and customer-facing status.
  • Tenant isolation and security tests for connector data.
  • Release evidence distinguishing available integrations from prototypes and roadmap items.

Public-language guardrails

Name an integration only after its released status, scope, and limitations have been verified.