Integrations overview
Learn the six connection lanes in MoodLens so you can pick the right setup path and describe it accurately.
MoodLens uses multiple connection lanes
Live connection: a persistent linked service used over time, such as GitHub.
One-time import: migration pull-ins from Trello, Asana, Jira, Notion, or ClickUp.
Partner app install: another platform offers "Connect MoodLens" through developer-app OAuth.
Direct API access: a trusted backend calls MoodLens with an external API key.
Assistant bridge: an assistant client connects through the MoodLens MCP server.
Outbound event flow: MoodLens pushes events to another system through webhooks.
Permission model
Most integration management is admin-only in shared workspaces.
API keys can be created and revoked only by workspace admins or owners.
Developer apps, webhooks, and workspace secrets are admin-managed.
Messaging links require the user to be a workspace member.
AI employees are shared at the workspace level, while personal conversation threads stay user-scoped.
Wording rules to keep support copy honest
Do not call imports "sync" unless there is a real ongoing sync.
Do not call MCP "the API" unless the article is specifically about assistant access.
Do not call developer apps "API keys". They are OAuth apps with client credentials.
Do not describe outbound webhooks as inbound integrations.