Skip to main content

Public API Connector - Google Maps Integration

Description​

This connector demonstrates integration with a public API that doesn't require authentication at the connector level. The Google Maps Places API connector shows how to configure connectors for public services where authentication is handled through query parameters (API keys) rather than headers. This pattern is common for public APIs like mapping services, weather data, or other information services that use API key authentication in the request URL.

Use Case​

Used in an arborist CRM system to provide location services for job sites. The connector enables place search, address autocomplete, and location details retrieval. It helps users find and validate client site addresses, calculate distances between job locations, and provide accurate mapping for field service operations.

Key Features​

  • No authentication configuration at connector level
  • Public API endpoint access
  • API key passed as query parameter in actions
  • Direct HTTPS connection to Google services
  • Support for various Places API endpoints
  • Clean configuration for public services

JSON Definition​

{
  "name": "Google Maps Places API",
  "key": "google_maps_places_api",
  "description": "Google places API (https://developers.google.com/maps/documentation/places/web-service/search-find-place)",
  "configuration": {
    "baseUrl": "https://maps.googleapis.com/maps/api/place",
    "authentication": {}
  },
  "type": "rest_api"
}

Notes​

  • Empty authentication object indicates no header-based auth
  • API keys are typically appended as query parameters in action calls
  • The base URL points directly to Google's public API endpoint
  • Documentation link in description helps developers understand the API
  • This pattern works for any public API with key-based authentication
  • Rate limiting and quotas are managed by the API provider