Understand where each service request is located
A location lookup can slow down an otherwise simple service request. Let Notis request geocode details when the address is submitted.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Get Geocode From Address
This tool retrieves geocode information (latitude and longitude) for a given address using the placekey api. it accepts address components (street address, city, region, postal code, iso country code) and returns geocode data including the unique placekey identifier and location details.
Why this helps
Service intake gets fragmented when someone must leave the request to find its coordinates.
- Retrieve coordinates while the request is being handled.
- Reduce context switching during service intake.
- Make location details available for downstream planning.
Setup
Build it in a few focused steps.
- 1Connect Keen io and Placekey to Notis once through the portal.
- 2Create an incoming webhook automation or ask Notis to geocode new service request addresses.
- 3Describe the outcome in one plain-language prompt: request geocode details for each submitted service address.
- 4Choose the webhook trigger and run-report channel, then test with one real service address.
Questions about this workflow
What location information is returned?
Placekey provides geocode information such as latitude and longitude and other location details.
Can I use this for a custom service request form?
Yes, when the form's backend sends the address in an HTTP request to the Notis webhook.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Keen io to Placekey. A trigger fires from one place; an action lands in another.
Keen io triggers
Placekey actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Geocode From Address
This tool retrieves geocode information (latitude and longitude) for a given address using the placekey api. it accepts address components (street address, city, region, postal code, iso country code) and returns geocode data including the unique placekey identifier and location details.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get placekey from address
Convert a physical address into a unique placekey identifier. the placekey is a universal standard identifier for any physical place that helps in location matching, enrichment, and deduplication.
Get placekey from coordinates
Get a placekey (unique identifier) for a given pair of latitude and longitude coordinates. this is the most basic and independent operation in placekey's api that requires minimal input parameters. the tool returns a "where" part of the placekey, which represents the physical location.
Connect any two apps with Notis in the middle.
Keen io and Placekey, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Placekey.