Google Meet
Rep connects Google Meet via their Workspace account; every booking page they host attaches a Meet link to the confirmation email and the calendar event. The meeting is owned by the rep so all their Workspace controls apply.
Everything Google Meet does inside Strkr.
- Auto-attach Google Meet link to every booking
- Per-user OAuth: meeting owned by the rep
- Covers booking pages and ad-hoc meetings
- Readiness chip in the team booking editor
Native code, not a shim.
OAuth where available
Google Meet will ship with a native OAuth flow when it lands. No pasted credentials for admins to rotate manually.
KMS-encrypted tokens
Access and refresh tokens are envelope-encrypted at rest using a dedicated customer-managed KMS key. Decryption only happens in Lambda memory during an active API call; plaintext tokens never land in a log.
Scoped to the connecting user
Each teammate connects their own Google Meet account. The token is scoped to that user and never gets reused by another user in the workspace.
Disconnect at any time
Admins or users can disconnect Google Meet from inside Strkr. Stored tokens are deleted and the provider's revocation endpoint is called within 24 hours.
Google Meet is on the roadmap.
We ship integrations as first-class native code, which takes a little longer than a Zapier shim. If Google Meet is a dealbreaker for your evaluation, reply to the welcome email after you start a trial and we'll flag it to the roadmap.