Turn geofence alerts into recognizable locations
An alert's coordinates say where, but not always which place. Resolve each point to a Placekey so follow-up starts with a clearer location reference.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
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.
Why this helps
Raw coordinates in alerts are hard to recognize quickly and may slow the next decision.
- Make alert locations easier to discuss and compare.
- Reduce time spent interpreting coordinate pairs.
- Create a consistent reference for location-based follow-up.
Setup
Build it in a few focused steps.
- 1Connect Keen io and Placekey to Notis once through the portal.
- 2Create a webhook automation or ask Notis to identify geofence alert locations conversationally.
- 3Write one prompt asking Placekey for the where identifier for each coordinate pair in an incoming alert.
- 4Choose the incoming webhook trigger and run-report channel, then test with one real alert coordinate pair.
Questions about this workflow
Which data does this use?
It uses the latitude and longitude included in the alert request.
What part of Placekey is returned?
The coordinates action returns the where part of the Placekey, representing the physical location.
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.