Integrations

Powoflow connects to over 50 external data sources, notification channels, and enterprise systems. Integrations bring external data into your asset operations platform — from real-time vehicle tracking to global hazard monitoring — and push events out to Slack, PagerDuty, and ERP systems.

---

Integration Types

Powoflow supports five integration patterns, each suited to different data flows.

Type	Direction	Trigger	Example
Webhook	Inbound	Real-time push	Garmin inReach sends a location fix
Poll	Inbound	Scheduled interval	NWT Climate station data fetched via FTP
Geo-Data Feed	Inbound	Scheduled interval	USGS earthquake feed polled every 5 minutes
Notification Channel	Outbound	Event-driven	Alarm triggers a PagerDuty incident
ERP/CMMS Connector	Bidirectional	Sync schedule	Work order synced to JD Edwards

---

Webhook Integrations

Webhook integrations receive real-time data pushed from external systems to Powoflow.

Garmin inReach (Vehicle Tracking)

Garmin inReach satellite communicators can push location updates to Powoflow in real-time. This is commonly used for vehicle and personnel tracking in remote areas without cellular coverage.

• Endpoint: POST /integrations/garmin-inreach/webhook
• Data: GPS coordinates, altitude, speed, heading, SOS status
• Processing: Location updates are mapped to the corresponding vehicle or asset resource

info

Garmin inReach webhooks must be configured in your Garmin Explore account. Point the MapShare webhook URL to your Powoflow integration endpoint.

---

Poll Integrations

Poll integrations fetch data from external systems on a configurable schedule.

NWT Climate (Alpine Weather Stations)

Pulls environmental data from Northwest Territories Climate monitoring stations via FTP.

• Protocol: FTP file download
• Data: Temperature, humidity, wind speed/direction, precipitation, barometric pressure
• Schedule: Configurable polling interval
• Mapping: Station data is mapped to site-level weather readings

---

Notification Channels

Powoflow can push events to external notification and incident management systems.

Slack

Rich notifications using Slack's Block Kit format.

• Alarm triggers, work order updates, and integration alerts
• Formatted with color-coded severity, asset links, and action buttons
• Configure per-channel routing (e.g., critical alarms to #alerts, work orders to #maintenance)

PagerDuty

Bidirectional integration using the Events API v2.

• Outbound: Powoflow alarms create PagerDuty incidents with severity mapping
• Inbound: PagerDuty acknowledgments and resolutions sync back to Powoflow
• Supports deduplication keys to prevent duplicate incidents

Microsoft Teams

Adaptive Card notifications posted to Teams channels.

• Formatted cards with severity indicators, asset context, and deep links
• Configure per-channel routing

Channel	Format	Direction	Key Feature
Slack	Block Kit	Outbound	Action buttons
PagerDuty	Events API v2	Bidirectional	Auto-resolve sync
MS Teams	Adaptive Cards	Outbound	Deep links

---

ERP/CMMS Connectors

Bidirectional sync with enterprise resource planning and maintenance management systems.

Supported Systems

System	Sync Scope	Direction
JD Edwards	Work orders, parts, equipment registry	Bidirectional
Maximo	Work orders, assets, failure codes	Bidirectional
Oracle	Work orders, inventory, cost centers	Bidirectional

Each connector provides:

• External ID mapping — links Powoflow resources to ERP records for bidirectional tracking
• Conflict resolution — configurable rules for handling simultaneous edits
• Idempotent sync — safe to retry without creating duplicates
• Sync history — full audit trail of every synced record

warning

ERP connectors require configuration by your Powoflow administrator. Contact support for setup assistance with JD Edwards, Maximo, or Oracle integrations.

---

Geo-Data Feeds

Powoflow aggregates data from 41 global hazard and environmental data sources, displayed as map overlays and used to generate proximity alerts when hazards threaten your assets.

Seismic (5 sources)

Source	Coverage	Data
USGS Earthquakes	Global	Magnitude, depth, location, tsunami flag
NRCAN	Canada	Canadian seismic network events
EMSC	Europe	European-Mediterranean seismic events
GeoNet NZ	New Zealand	NZ seismic network events
Smithsonian GVP	Global	Volcanic seismicity and eruption reports

Weather Alerts (5 sources)

Source	Coverage	Data
NWS	United States	Watches, warnings, advisories with polygons
MET Norway	Norway, Arctic	Weather warnings and forecasts
MeteoAlarm	European Union	Multi-country severe weather alerts
SPC Outlooks	United States	Severe weather probability outlooks
NHC Tropical Cyclones	Atlantic, Pacific	Hurricane/typhoon tracks, cones, watches

Volcanic (3 sources)

Source	Coverage	Data
USGS Volcanoes	United States	Alert levels, aviation color codes
GeoNet Volcano	New Zealand	Volcanic alert bulletins
Smithsonian GVP	Global	Eruption reports, activity updates

Fire (3 sources)

Source	Coverage	Data
NASA FIRMS	Global	Active fire detections (MODIS/VIIRS satellite)
NIFC Fire Perimeters	United States	Wildfire boundaries and containment
VIIRS Gas Flares	Global	Industrial gas flare detections

Water (3 sources)

Source	Coverage	Data
NVE Flood	Norway	River flood warnings and levels
NVE Avalanche	Norway	Avalanche danger assessments
UK EA Flood	United Kingdom	Flood warnings and river levels

Air Quality (2 sources)

Source	Coverage	Data
OpenAQ	Global	PM2.5, PM10, O3, NO2, SO2, CO measurements
AQICN / WAQI	Global	Air Quality Index readings by station

Drought (1 source)

Source	Coverage	Data
US Drought Monitor	United States	Drought severity classifications (D0-D4)

Conflict (1 source)

Source	Coverage	Data
ACLED	Global	Armed conflict events, protests, violence

Maritime (2 sources)

Source	Coverage	Data
Global Fishing Watch	Global	Vessel tracking and fishing activity
NGA MODU	Global	Mobile Offshore Drilling Unit positions

Radiation (1 source)

Source	Coverage	Data
Safecast	Global	Crowd-sourced radiation measurements

Lightning (1 source)

Source	Coverage	Data
Blitzortung	Global	Real-time lightning strike locations

UV Index (2 sources)

Source	Coverage	Data
OpenUV	Global	Current and forecasted UV index
NOAA UV Forecast	United States	UV index forecasts by location

Aviation (1 source)

Source	Coverage	Data
FAA Airport Status	United States	Airport delays, closures, ground stops

Energy (1 source)

Source	Coverage	Data
UK Carbon Intensity	United Kingdom	Grid carbon intensity and generation mix

Border (1 source)

Source	Coverage	Data
CBP Border Wait Times	US-Mexico, US-Canada	Port of entry wait times by lane type

Travel Advisories (2 sources)

Source	Coverage	Data
US State Department	Global	Country-level travel advisories (1-4)
UK FCDO	Global	Foreign travel advice and alerts

Risk Indices (2 sources)

Source	Coverage	Data
INFORM Risk	Global	Country-level multi-hazard risk scores
INFORM Severity	Global	Crisis severity index for active emergencies

Infrastructure (1 source)

Source	Coverage	Data
PHMSA Pipeline	United States	Pipeline incident reports and locations

Space Weather (2 sources)

Source	Coverage	Data
NOAA SWPC	Global	Geomagnetic storms, solar flares, radio blackouts
CelesTrak Satellites	Global	Satellite conjunction and reentry alerts

Disaster (1 source)

Source	Coverage	Data
GDACS	Global	Multi-hazard disaster alerts and impact estimates

Tsunami (1 source)

Source	Coverage	Data
NOAA Tsunami Alerts	Pacific, Atlantic, Indian	Tsunami watches, warnings, and advisories

---

Geo-Alert Proximity Engine

The Geo-Alert engine automatically detects when hazards from any of the 41 geo-data feeds occur near your assets and sends proximity alerts.

How It Works

1. Geo-data feeds are polled on schedule (typically every 5-15 minutes)
2. New hazard events are compared against the locations of all your assets
3. If a hazard falls within the configured proximity threshold, an alert is generated
4. Alerts are delivered via your configured notification channels

Alertable Categories & Default Thresholds

Powoflow supports 17 alertable categories with configurable proximity thresholds:

Category	Default Threshold	Trigger Example
Seismic (M5+)	200 km	M5.2 earthquake 150 km from your facility
Seismic (M7+)	500 km	M7.1 earthquake anywhere within 500 km
Fire	25 km	Active wildfire detected 15 km from site
Weather	Polygon intersection	Tornado warning polygon overlaps your location
Volcanic	100 km	Eruption alert at volcano near your operations
Flood	50 km	Flood warning for river near your assets
Tsunami	Coastal zone	Tsunami warning for coastline near your port
Tropical Cyclone	Forecast cone	Hurricane track cone passes within range
Air Quality	50 km	AQI exceeds hazardous threshold nearby
Lightning	25 km	Lightning cluster detected near outdoor operations
Conflict	50 km	Armed conflict event reported near your site
Radiation	100 km	Elevated radiation readings detected
Avalanche	25 km	Avalanche danger rating elevated in your area
Drought	County/region	Extreme drought declared in your operating area
Space Weather	Global	G3+ geomagnetic storm (affects satellite comms)
Travel Advisory	Country	Travel advisory level raised for operating country
Disaster	200 km	GDACS alert for multi-hazard event nearby

info

Thresholds are fully configurable per tenant. You can increase or decrease the radius, or disable categories entirely.

Geographic Filters

Control which geo-data events are relevant to your operations:

Filter Type	Description
Global	Receive all events worldwide
Country	Filter to specific countries
Region	Filter to specific regions or states
Bounding Box	Define a geographic rectangle on the map
Asset Proximity	Only alert when events are near your actual asset locations

Per-Tenant Subscription Management

Each tenant can independently:

• Enable or disable individual geo-data sources
• Set custom proximity thresholds per category
• Configure geographic filters per source
• Route alerts to specific notification channels

Deduplication

The proximity engine applies a 4-hour deduplication window to prevent alert fatigue. If the same hazard event would trigger multiple alerts for the same asset within 4 hours, only the first alert is sent.

Notification Delivery

Proximity alerts are delivered through multiple channels simultaneously:

Channel	Description
Activity Feed	Appears in the Powoflow activity feed in real-time
Push Notification	Mobile push notification to relevant users
Slack	Posted to configured Slack channel
PagerDuty	Creates PagerDuty incident (for critical categories)
MS Teams	Posted to configured Teams channel

---

Configuration

Connecting a Vendor

1. Navigate to Settings > Integrations
2. Browse the vendor catalog or search by name
3. Click Connect on the desired integration
4. Enter any required credentials or configuration (API keys, webhook URLs, etc.)
5. Click Save — the integration begins syncing

Feed Configuration

Each connected integration has configurable settings:

Setting	Description
Thresholds	Minimum severity or magnitude to ingest (e.g., M4.0+ earthquakes)
Channels	Which notification channels receive alerts from this feed
Geographic Filter	Limit data to specific regions or bounding boxes
Sync Interval	How often to poll for new data (poll integrations only)

Manual Sync

Click Sync Now on any poll or geo-data integration to trigger an immediate data fetch outside the regular schedule.

Sync Status & History

Each integration displays:

• Last Sync — timestamp of the most recent successful sync
• Status — healthy, degraded, or error
• Record Count — number of records ingested in the last sync
• Error Log — details of any failed sync attempts

tip

If an integration shows a degraded or error status, check the error log for details. Common issues include expired API keys, rate limiting, or upstream service outages.

Disconnecting a Vendor

1. Navigate to Settings > Integrations
2. Find the connected vendor
3. Click Disconnect
4. Confirm the disconnection

warning

Disconnecting a vendor stops all data ingestion and alert generation from that source. Historical data already ingested is retained.

Notification Routing

Configure which events from which integrations go to which notification channels:

1. Navigate to Settings > Integrations > Notification Routing
2. Create routing rules: IF [source] AND [severity >= X] THEN [channel]
3. Multiple rules can apply to the same event (e.g., critical earthquakes go to both Slack and PagerDuty)

tip

Start with broad routing rules and refine over time. It's better to receive too many alerts initially and tune down than to miss a critical event.