Integration guide

Status vocabulary

Every system in the integrations registry carries exactly one of the statuses below. This is the same vocabulary rendered on every category, workflow, and app page — nothing on the marketing site claims a status that isn't backed by the registry.

• Native: Built into The Forge — no external configuration required.
• Verified prebuilt: A prebuilt connector, tested against a live third-party account. Ready to configure.
• Configurable API: Connected via a documented third-party API — customer-specific setup within a standard scope.
• Webhook: Event-driven inbound connection over a documented webhook contract.
• Managed import / export: Bulk data movement via managed import/export files, used where a live API isn't available.
• Custom available: Available through a scoped custom integration engagement — new connector, mapping, and testing.
• Under validation: A connector exists but is not yet approved for production customers.
• Planned: On the roadmap. Not available today.
• Unsupported: No supported connection currently exists for this system.

What's available today

During beta, nothing in the registry qualifies as Native or Verified prebuilt — no connector has been packaged as zero-configuration or pre-validated against a live third-party account yet. Every supported connection today ships as one of the statuses below.

• Configurable API
• Webhook
• Managed import / export
• Custom available

Source-of-truth boundaries

The Forge does not claim to become the single source of truth for every record type. Specialized systems keep authority for their domain — the ledger stays in accounting, processed payroll stays with the payroll provider, regulated clinical or student records stay in the specialized system of record. The Forge becomes authoritative for the operational workflow, responsibility, escalation, and cross-system reporting built around those records. The full domain-by-domain boundary is documented on the Integrations hub.

Setup expectations

• Every integration is scoped during the Blueprint before it is built — no connector ships without a confirmed API, auth path, and field mapping.
• Configurable API and webhook connections require customer-specific setup within a standard scope; custom-available connections are a separately scoped engagement.
• Managed import/export is used where a live API isn't available — data moves in bulk files rather than in real time.
• Every connection reports health, tracks credential expiration, records failures, and escalates unresolved exceptions to a named owner.