Building connected applications
Start with a bounded interface and a concrete job for the user.
Choose the smallest useful integration
Expose a supported HTTPS MCP server or an OpenAPI tool source for actions a bot should call. Use a bot webhook when an external event should start supported work inside One.
Describe the user’s goal, input data, required permissions, side effects, and failure behavior. Separate read actions from write actions, and avoid asking for broader access than the task needs.
Design for real operation
Make write actions retry-safe where possible. Validate requests, scope access to the right user and workspace, bound response sizes, and define how credentials can be rotated or revoked.
Use fictional data and offline tests during development. An integration should fail clearly when a required provider or permission is missing.
Apply to the ecosystem program
The integration program is application-based. There is no already-operational public marketplace or automatic listing flow. Approved contributors may receive the project access needed for an agreed contribution.
Commercial terms, review criteria, maintenance responsibilities, and distribution are agreed with Lughlabs before release.