twenty-oauth-mastery
由 avirweb 提供
Coding Agents & IDEs简介
**Author**: Generated from extensive OAuth debugging sessions in OpenCode.
描述
该技能的功能
OAuth authentication knowledge for Twenty CRM covering implementation patterns, common failure modes, and automatic email/calendar sync setup after login. Focuses on Passport.js strategy configuration, token management, domain allowlists, and the compile-then-deploy workflow Twenty requires for source changes to take effect.
Twenty's OAuth flow has several non-obvious failure points, like needing to rebuild and redeploy compiled JavaScript before source changes take effect, that generic OAuth documentation does not cover.
何时使用
- Fixing redirect loops after Google OAuth login completes
- Allowing both .com and .co company domains to authenticate
- Triggering automatic Gmail and Calendar sync on first OAuth sign-in
- Debugging token refresh failures in a self-hosted Twenty instance
- Tracing why the frontend stays on the welcome page instead of redirecting to the dashboard
示例工作流
User asks: Why does OAuth login succeed but Gmail sync never starts?
- 1
Check the validate() method in google.auth.strategy.ts to confirm accessToken and refreshToken are included in the return object
- 2
Verify auth.service.ts calls oauthSyncService.setupSyncForOAuthUser() after a successful login
- 3
Confirm Google OAuth scopes include gmail.readonly and calendar.events
- 4
Check that CALENDAR_PROVIDER_GOOGLE_ENABLED and MESSAGING_PROVIDER_GMAIL_ENABLED are set to true in the environment
- 5
Query the connectedAccount table to confirm tokens were persisted and sync channels exist
Root cause identified as tokens lost in validate(), fix applied, sync channels created with syncStatus=ONGOING
前置要求
- Google Cloud Console project with OAuth 2.0 credentials (client ID and client secret)
- Redirect URIs and authorized origins configured in Google Cloud Console
安装
clawhub install avirweb/twenty-oauth-mastery运行 CLI 命令,或把这段提示词粘贴到 Claude Code、Cursor、Codex 或你在用的任意编程智能体里。