Integration and AI employee troubleshooting
Use this guided checklist when MCP setup, webhooks, developer apps, extension features, or AI employee actions are not behaving as expected.
MCP and developer-platform checks
If MCP setup fails, confirm Node.js is installed, re-run the installer, restart the target client, and verify the config path.
If a developer app fails, confirm the redirect URL exactly matches an allowed redirect URI.
If a developer-app secret was rotated, old tokens are no longer valid.
If an app was deleted, installations must be recreated.
Webhook and extension checks
Confirm webhook URLs are HTTPS and publicly reachable, not local or private.
Verify the endpoint checks X-MoodLens-Signature against the raw request body.
If a webhook stopped firing, check whether it was auto-disabled after repeated failures.
For the extension, remember that browser-internal pages cannot be read and meeting extraction depends on readable page content.
AI employee checks
If an employee appears busy, another session may hold the employee lock.
If messaging-link setup fails, regenerate the code because it expires after 10 minutes.
If a voice call cannot start, the user may have hit their plan quota for employee calls.
Actual tool availability depends on the employee's permissions and the workspace's configured integrations and secrets.