DocsDeveloper integration

Developer overview and open interfaces

Explore third-party apps, MCP, business APIs and app contracts with explicit availability.

Choose an integration layer

App integrations bring business capabilities into the workspace. MCP exposes external tools and resources to executors. Business APIs exchange project and task data. App manifests render approved data as workspace apps. Identify data direction and side effects before choosing a route.

Integration layers and status
LayerCurrent statusPrerequisite
Third-party connectionsCatalog and provider configuration exist in source; validate each connectionDeployment configuration, authorization and a minimal verified call
MCP toolsSource includes stdio/HTTP configuration and executionCompatible server, trusted runtime and tool grants
Business REST APIPublic design draft; general developer service not confirmed liveEndpoint, identity model and test environment must be provisioned
App manifestsReference for the current constrained JSON schemaRuntime support, source access and publication checks
Webhook eventsDelivery and signature design draftSubscription, key management and retry services

Minimum integration brief

Provide application name, maintainer, purpose, test identity, fields, read/write scopes, endpoints, authentication, volume and incident contact. State whether identities are personal or organizational, model exposure, retention and cleanup after disabling.

Separate development, testing and release

Integrate with redacted data and separate credentials, then test allow, deny, revoke, timeout and retry paths. Release requires compatibility versions, ownership, quotas, monitoring and rollback. Success in development still requires network and identity validation in the target deployment.

Versioning and compatibility

Drafts may change before release. Freeze versions, fields, errors, limits and upgrade windows for contracted integrations. Breaking changes require a new version and migration guidance. Unknown-field handling depends on the contract: the current app manifest is closed and rejects unknown fields.

Authorization, licensing and ownership

Integrators need rights to interfaces, accounts, data and dependencies. Protocol publication does not grant rights to third-party marks, source or business data. Distributable SDKs, samples and adapters need explicit licenses. Agree customer-specific logic, general connectors and maintenance ownership in the engagement.

Choose the next guide

Begin with one read-only interface or tool. Verify a reproducible path before adding writes or events. FDE work can include adaptation, integration testing and handover.

All documentationNext guide

Still have a question?

Explore expert support