Skip to main content
Connect your Base44 app to Gmail to send emails based on events, data changes, or schedules in your app. Use Gmail to deliver alerts, approvals, digests, and reports, either from one shared account or from each person’s own inbox.
Which type should you use? Use a connector for app builders when your app sends email from one Gmail account for everyone, for example an ops inbox that emails weekly reports. Use a connector for app users when each person sends email from their own Gmail account.
You need a Builder plan or higher to use connectors in your app.

What you can do

Send event alerts

Email the right people when something happens in your app, such as a new ticket, approval, or failure.

Send scheduled digests

Generate daily or weekly summaries of activity, metrics, or changes and email them automatically.

Notify your users

Email a person when their own record changes, such as a document approval or status update.
Example prompts for the AI chat

At a glance

Type identifier
gmail
Auth model
OAuth
Connector types
For app builders, For app users
Connection config
None

Connect it

Connect one Gmail account that all flows in your app use.To connect Gmail:
  1. Go to your app editor.
  2. Describe what you want to do with Gmail in the AI chat, for example: Connect this app to Gmail and email me when a new ticket is created.
  3. Review the Action required and Required permissions in the side panel.
  4. Click Connect to Gmail.
  5. In the Google window, select the account you want to connect, review the permissions, and click Allow.
  6. Return to the editor and let the AI finish creating the flows that use Gmail.

Use it in a backend function

Once Gmail is connected, your backend functions can retrieve an access token and call the Gmail API directly. Base44 handles the OAuth flow and token storage.
  • For a shared connection, use getConnection() to retrieve the token.
  • For an app user connection, use getCurrentAppUserConnection() so each request uses the signed-in person’s token.
This is a simplified example. The setup and full code patterns are the same for every connector. See the developer guides for the complete pattern:

Shared connectors

Configure, deploy, and call a shared connection from a backend function.

App user connectors

Retrieve a per-user token and call the API as the signed-in person.

Gmail scopes and permissions

When you connect Gmail, the connector requests permissions (scopes) that control what your app can do with your Gmail account. Below is the current list of Gmail scopes the connector may request.

Gmail scopes

  • gmail.send: Send email messages.
  • gmail.readonly: Read email messages and metadata.
  • gmail.modify: Modify messages, for example mark as read or move to folders.
  • gmail.compose: Create draft messages.
Scope lists may change over time. Always review the permissions shown during the connection flow.

Troubleshooting

The redirect URI registered in your Google OAuth app must exactly match one shown in View redirect URIs for your apps for that app. Each app has its own set of redirect URIs, so add every URI shown for the app you are connecting.
If your Google OAuth app is in testing mode, only approved test users can connect. Publish or move your OAuth app out of testing mode so anyone using your app can connect their own account.

FAQs

  1. Go to your app dashboard and click Integrations.
  2. Click the My integrations tab.
  3. Find Gmail and click the More Actions icon , then Switch account.
Yes. In the AI chat, specify the subject line, message body, formatting, recipients, and any dynamic fields.You can also edit the generated backend functions in Dashboard → Code → Functions to further customize the email payload.
Yes. Use a connector for app users so each person connects their own Gmail account. See the connectors overview.
Click the More actions icon on the connector in your app’s Integrations tab, then choose an option such as switch account, reconnect, or disconnect. Learn more about managing connectors.