Skip to content

Integrations

Fits into the tools your
city already uses.

Connect mapping, messaging, identity and data systems in minutes — or build on the same API our own apps use.

Integrations

Showing 12 integrations

  • Native

    GIS

    Data

    Two-way sync with your city’s geographic information system.

    What it syncs

    • District and ward boundaries
    • Asset layers (lights, bins, mains)
    • Incident points, back to your maps
  • Native

    Slack

    Messaging

    Route alerts and approvals to department channels.

    What it syncs

    • New urgent incidents per channel
    • Approve AI suggestions inline
    • Daily summaries
  • Available

    Microsoft Teams

    Messaging

    Post updates, escalations and approvals to Teams.

    What it syncs

    • Escalations to on-call teams
    • Adaptive-card approvals
    • Status changes in threads
  • Native

    Email intake

    Messaging

    Turn inbound emails into structured reports.

    What it syncs

    • Sender, subject and body
    • Photos and attachments
    • Replies back to the resident
  • Available

    SMS updates

    Messaging

    Keep residents informed without an app.

    What it syncs

    • Acknowledgement on receipt
    • Status changes
    • Resolution with a link to the photo
  • Available

    Open data

    Data

    Publish anonymized datasets on a schedule.

    What it syncs

    • Incidents without personal data
    • Resolution times by district
    • CSV, GeoJSON and JSON feeds
  • Beta

    Asset management

    Data

    Link incidents to the assets in your maintenance system.

    What it syncs

    • Asset registry and IDs
    • Work orders both ways
    • Maintenance history
  • Available

    311 & CRM

    Data

    Bring existing service-request systems onto one record.

    What it syncs

    • Cases and case numbers
    • Resident contact preferences
    • Status back to the CRM
  • Available

    SSO

    Identity

    SAML 2.0 and OpenID Connect with your identity provider.

    What it syncs

    • Sign-in for every staff seat
    • Groups mapped to roles
    • Session and MFA policies
  • Beta

    SCIM provisioning

    Identity

    Create and remove staff accounts automatically.

    What it syncs

    • Users and departments
    • Deprovisioning on exit
    • Role changes
  • Native

    REST API

    Developer

    Read and write every object over a documented REST API.

    What it syncs

    • Incidents, teams and assets
    • Analytics and SLA metrics
    • Scoped API keys per system
  • Native

    Webhooks

    Developer

    Signed events for every status change.

    What it syncs

    • Created, assigned, resolved events
    • HMAC signatures and retries
    • Per-event subscriptions

For developers

Build on the same API our apps use.

Everything in CivicFlow is available over REST, with signed webhooks for every change. Versioned, documented and covered by the uptime SLA.

  • OpenAPI 3.1 specification
  • Scoped API keys and audit logs
  • Sandbox workspace with sample data
GET /v2/incidents
# List open incidents in the north districtcurl "https://api.civicflow.site/v2/incidents?status=open&district=north" \  -H "Authorization: Bearer $CIVICFLOW_KEY"# 200 OK{  "data": [    {      "id": "CF-4821",      "title": "Streetlight outage",      "category": "lighting",      "status": "urgent",      "priority": "high",      "location": "Linden St & 4th Ave",      "assigned_team": "elec-4",      "sla_due_at": "2026-10-08T21:12:00Z"    }  ],  "has_more": true}

REST & GraphQL · OpenAPI 3.1 · 99.99% uptime SLA

Connect CivicFlow to your stack.

Show us the systems you run today — we will map out the integrations in your demo.