Skip to the operations

Address verification

Google Maps in a decision flow.

2 Google Maps operations a decision flow can call directly, with the credentials your own contract issued. The response is data the rest of the flow reads, branches on, and keeps in the 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

Address verification calls have a natural place in a flow.

An address is an input other systems will trust, so it is worth resolving to a canonical form before it becomes a field in a credit file or a KYC record. The call is cheap and belongs early, where correcting the input is still free.

Whatever Google Maps returns is part of the run, so it is part of the record. When someone asks months later why an applicant was declined, the answer cites what came back at the time rather than re-fetching from a service whose answer has since changed.

  • 01Add Google Maps as a connection authenticating with an API key.
  • 02Google Maps has one host for both environments, so guard test runs with your own credentials and limits.
  • 03Place a Connection node and pick an operation — “Validate and geocode an address” is usually the first one a flow needs.
  • 04Map the response into the fields your rules read, then test the whole path before it carries live traffic.

Common questions

Using Google Maps in a flow.

How do I connect Google Maps to a decision flow?

Add Google Maps as a connection in your workspace authenticating with an API key, with the credentials your own contract issued — ArboRule calls the provider as you, and never holds a contract on your behalf. Once the connection exists, any flow in the workspace can place a Connection node and choose one of its operations. The credentials live on the connection, not in the flow, so a policy owner can use Google Maps in a decision without ever seeing the secret.

Can I test Google Maps without touching production?

Google Maps exposes one host for both environments, so there is no separate sandbox to point at. Test runs still execute in Sandbox and are recorded separately in decision history, but the call goes to the same place as production — so guard it with your own test credentials, rate limits, or data.

What can a flow call on Google Maps?

2 operations: “Validate and geocode an address”, “Validate coordinates against an address”. Each one is a step you place on the canvas and map into the fields your rules read, and most flows start with “Validate and geocode an address”. The list comes from the same manifest the engine uses to make the call, so this page cannot describe an operation the product does not have.

Where in a decision should Google Maps be called?

An address is an input other systems will trust, so it is worth resolving to a canonical form before it becomes a field in a credit file or a KYC record. The call is cheap and belongs early, where correcting the input is still free.

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