{"slug":"platform/24-integration-manager","title":"24 — Integration Manager","section":"platform","sectionLabel":"Platform","status":"unclassified","type":"document","path":"platform/24-integration-manager.mdx","bytes":3149,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n> **EXTRACTED / NOT CANONICAL.** Descope-as-canonical authorization is\n> superseded. Retain this file only as source material for Integration Manager\n> responsibilities.\n\n> **Extracted from:** IntegrateWise Platform Specification Suite\n> **Region:** third_region\n> **Original line:** 3139\n> **Lines:** 40 | **Chars:** 1,862\n> **Status:** Raw extraction — requires review and canonicalization\n\n24 — Integration Manager\n24.1 Why this doc exists\nConnector Framework (08) describes Nango/MCP/Native/Custom API as separate concepts. The Integration Manager is the single abstraction layer that lets a Capability invocation pick the right underlying transport, abstracting over all four.\n\nAuthorization authority: **Descope** is the canonical external authorization authority for supported outbound connections. Nango is one transport among the compatibility adapters (legacy/dormant) and is not the default architecture.\n\n24.2 Pipeline (preserves user’s ASCII)\nCapability (05)\n↓\nIntegration Manager\n↓\nDescope ── canonical outbound authorization authority (where supported)\nMCP ── tool servers, structured contexts\nNango ── legacy/dormant compatibility adapter (OAuth-mature SaaS)\nNative ── first-party adapters (Salesforce, HubSpot)\nCustom API ── raw HTTP/GraphQL/protobuf\n24.2b Execution surface boundary\nIW-Continuity-Bridge is the **public semantic MCP surface** (fixed IntegrateWise semantic contract). External AI clients (ChatGPT, Claude, Perplexity, Hermes) connect through the Bridge.\nThe **Descope MCP Adapter** (established at commit `5c15413e`, internal execution adapter) resolves Descope-managed outbound authorization and executes an already selected, governed, activated provider route. External AI clients must not connect directly to the Descope MCP execution surface.\n24.3 Responsibilities\nResolve Capability transport*hints[] to one of {nango, mcp, native, custom}.\nMint & cache short-lived conn* tokens through 08 / 14.\nAggregate Connector Deltas into a unified ConnectorDelta shape.\nHealth-impose per-transport breakers.\n24.4 Inputs\nCapabilityInvoked events (05).\nConnector HealthyChanged (08).\nAdmin transport overrides.\n24.5 Outputs\nResolved writes through chosen transport.\nAggregated ConnectorDelta stream into Spine (02) and Signals (10).\n24.6 Events produced\nIntegrationResolved, IntegrationDispatched, IntegrationCompleted, IntegrationFailed, IntegrationTokenRefreshed, IntegrationBreakerOpened, IntegrationBreakerClosed.\n24.7 Events consumed\nEvery CapabilityInvoked, ConnectorHealthyChanged, MCPDiscoveryUpdated.\n24.8 APIs\nPOST /integration/resolve, GET /integration/{cap_id}/transports, POST /integration/{cap_id}/dispatch, GET /integration/breakers.\n24.9 State transitions\nidle → resolving → dispatching → succeeded | failed → cooldown → idle.\n\n24.10 Failure handling\nTransport failure → breaker open per transport; subsequent attempts use next transport.\nAfter N consecutive breaker opens → emit ConnectorRetired (08.10).\n24.11 Extension points\nNew transports via INTEGRATION_TRANSPORT(name).\nCustom resolver strategies INTEGRATION_RESOLVER(name).\n"}