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.
Please note: Our Google Workspace (Gmail) connector only works with business accounts. It doesn't not work with free 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 your Leadfwd application project with Google
To get started, click here to start the registration process. We'll walk you through the entire flow, step by step.
You'll be required to login as an Administrator of your Gmail (Google Workspace) organization.
Once you login, keep 'Create a project' selected and click Continue.
Once the Gmail API has been enabled for your new project, the next step is to authorize permissions (scopes) for how you'll use the API with Leadfwd. Click on Go to credentials.
Step 1. Credential Type
Which API are you using?
By default the API being used will be the Gmail API. Please leave that selection.
What data will you be accessing?
Select: User data
Step 2. Set up Oauth Consent Screen
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.
Click Save and Continue...
Step 3. 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...
Step 4. Oauth Client ID
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. Enter that URL in the field provided.
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.
Step 5. Copy/Paste Credentials
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.
You will be immediately redirected to the Oauth 2.0 Client IDs Manager. Click to 'Edit' your new Oauth client.
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.