What does the Nashua NH 311 data include?

2 tables: service requests (one row per service request) and service types (one row per service type).

Do I need an account with Nashua NH 311?

No. The data is public, so there is nothing to sign up for and nothing to paste in.

How fresh is the data?

As fresh as your schedule: daily by default, or weekly or monthly. Schedules as often as every 15 minutes are on the Enterprise plan.

Will running it again create duplicate rows?

No. Each row is stored once, by its key: when a run reads a row that is already there, it replaces that copy instead of adding a second one.

Do I need to write code?

No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

Nashua NH 311

Public data

Ready to useNo account needed

Public requests from Nashua, New Hampshire and service types the city accepts. Ingest delivers this data to a data warehouse you own as 2 tables, and updates it on the schedule you choose. There is no code to write and nothing to install.

What people use it for

Track request activityMonitor how requests are created and updated to see trends emerge.
See location patternsPlot requests to find which areas report problems most often.

What you get

Table	Each row is
Service requests `service_requests`	One service request
Service types `services`	One service type

Good to know

Service requests: Each run re-reads everything and updates rows that changed. Rows the source removes stay in your table.
Service types: Each run re-reads everything and updates rows that changed. Rows the source removes stay in your table.

How it works

Choose Nashua NH 311. The data is public, so there is nothing to sign in to.
Pick where it goes. BigQuery, Snowflake, Databricks, Redshift and 10 more, in an account you own.
Pick a schedule. Daily is the default, and weekly and monthly are there too.
Ingest runs it from then on. If a run fails, your dashboard shows which table and why.

Questions

What does the Nashua NH 311 data include?: 2 tables: service requests (one row per service request) and service types (one row per service type).
Do I need an account with Nashua NH 311?: No. The data is public, so there is nothing to sign up for and nothing to paste in.
Which warehouses can Nashua NH 311 data go to?: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
How fresh is the data?: As fresh as your schedule: daily by default, or weekly or monthly. Schedules as often as every 15 minutes are on the Enterprise plan.
Will running it again create duplicate rows?: No. Each row is stored once, by its key: when a run reads a row that is already there, it replaces that copy instead of adding a second one.
Do I need to write code?: No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

For your data team: technical reference

Connector nashua_311, version 0.1.0, a REST source, status beta, authentication none.

Vendor documentation: https://seeclickfix.com/open311/v2/docs

Configuration

No configuration required.

Resources

Resource	Status	Plan	Write	Primary key	Overrides
`service_requests` Re-fetches the full public request collection exposed by Nashua SeeClickFix Open311 on each run, using page-number pagination with 20-row pages and no creation-date horizon. Saved verification on 2026-09-11 found 12 distinct requests, including records from 2022; this is observed provider coverage, not a guarantee of all municipal history. Merge updates previously seen request IDs with returned values. Records deleted or no longer exposed by the source remain in the destination.	beta	full	merge	`service_request_id`	-
`services` Re-fetches the current public service-type catalog exposed by Nashua SeeClickFix Open311 on each run. Merge updates returned service codes; removed codes remain in the destination. This organization-scoped catalog does not define all municipal services and is not used to filter request rows.	beta	full	merge	`service_code`	-