Our Google Workspace (Gmail) connector enables Leadfwd Engage to send emails through individual user mailboxes (each requires separate authorization) and to read email replies that originated from messages sent by Leadfwd Engage.
Step-by-step process (3-5 minutes to complete):
1. Register a Google Project
2. Enable Gmail API
3. Create Credentials
4. Configure Oauth Consent Screen, Set Permissions (Scopes) and Domain Paths.
5. Copy your Client ID and Secret. Apply to Google Workspace Settings in Leadfwd.
Business Accounts (Workspace) only: Our Google Workspace (Gmail) connector only works with business accounts. It doesn't not work with free personal Gmail accounts.
Registering a Google Platform Web Application (it's free!)
Registering a Google Web Application takes less than 5 minutes and is completely free. Why does Leadfwd require this? Two reasons:
To grant our customers complete control over the data integration between Google Workspace (Gmail) and Leadfwd.
By controlling your own connector web application, your organization will not be at risk of sending violations from any other organizations using Leadfwd, as each organization has their own unique Application ID with Google.
Register a Google Project
You'll be required to login as an Administrator of your Gmail (Google Workspace) organization.
Name your Project accordingly with a label that you will recognize as being purposed for Leadfwd (i.e. Leadfwd Connector), then click Create.
Enable Gmail API
Once your Project is named and created, navigate to (https://console.cloud.google.com/apis/library/gmail.googleapis.com) and click 'Enable' for the Gmail API.
Your Project (i.e. Leadfwd Connector Example) should be selected in the top menu next to Google Cloud Platform.
Once the Gmail API is enabled, then continue to this link (https://console.cloud.google.com/apis/credentials/wizard) to set up credentials for the API or click the button from the Gmail API panel 'Create Credentials'
Which API are you using?
Start typing 'Gmail' to select Gmail API in the drop menu or scroll through the options to find it.
What data will you be accessing?
Select: User data
Set up Oauth Consent Screen
Select 'Internal' for the user type and click 'Create'
In order to connect mailboxes for Engage users or AI Sales Agents, each Gmail user will be required to grant consent to the application.
You can choose any name for the application. We recommend 'Leadfwd Connector' so that your team will recognize the usage and purpose of the authorization.
User support email
You will choose from a list of existing mailboxes and groups associated with your domain. We typically recommend using the email address of whomever is creating this application project for your team.
Developer contact information
We recommend you use the same email address as the 'User support email' selection, so your team can receive communication on any changes to the project.
Based on the application domain that your Leadfwd account is deployed on, you'll need to enter it here. It will either be in25app.com, securenetgate9.com or inboxgateway.com. If your account is deployed from mx8.inboxgateway.com or mx9.inboxgateway.com, you'll simply use inboxgateway.com for this input only.
Click Save and Continue...
Permissions / Scopes
Scopes determine the type of permission the connector will have to your Gmail instance. Leadfwd only requires read-only access to mailboxes (to find replies to Sequences) and access to send emails using a mailbox with Sequences.
From the list of available scopes, select gmail.readonly and gmail.send:
Then, click Update...
Oauth Client ID
Now that the Oauth Consent Screen is set up, you can proceed to set up credentials for the connector. To do that navigate to the Credentials panel and from that view click on Create Credentials / Oauth Client ID at the top of the panel.
Select Web application
Enter Leadfwd Connector or any name that is easily identifiable for your team in the future.
This is the domain that your Leadfwd account is deployed from. When you login to your account you will see one of the following domains: in25app.com, securenetgate9.com, mx8.inboxgateway.com, mx9.inboxgateway.com.
Unlike Authorized domains for Oauth, you'll use the full domain (mx8.inboxgateway.com and mx9.inboxgateway.com) instead of just inboxgateway.com, if your account is deployed from either of those domains.
Enter that URL in the field provided.
Authorized redirect URI
The authorized redirect URIs instruct the connector on where to send users once they perform actions, like connecting their inbox.
Using your application domain as shown in the previous step, replace <domain> add the following URIs:
Tip: To add another URI you'll need to click +ADD URI.
Now that your Connector is created, you'll receive a confirmation message with a Client ID. This is the unique identifier for your Oauth connector. Click Done...
You will be immediately redirected to the Oauth 2.0 Client IDs Manager. Click to 'Edit' your new Oauth client.
Add your Client ID and Client Secret
From your Leadfwd account Navigate to Settings > Integrations > Available Apps and select Enable Google Workspace.
From the dialog that is displayed, you will need to first copy your Client ID and paste it into the Gmail Connector Manager in your Leadfwd account and then your Client secret.
You'll be prompted to connect using credentials from a Gmail account associated with the organization and domain that your connect was just created for. This is only for testing and these credentials are not committed for actual usage in the platform.