Scaffold the Google Meet app
Context
First PR of a new public app that imports Google Meet recordings, transcripts and Gemini notes into Call Recordings. It follows the same pattern as the existing Teams, Fathom and Granola apps: read the meeting artifacts after the call through the provider API (Meet REST API v2) and write them to the standard callRecording object, with no meeting bot.
The work is split into small PRs, each based on main and merged before the next one starts:
- App shell (this PR)
- Test setup (vitest, unit and integration tests)
- Google OAuth connection
- Meet API client and conference listing
- Transcript import into Call Recordings with calendar event matching
- Gemini notes and recordings
- History import and daily catch-up
- README, setup guide, logo and marketplace listing
What this PR does
Adds packages/twenty-apps/public/google-meet, generated with twenty app init and then aligned with the neighbouring apps:
application-config.tswith the app name, description and marketplace metadata- A default role that grants no access to records or settings. Permissions get added by the PRs that need them.
- Lint and TypeScript config copied from the Teams app
package.jsonandyarn.lockwith only the dependencies needed to lint, typecheck and build
Removed from the generated template: the example page, front component, navigation item and health check function, the .github folder (CI rejects it inside app folders), and the test files, which come back in the next PR together with vitest.
The app does nothing yet. It is not published to npm and has no twenty-app keyword, so it does not appear in the marketplace.
Checks
Run locally in the app folder: yarn install --immutable, yarn lint, yarn typecheck and twenty app build all pass.