Back to Connections

Calendar, Gmail, and HubSpot setup

Separate Google grants

Connect Sheets, Calendar, and Gmail separately. Calendar can create and edit events but cannot read unrelated calendar data. Gmail can send as you but cannot read the inbox. A connection is never silently widened.

Google Cloud

Use the dedicated data-access OAuth client and add the exact Google callback under your APP_URL. Configure test users, then submit calendar.events as sensitive and gmail.send as restricted. The unverified-app warning is expected during test-user development.

HubSpot app

Add the exact HubSpot callback, request only contact read/write scopes, and configure the client ID and secret. Weftyn encrypts rotating refresh tokens and refreshes short-lived access under a connection lock.

Safe flow behavior

Gmail is plain text, one recipient, no inbox access, and is capped by plan and per run. HubSpot contact upsert is retry-safe; timeline notes can duplicate on full-flow retries. Calendar flows should find before create when duplicate events matter.

Revoke and reconnect

Force expiry, revoke at the provider, confirm the reconnect state, then disconnect and reconnect from Settings. Disconnect attempts provider revocation before removing the encrypted local connection.