Skip to the operations

Address verification

Google Maps in a decision flow.

A Connection node calls Google Maps mid-decision with the credentials your own contract issued. Whatever comes back is data the rest of the flow can read, branch on, and keep in the decision's trace.

Category
Address verification
Type
Integration
Authentication
api_key
Test environment
Production host only

What a flow can call

2 operations, each one a step you can place on the canvas.

  1. GET/maps/api/geocode/json?address=$data.applicant_address&components=country:$data.applicant_country_code

    Validate and geocode an address

    Resolves a postal address to structured components and coordinates.

  2. GET/maps/api/geocode/json?latlng=$data.latitude,$data.longitude

    Validate coordinates against an address

    Converts captured coordinates to a structured address.

Provider documentation: https://developers.google.com/maps/documentation/geocoding/guides-v3/requests-geocoding

Where it sits in the decision

A provider call is a node, not a side effect.

The call runs where the policy needs it — after the cheap checks that might make it unnecessary, before the rules that depend on it. Calls that do not depend on each other run together rather than in sequence.

Because it is part of the run, the response is part of the record. When someone asks why an applicant was declined months later, what Google Maps returned at the time is in the trace, not re-fetched from a service whose answer has since changed.

  • 01Add Google Maps as a connection, with your credentials.
  • 02Place a Connection node and choose the operation.
  • 03Read the response in the rules, tables and branches that follow.
  • 04Test the whole path in Sandbox before it carries live traffic.

Ready when you are

Wire Google Maps into a real decision.

Build the flow in Sandbox, connect your account, and watch the decision pull what it needs before it answers.

Read the docs