This guide walks you through the complete process of connecting Google Sheets (Source) to Brevo (Destination) using the sysConnector platform. Once configured, data from Google Sheets will sync automatically into Brevo.
Prerequisites
Make sure you have the following:
Service Account JSON*
Brevo Credentials:
API Key
Step 1: Create a New Connection
Log in to the sysConnector.
Click Create Connection.

If your app is missing, click Request Integration to notify the sysConnector team.
Step 2: Configure Google Sheets as the Source
Select Google Sheets
Choose Google Sheets from the app list
Click Next

Upload Service Account JSON
Enter an Account Name
Example: Google Sheets Marketing Data
Paste the Service Account JSON file you downloaded earlier
Click Connect to Google Sheets
Once the connection is successful, click Next

How to Create Service Account JSON
1. Create a Google Cloud Project
Go to Google Cloud Console
Click Select Project → New Project
Enter a project name (e.g., Sheets Integration Project)
Click Create
2. Enable Google Sheets API
Go to APIs & Services → Library
Search for Google Sheets API
Click Enable
(Optional: Enable Google Drive API for file access)
3. Create a Service Account
Go to APIs & Services → Credentials
Click Create Credentials → Service Account
Enter Name: Sheets Connector Account
Click Create and Continue
Skip optional roles → Click Done
4. Generate Service Account JSON Key
Open the created Service Account
Go to Keys tab
Click Add Key → Create New Key
Select JSON
Click Create
A JSON file will automatically download. This is your Service Account JSON. Keep this file secure and use it in sysConnector
Select Spreadsheet and Worksheet
Enter the Spreadsheet ID
Click Load Sheets
Select the Worksheet (tab) containing your data
Click Next

Important Note
Make sure your Google Sheet is shared with the email indicated in the Service Account JSON (client_email).
Without this, sysConnector will not be able to access your sheet.
Step 3: Configure Brevo as the Destination
Select Brevo as the Destination App.

Enter a Destination Account Name
Example:Brevo MarketingorBrevo CRM Prod.Enter required credentials:
API Key
Click Connect to Brevo to verify access.

How to Generate a Brevo API Key
Log in to your Brevo account
Click your profile name (top-right corner)
Go to Settings → SMTP & API → API Keys
Click Generate a new API key
Enter a name for your app
Example: sysConnector IntegrationClick Generate
Copy the API key
Important:
Your API key is only shown once — make sure to copy and save it
If you lose it, you will need to generate a new one
Step 4: Define Connection Settings
Connection Name
Use a clear, descriptive name such as:Google Sheet Leads 2026Project Selection
Choose an existing Project (folder) or use Unassigned.Sync Frequency
Select Event Space to enable real-time syncing when a lead is submitted.

Projects act like folders inside sysConnector.
Select an existing Project, or
Leave it as Unassigned if no structure exists yet
This is especially useful for:
Separating marketing vs sales workflows
Organizing by region or business unit
Controlling user access permissions
Step 5: Field Mapping and Data Transformation
This step defines exactly how data collected in Google Sheet is translated, formatted, and delivered into Brevo. Proper configuration here ensures clean data, accurate reporting, and successful automation.
5.1 Basic Field Mapping
This section establishes a direct relationship between Google Sheet fields (source) and Brevo fields (destination).
Process:
For each data point, select the Google Sheet field on the left.
Map it to the corresponding Brevo field on the right.
Example:
Google Sheet field Name → Brevo field First Name
Google Sheet field Email → Brevo Email
If a required Brevo field is not mapped, records may fail to sync or be rejected.

5.2 Using Custom Text
The Custom Text feature allows you to send a fixed value that does not exist in the Google Sheet itself.
Common Use Case:
Create a field in Brevo called Lead Source
Use Custom Text to automatically populate it with Google Sheet for every lead coming through this connection
This is especially useful for campaign tracking, reporting, and segmentation.

5.3 Custom Transformations (Merging and Formatting)
Custom transformations allow you to manipulate or enhance data before it reaches Brevo, which is useful when the data structures between systems do not align perfectly.
Merge Fields
You can select multiple Google Sheet fields and combine them into a single Brevo field.
You may apply a divider (comma, dash, pipe, etc.) between values for readability.
Example:
If your Google Sheet contains separate columns for First Name and Last Name, you can merge them into a single Full Name field in Brevo (e.g., John Doe).
Prefix and Postfix
You can add text before (prefix) or after (postfix) a value.
Example:
Prefix:
GS-Result:
GS-john.doe@email.co
This is useful for tagging, internal labeling, or adding context to incoming data.

5.4 Data Type Conversion
In some cases, Google Sheet sends data in a format that does not match the required data type in Brevo.
Example:
Google Sheet sends a value as Text
Brevo requires an Integer
How sysConnector Handles This:
During testing, sysConnector automatically detects mismatched data types.
Since Brevo field types are fixed, you must adjust the Source Type in sysConnector to match the destination field.
This ensures records are accepted and processed correctly.
5.5 Mandatory Testing and Validation
Before a connection can be activated, mapping must be tested successfully.
Process:
Enter sample test data for every mapped field.
Click Test Mapping.
The system validates formatting (e.g., email fields must contain valid email formats).
After a successful test, log in to Brevo and confirm the test record appears correctly.
Activation is blocked until testing passes.

Step 6: Testing and Activation
Enter sample test data and click Test Mapping.
This step is mandatory before activation.Log in to Brevo and confirm the test data was received correctly.
Click Save and Activate to begin live syncing.

Managing Your Connection
Monitoring
Go to Reports to view:
Successful lead transfers
Failed sync attempts
Logs from the last 24 hours to 30 days