Перейти к содержимому
TakoAPI
Назад к навыкам

twenty-oauth-mastery

от avirweb

Coding Agents & IDEs
780Число загрузок по данным clawskills.sh
0Просмотры
0 лайковВойдите, чтобы поставить лайк навыку
—Ещё нет оценок
Ваша оценка

Кратко

**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. 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

ВЫВОД

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 — любой кодинг-агент, которым пользуетесь.

Ссылки