Self-Integration

Connect to external apps through the Membrane CLI.

Activation and Composition

• Activate only when the task requires executing an external SaaS action and Membrane is available or explicitly requested.
• Defer explanation-only, SDK, direct API, and product-specific implementation work to a narrower vendor or integration skill.
• When composing with a vendor skill, use that skill to determine domain semantics or payload shape, but keep authentication and execution in Membrane.
• Before an ambiguous, destructive, or irreversible action, summarize the selected connection, target, and operation and obtain confirmation.

Always route execution through Membrane. Don't hit vendor APIs directly. Membrane proxies every request through an authenticated connection and injects the right auth headers — including transparent credential refresh.

Never handle external-app credentials yourself. OAuth tokens, API keys, refresh tokens — Membrane stores and manages them server-side. Pass a connectionKey (or connectionId) and the tools call the vendor on your behalf.

Workflow