Saltar al contenido
TakoAPI
Volver a skills

twenty-oauth-mastery

por avirweb

Coding Agents & IDEs
780Descargas según clawskills.sh
0Vistas
0 me gustaInicia sesión para dar me gusta a esta skill
—Aún sin valoraciones
Tu valoración

Resumen

**Author**: Generated from extensive OAuth debugging sessions in OpenCode.

Descripción

Qué hace esta skill

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.

Cuándo usarla

  • 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

Flujo de trabajo de ejemplo

ENTRADA

User asks: Why does OAuth login succeed but Gmail sync never starts?

AGENTE
  1. 1

    Check the validate() method in google.auth.strategy.ts to confirm accessToken and refreshToken are included in the return object

  2. 2

    Verify auth.service.ts calls oauthSyncService.setupSyncForOAuthUser() after a successful login

  3. 3

    Confirm Google OAuth scopes include gmail.readonly and calendar.events

  4. 4

    Check that CALENDAR_PROVIDER_GOOGLE_ENABLED and MESSAGING_PROVIDER_GMAIL_ENABLED are set to true in the environment

  5. 5

    Query the connectedAccount table to confirm tokens were persisted and sync channels exist

SALIDA

Root cause identified as tokens lost in validate(), fix applied, sync channels created with syncStatus=ONGOING

Requisitos

  • Google Cloud Console project with OAuth 2.0 credentials (client ID and client secret)
  • Redirect URIs and authorized origins configured in Google Cloud Console

Instalación

clawhub install avirweb/twenty-oauth-mastery

Ejecuta el comando de la CLI o pega el prompt en Claude Code, Cursor, Codex o el agente de programación que uses.

Enlaces