Integration guide

Connection statuses

Every connection carries exactly one of the statuses below, so you always know what is available today and what needs setup.

• Native: Built into The Forge — no external configuration required.
• 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.
• Coming to the platform: Planned. Not available today.
• Unsupported: No supported connection currently exists for this system.

What's available today

Today, nothing in the registry qualifies as Native or 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

Which system keeps the official record

The Forge does not take over every record. Specialized systems keep their official records — the ledger stays in your accounting software, processed payroll stays with your payroll provider, and regulated clinical or student records stay in their specialized systems. The Forge keeps the official record for the daily work built around them: who is responsible, what happens next, and how it is reported. The full system-by-system breakdown is on the Integrations page.

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 shows whether it is working, warns before credentials expire, records failures, and alerts a named owner when a problem is not resolved.

Platform capability status

The status above describes each third-party connection. The Forge screens that manage those connections carry their own readiness status, read from the same capability registry the product uses internally.

• Integration connections & access panel: Available — Clients can see every system connected during implementation, revoke access themselves without contacting support, and confirm a recurring access review — the credential is encrypted at rest and wiped immediately on revocation.
• Automatic updates from connected financial systems: Early access — Updates arriving from your connected financial systems are verified as genuinely coming from that provider before anything is applied to your records.