Integrations

GitHub, imports, webhooks, and workspace secrets explained

A cleaner explanation of the connected-tool model in MoodLens so teams know what is live, what is imported, and what is operational infrastructure.

April 27, 20268 min readMoodLens Editorial Team

The fastest way to lose trust is calling every external tool a sync. This guide explains the real connection lanes in MoodLens.

Integrations

GitHub, imports, webhooks, and workspace secrets explained

GitHub is the live engineering lane
Imports are migration lanes
Webhooks and secrets are operational infrastructure

GitHub is the live engineering lane

GitHub is the main live engineering connection in MoodLens. Repositories are linked intentionally after workspace connection, and engineering activity stays attached to real delivery work instead of becoming a static import snapshot.

Imports are migration lanes

Trello, Jira, Asana, Notion, and ClickUp are better described as migration and setup lanes. They help teams move existing work into MoodLens and continue natively from there.

Webhooks and secrets are operational infrastructure

Outbound webhooks push events out of MoodLens. Workspace secrets hold sensitive credentials so automations and AI Employees can work with external systems without raw secret values being pasted into normal chat.

Apply the guide

Try it with one real project.

Try MoodLens free