You can validate addresses, perform geocoding, and enhance location services across your workflows with the Google Maps integration. This eliminates shipping errors, improves field service routing, and ensures employee and vendor addresses are always accurate and deliverable.
Usecases
By connecting Google Maps, your teams can:
Standardize addresses: Validate and format employee addresses in user profiles during the onboarding process.
Verify asset locations: Confirm addresses for asset management and shipping purposes.
Manage changes: Validate location data accurately within change requests.
Permissions
The Google Maps integration uses an API key to authenticate requests. Before connecting, you must configure your Google Cloud project with the following requirements:
Requirement | Purpose |
Address Validation API enabled | The integration calls Google's Address Validation API to validate and standardize addresses, returning formatted addresses, geocoordinates, and validation flags. |
Billing enabled on Google Cloud project | Address Validation API is a paid API and requires billing to be enabled. |
API key restriction (recommended) | Restrict your API key to only the Address Validation API for security to prevent misuse if the key is leaked. |
Setup
Configure your Google Cloud project:
Log in to your Google Cloud Console
Enable the Address Validation API in your project. Also ensure Billing is enabled.
Navigate to APIs & Services > Credentials
Click Create Credentials > API Key
Recommended: Click Restrict Key and limit it to the Address Validation API only
Copy and securely store the API key
In your Atomicwork account, navigate to Settings > App Store > Google Maps.
Click on Connect
Enter your Google Cloud API key click on Test to test the connection.
Click on Connect to activate the integration.
Supported workflow actions
You can use the Validate Address action, which standardizes and verifies location data using Google's services.
Configure input fields
Address (Required) - Enter the full address, including street, city, state, and postal code.
Region code (Optional) - Provide a country code (for example, US, IN, GB) to improve validation accuracy and prevent Google from misinterpreting the country.
Response fields
When a workflow runs the Validate Address action, it returns detailed location data that you can use in subsequent workflow actions:
Formatted address: The standardized version of the input address.
Address complete: A true or false value indicating if the address has all required components.
Coordinates: The latitude and longitude of the location.
Validation flags: Indicators showing if components were unconfirmed, inferred, or replaced.
Granularity: Precision levels for the validation and geocode.
Place ID: The unique Google Place identifier.
Troubleshooting
If you encounter errors while using the integration, review the following solutions:
Error | Cause | Resolution |
"api_key is null" | The integration configuration is missing the API key. | Navigate to your integration settings and add the required API key. |
403 Forbidden | The provided API key does not have the Address Validation API enabled, or billing is not set up on your Google Cloud project. | Enable the Address Validation API in your Google Cloud project and ensure billing is enabled. |
Invalid address results | Google may misinterpret the intended country without a region code. | Provide a region code (e.g., |
Quota exceeded | You have reached your Google Maps API usage limits. | Check your Google Cloud Console to review quota limits and billing status. |
