Nashville 311
Sync Nashville 311 service requests into your warehouse.
The Nashville 311 connector syncs Nashville service requests into analytics-ready tables in your data warehouse. Pull hubNashville service requests with request and subrequest type, origin, opened and closed timestamps and council district from the hubNashville feature service on the Nashville open data portal, with Ingest handling pagination and retries so the tables stay current.
Nashville 311 is not a certified connector yet. Ingest authors one from the vendor's API documentation when a customer asks for it, runs it against the real API, and only then lists it as deployable. Request it and it moves up the queue.
What you can sync
Ingest lands the following Nashville 311 data in your warehouse or lake, each as its own table on the schedule you pick:
- Service requests
- Request status and closure
- Request and subrequest types
- Council district and location
Authentication
None. The Nashville 311 API is public and needs no credential.
Credentials go into a form, never into a chat, and are held in a secret store under your own path. Only the key NAMES ever reach the control database.