Google Business Profile (formerly Google My Business) is Google's free tool for managing how a business appears on Google Search and Maps. The Google Business Profile connector reads accounts, locations, attributes, reviews, posts, photos and videos, verifications, and performance metrics such as impressions, calls, website clicks, direction requests, and search keywords. It can also reply to reviews and publish posts on a location's profile.
Power end-to-end data operations for your Google Business Profile API with Nexla. Our bi-directional Google Business Profile connector is purpose-built for Google Business Profile, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Google Business Profile or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Google Business Profile workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Google Business Profile uses OAuth 2.0 with your own Google Cloud OAuth client. Google only lets approved Google Cloud projects call the Business Profile APIs, so you set up the project, get it approved, and then give Nexla its client ID and client secret. When you authorize the credential, you sign in with the Google account that owns or manages your Business Profile.
Make sure your Business Profile is verified and has been active for at least 60 days, and that it lists a website for the business. Google requires both before it approves API access.
In the Google Cloud console, create a project (or pick an existing one), and note its Project number from the project dashboard.
Submit the Business Profile API contact form, and choose Application for Basic API Access. Include the project number, and send the request from an email address that is an owner or manager of the Business Profile.
Wait for Google's approval. To check it, open the quotas for the Business Profile APIs in the Cloud console: a quota of 0 queries per minute means the project is not approved yet, and 300 means it is approved.
In the Cloud console, under APIs & Services > Library, enable the Business Profile APIs that the templates use: Google My Business API, My Business Account Management API, My Business Business Information API, Business Profile Performance API, and My Business Verifications API.
Configure the OAuth consent screen, and add the scope https://www.googleapis.com/auth/business.manage. While the app is in Testing mode, add the Google account you will sign in with as a test user.
Under APIs & Services > Credentials, click Create credentials > OAuth client ID, and choose Web application.
Under Authorized redirect URIs, add https://dataops.nexla.io/nexla-api/oauth/callback.
Create the client, and copy the Client ID and Client secret.
Templates need IDs from your account
Most templates need a numeric Account ID, Location ID, or Review ID. Run List Accounts first to find the account ID (the number after accounts/ in each name), then List Locations to find location IDs (the number after locations/), and List Reviews to find review IDs. The review, post, and media templates need the ID of the account that owns the location; for a location in a location group, that is the location group's account ID.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Enter the client ID of your Google Cloud OAuth client in the Client ID field, and its client secret in the Client Secret field. See Prerequisites.
The client secret is sensitive and should be kept secure. If it is exposed, reset it in the Google Cloud console under APIs & Services > Credentials, and update this credential.
Click Authorize, and sign in with the Google account that owns or manages your Business Profile. Grant the requested access to manage your Business Profile listings (scope business.manage). Nexla requests offline access, so it can refresh the access token without asking you to sign in again.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
Nexla tests the credential by listing the Business Profile accounts the signed-in Google account can manage.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Google Business Profile connector tile, then select the credential that will be used to connect to your Google Business Profile account, and click Next; or, create a new Google Business Profile credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Google Business Profile endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below, grouped by area.
Templates that say Nexla reads every page follow Google's nextPageToken; all other templates make a single request. Each template reads data for one account or location; enter its ID as described in Prerequisites.
Lists the Business Profile accounts the signed-in Google account can manage, including personal accounts, location groups, and organizations, with each account's name (accounts/{id}), account name, type, and your role. Start here to find account IDs.
Calls GET /v1/accounts?pageSize=20.
Nexla follows Google's nextPageToken and reads every page automatically.
Lists the locations (business listings) in an account, with title, address, phone numbers, website, categories, hours, and open status. Use it to find location IDs.
Calls GET /v1/accounts/{Account ID}/locations?readMask={Read Mask}&filter={Filter}&pageSize=100.
Nexla follows Google's nextPageToken and reads every page automatically.
Account ID (required): The numeric Business Profile account ID: the number after accounts/ in the name returned by List Accounts.
Read Mask (required; default name,title,storeCode,storefrontAddress,phoneNumbers,websiteUri,categories,regularHours,specialHours,openInfo,metadata,latlng,labels,profile,serviceArea,languageCode): Comma-separated location fields to return; Google requires this setting. The default returns the name, store code, address, phone numbers, website, categories, regular and special hours, open status, metadata, coordinates, labels, profile description, service area, and language.
Filter (optional): An optional Google filter expression, such as title="Main St" or storefrontAddress.locality="Austin". Leave it empty to return every location.
Returns one location's listing details, such as title, address, phone numbers, website, categories, hours, status, and profile description.
Calls GET /v1/locations/{Location ID}?readMask={Read Mask}.
Location ID (required): The numeric location ID: the number after locations/ in the name returned by List Locations.
Read Mask (required; default name,title,storeCode,storefrontAddress,phoneNumbers,websiteUri,categories,regularHours,specialHours,openInfo,metadata,latlng,labels,profile,serviceArea,languageCode): Comma-separated location fields to return; Google requires this setting. The default returns the name, store code, address, phone numbers, website, categories, regular and special hours, open status, metadata, coordinates, labels, profile description, service area, and language.
Lists the posts (updates, offers, events, and alerts) published on a location's profile, with summary, topic type, state, call to action, media, search URL, and create time.
Calls GET /v4/accounts/{Account ID}/locations/{Location ID}/localPosts?pageSize=100.
Nexla follows Google's nextPageToken and reads every page automatically.
Account ID (required): The numeric Business Profile account ID: the number after accounts/ in the name returned by List Accounts.
Location ID (required): The numeric location ID: the number after locations/ in the name returned by List Locations.
These templates read the Business Profile Performance API. Google can take a few days to finish a day's metrics, so the most recent days can be incomplete or missing.
Google takes metric dates as separate year, month, and day values. Daily Performance Metrics (one day) and Search Keyword Impressions (monthly) work them out from the Days Ago or Months Ago setting. If Google rejects the date range, or you need a longer period, use Daily Performance Metrics (date range) and enter the dates yourself, and check the first run's results against the Performance view in Business Profile.
Daily Performance Metrics (one day)
Returns one day of performance metrics for a location: impressions on Google Search and Maps by desktop and mobile, conversations, direction requests, call clicks, website clicks, bookings, food orders, and food menu clicks. Run it daily to build up a history.
Calls GET /v1/locations/{Location ID}:fetchMultiDailyMetricsTimeSeries with all eleven daily metrics, for the single day Days Ago days before today.
Location ID (required): The numeric location ID: the number after locations/ in the name returned by List Locations.
Days Ago (required; default 3): The day to read, as a number of days before today. The default 3 leaves time for Google to finish the day's metrics.
Returns the same performance metrics as Daily Performance Metrics (one day) for a date range you enter, with one record per metric holding a value for each day.
Calls GET /v1/locations/{Location ID}:fetchMultiDailyMetricsTimeSeries with all eleven daily metrics.
Location ID (required): The numeric location ID: the number after locations/ in the name returned by List Locations.
Start Year (required): The year the range starts, as four digits, for example 2026.
Start Month (required): The month the range starts, as a number from 1 to 12.
Start Day (required): The day of the month the range starts, as a number from 1 to 31.
End Year (required): The year the range ends, as four digits. The end date is included.
End Month (required): The month the range ends, as a number from 1 to 12.
End Day (required): The day of the month the range ends, as a number from 1 to 31.
Enter each part as a plain number, for example 2026, 11, and 5. These settings have no default; update them whenever you want a different range.
Lists the search keywords people used to find a location on Google, with the impressions for each, for one calendar month.
Calls GET /v1/locations/{Location ID}/searchkeywords/impressions/monthly for the single calendar month Months Ago months before the current month. Nexla follows Google's nextPageToken and reads every page automatically.
Location ID (required): The numeric location ID: the number after locations/ in the name returned by List Locations.
Months Ago (required; default 1): The month to read, as a number of months before the current month. The default 1 reads last month.
Lists the verification attempts for a location, with method (such as postcard, phone, or email), state, and create time. Use it to find out why a location is not live.
Calls GET /v1/locations/{Location ID}/verifications?pageSize=100.
Nexla follows Google's nextPageToken and reads every page automatically.
Location ID (required): The numeric location ID: the number after locations/ in the name returned by List Locations.
Shows whether you can manage a location (hasVoiceOfMerchant and hasBusinessAuthority) and, if not, what to do next, such as verify the location, resolve an ownership conflict, or wait.
Calls GET /v1/locations/{Location ID}/VoiceOfMerchantState.
Location ID (required): The numeric location ID: the number after locations/ in the name returned by List Locations.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Google Business Profile data sources can also be manually configured to ingest data from any valid Google Business Profile API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
Google Business Profile is split across several Google APIs, each on its own host: mybusinessaccountmanagement.googleapis.com, mybusinessbusinessinformation.googleapis.com, businessprofileperformance.googleapis.com, mybusinessverifications.googleapis.com, and mybusiness.googleapis.com (v4, for reviews, posts, and media). The credential's access token works on all of them.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Google Business Profile data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the Google Business Profile destination, and select the Send to Destination option from the menu. Select the Google Business Profile connector from the list of available destination connectors, then select the credential that will be used to connect to your Google Business Profile account, and click Next; or, create a new Google Business Profile credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Google Business Profile endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
These templates publish content that anyone can see on Google Search and Maps. Test them with a single record before sending a full Nexset. The connector does not edit location details, such as hours or address; make those changes in Business Profile.
Create Local Post
Publishes a post on a location's Business Profile. Each record becomes one post.
Sends POST /v4/accounts/{Account ID}/locations/{Location ID}/localPosts.
Account ID (required): The numeric Business Profile account ID: the number after accounts/ in the name returned by List Accounts.
Location ID (required): The numeric location ID: the number after locations/ in the name returned by List Locations.
Each record is sent as the JSON request body, one request per record, and must be a Google LocalPost: for example summary, topicType (STANDARD, EVENT, OFFER, or ALERT), and optionally callToAction, event, offer, and media.
Google Business Profile destinations can also be manually configured to send data to any valid Google Business Profile API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Google Business Profile endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the Google Business Profile endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.