GovFlow
govflow.org
- Web
- API
- Self-hosted
What GovFlow is
GovFlow is an open-source request management system for local governments, covering 311 service requests, help desk requests, and public questions and answers. Teams can customize request workflows and use a dashboard to review case volumes and location-based service breakdowns. The API currently accepts new requests through API calls and inbound email. The features page also describes web, SMS, social media, and chatbot channels, but the repository identifies SMS and chatbot intake as planned expansion areas. GovFlow supports the Open311 GeoReport v2 specification for interoperability with existing 311 systems and external apps; the project says this compatibility is in alpha. Its API server is MIT licensed and can be extended with plugins, while custom frontends and dashboards can be built using UI components and design patterns. Some UI components had not yet been open sourced. Deployment requires a database and S3-compatible object storage. Transactional email uses SendGrid and SMS uses Twilio, and provider accounts and credentials are required. The project is listed for API, self-hosted, and web use and directs users to GitHub issues for fixes and enhancements.
Who it suits
GovFlow is intended for local governments, including city CIOs and CDOs, as well as GovTech developers and service providers. It may suit teams seeking a self-hosted request management system they can extend.
Good to know, and what to watch
- Teams can customize request handling workflows.
- Dashboard reports case volume and location-based breakdowns.
- MIT-licensed API server supports plugins.
- Supports Open311 GeoReport v2 interoperability.
- SMS and chatbot intake are planned, not currently supported.
- Deployment requires a database and S3-compatible storage.
- Some UI components had not been open sourced.
- Open311 compatibility is in alpha.
The verdict
GovFlow offers local governments an extensible request management API and self-hosted deployment, with workflow customization and Open311 support. Its current intake limitations, deployment dependencies, and alpha compatibility status merit attention before adoption.
What the maker publishes
- Analytics
- Its dashboard provides case volume and location based service breakdown insights. source
- Analytics
- Its dashboard helps users review case volumes and identify service breakdowns by location. source
- Current request intake
- The repository says the API currently supports new requests through API calls and inbound email, while SMS and chatbot intake are planned expansion areas. source
- Deployment
- The project README describes installing GovFlow from npm, configuring a database and object storage, and running its server locally. source
- Deployment requirements
- The setup instructions require a database and S3 compatible object storage, and describe running GovFlow's default server locally. source
- Development status
- The repository describes the project as being developed by a small team within Zencity and prioritizing features based on early adopter use cases. source
- File storage
- Service request files are stored through an S3 compatible object storage backend, with time limited signed upload and download URLs. source
- File storage
- The project README says files are stored on S3-compatible object storage and describes using time-limited presigned URLs for uploads and downloads. source
- Intended users
- The project describes GovFlow as serving local governments and residents, with 311, public questions and comments, and internal requests among its use cases. source
- License and extensibility
- The maker describes GovFlow as MIT licensed and says its API server can be extended with plugins and custom frontends and dashboards can be built using UI components and design patterns. source
- License and extensibility
- GovFlow is licensed under MIT and supports plugins to extend or change API server behavior. source
- Messaging integrations
- The repository says transactional email uses SendGrid and SMS uses Twilio, with provider accounts and credentials required. source
- Messaging integrations
- The project README says transactional email uses SendGrid and SMS uses Twilio, and that users must configure accounts and credentials with both providers. source
- Open 311
- GovFlow supports the Open311 GeoReport v2 specification for integration with existing 311 systems and interoperability with external apps. source
- Open 311
- GovFlow supports the Open311 GeoReport v2 specification for integration with existing 311 systems and interoperability with external apps. source
- Product
- GovFlow is an open source request management system for local governments, covering 311 requests, help desk requests, and public questions and answers. source
- Project maturity
- The GovFlow website says Open311 GeoReport v2 compatibility is currently in alpha. source
- Purpose
- GovFlow is an open source request management system for local governments that handles 311 requests, help desk requests, and public questions and answers. source
- Request channels
- The features page says constituents can submit requests by email, web, SMS, social media, and chatbots, and receive responses through the same channels. source
- Request channels
- It can receive service requests through email, web, SMS, social media, and chatbots, and respond through the same channels. source
- Support and community
- The maker directs users to GitHub issues for fixes and enhancements and discussions for new functionality. source
- Support and community
- The project invites users to report bugs through GitHub issues and discuss features and architecture in GitHub Discussions. source
- UI availability
- The repository says the API server is open source but some UI components had not yet been open sourced. source
- Who it serves
- The maker describes GovFlow as designed for local governments, including city CIOs and CDOs, and for GovTech developers and service providers. source
Checked against the maker's pages on 9 Oct 2026.