Integrations
Integration setup for your IT administrator
Understand responsibility for OAuth applications, provider permissions and callback configuration.
Customer and Sorsana responsibilities
Customers select properties/accounts, grant provider access, maintain DNS and sender ownership, approve WhatsApp templates and test delivery. Sorsana manages the hosted API address, encryption key, database migrations, background workers, scheduler and platform OAuth configuration. Ordinary customer setup does not require deployment commands or database access.
Use the standard sign-in first
Save the Google or Microsoft connection and choose Connect account. If sign-in is disabled, ask Sorsana support to enable the platform application. If your organisation requires its own OAuth application, agree its provider configuration with Sorsana before entering credentials in Advanced: use an OAuth app supplied by your IT team.
Bring your own OAuth application
An IT administrator performs these steps; never put a client secret in a help request or public screenshot.
- Obtain the exact public OAuth callback address from Sorsana support. It ends in /connectors/oauth/callback and may include an API version prefix. Register it exactly; do not substitute the website URL.
- For Google, create a web OAuth client, enable Gmail and/or Calendar APIs, configure the consent screen and authorised users, and complete any verification Google requires for the requested scopes.
- For Microsoft, create a web application registration appropriate for your organisation and grant delegated calendar or mail scopes. Shared mailbox users also need Exchange access and shared read/send permissions. Ask your tenant administrator to approve consent where required.
- Store the client ID/secret in the relevant connection’s advanced fields, Save settings, Connect account and Test. Repeat separately for mail and calendar when both are used.
- Arrange secret rotation before expiry. Update the saved secret and reconnect/test; do not remove access from a working account until replacement access is verified.
Google push setup belongs to hosting
Gmail push needs a Pub/Sub topic in the OAuth application’s Google Cloud project, Gmail publisher permission and an authenticated push subscription. Sorsana verifies the service-account identity, audience and subscription. Coordinate custom OAuth projects with support; mail polling still works if push is not configured. Customers should not create an unauthenticated public callback.
Provider references
Use current provider instructions for consent, permissions and push configuration.