Use Google sign-in in your Crisp app.
Sign in with Google, and Google APIs on their behalf.
Let people sign in with their Google account, and with the scopes you choose read their Calendar, Gmail or Drive on their behalf, through an OAuth client you create in Google Cloud. The same client can be reused by every other Google connector.
What you need.
Create an app in your Google sign-in account and paste its client id and secret. Your app runs the sign-in itself, so people sign in with Google sign-in on your own pages.
- Client id
GOOGLE_OAUTH_CLIENT_ID- console.cloud.google.com, Credentials, OAuth client (one client serves every Google connector). Ends with .apps.googleusercontent.com
- Client secret
GOOGLE_OAUTH_CLIENT_SECRET- The same OAuth client. Starts with GOCSPX-
How to connect.
-
Open your project, or start a new one from the dashboard.
-
Open the workspace menu and choose Connectors, then pick Google sign-in.
-
Paste the keys and save. Your preview restarts, and your app can use the service from then on.
Then ask for the feature
- “Add Sign in with Google”
- “Put bookings on the customer's Google Calendar”
What happens to your keys.
- Each key is saved as a private setting of your project, under the name shown above.
- The AI that builds your app sees only the names. It writes code that reads each key by name, and never the value.
- The values reach your preview and your published app, and never the chat, the code or the logs.
- Open Connectors in your project to replace a key or disconnect the service. Publish again so your live app uses the change.
Service names and logos belong to their owners; Crisp is not affiliated with them. A service changes its keys and pages now and then. Found something out of date? Tell us and we will correct it.
Ask for the feature, and Crisp builds it with Google sign-in.
Free plan with $3 of AI usage a month, no credit card. Pro is $20 a month. See pricing.
No credit card. Your code and data stay yours.