US Chamber of Commerce Events Scraper
Pricing
from $9.99 / 1,000 results
US Chamber of Commerce Events Scraper
Extract business networking events, chamber meetings, workshops, conferences, and other publicly listed events from selected US Chamber of Commerce calendars.
Pricing
from $9.99 / 1,000 results
Rating
0.0
(0)
Developer
Jamshaid Arif
Maintained by CommunityActor stats
0
Bookmarked
6
Total users
2
Monthly active users
15 days ago
Last modified
Categories
Features
Share
Extract business networking events, chamber meetings, workshops, conferences, and other publicly listed events from selected US Chamber of Commerce calendars.
This actor collects event names, dates, times, event URLs, and chamber names into a structured Apify dataset. It also supports custom event-calendar URLs using configurable HTML parsers.
Features
- Scrape events from four predefined chamber calendars.
- Add custom chamber event-calendar URLs.
- Extract event names and event links.
- Capture event dates and start/end times when available.
- Automatically remove duplicate events.
- Configure request delays and timeouts.
- Limit the number of saved events.
- Export structured results through Apify.
Supported Chamber Websites
The actor includes four predefined sources:
| Chamber | Website |
|---|---|
| Worthington | business.worthingtonchamber.org |
| Dublin | dublinchamber.org |
| Tri-Village | chamberpartnership.org |
| Hilliard | business.hilliardchamber.org |
You can select individual sources or scrape all four.
Input Configuration
1. Select Chamber Websites
Use sites to choose predefined chamber calendars.
Available values:
WorthingtonDublinTri-VillageHilliard
If this field is empty or omitted, the actor selects all four predefined sources.
2. Custom Calendar URLs
Use startUrls to provide additional event-calendar pages.
Two formats are supported:
Simple URL format
{"startUrls": ["https://example.com/events"]}
Custom parser format
{"startUrls": [{"url": "https://example.com/events","label": "Example Chamber","parser": "gz-title"}]}
Supported parser types:
gz-bodygz-titlemn-listing
If a parser is not specified, gz-title is used.
These parser types rely on specific HTML CSS selectors. Custom websites using different page structures may require code adjustments.
3. Scraping Controls
| Input | Default | Description |
|---|---|---|
maxItems | 0 | Maximum number of event records to save. 0 means unlimited. |
requestDelaySecs | 0 | Delay between source requests, in seconds. |
requestTimeoutSecs | 30 | Maximum request timeout, in seconds. |
Negative values are rejected. The timeout must be greater than zero.
Output Data
Each successfully extracted event contains the following fields:
| Field | Description |
|---|---|
source | Data source identifier |
chamber | Chamber or custom source name |
date | Event date in YYYY-MM-DD format |
time | Event start time, when available |
endTime | Event end time, when available |
event | Event title |
url | Direct event link |
scrapedAt | UTC timestamp when the record was collected |
Example Output
{"source": "chamber-calendar","chamber": "Dublin","date": "2026-11-04","time": "09:00","endTime": "10:30","event": "Business Networking Breakfast","url": "https://www.dublinchamber.org/events/example","scrapedAt": "2026-11-04T08:00:00+00:00"}
Illustrative example only; this is not a verified live result.
Duplicate Removal
The actor generates a SHA-1 fingerprint using:
- Chamber name
- Event date
- Start time
- End time
- Event title
- Event URL
Matching fingerprints are skipped during the same run.
Error Handling
If a source cannot be fetched, the actor:
- Logs a warning.
- Increments the failed-request counter.
- Saves an error record containing the source name, URL, and error message.
- Continues processing the remaining sources.
Error records are included in the dataset and can be identified by the error field.
Run Summary
At the end of the run, the actor saves a SUMMARY key-value store record containing:
| Field | Description |
|---|---|
sourcesRequested | Number of selected sources and custom URLs |
eventsFound | Total event records parsed before deduplication |
eventsSaved | Number of unique event records saved |
duplicateEventsRemoved | Duplicate count based on the parsed records |
failedRequests | Number of failed source requests |
finishedAt | UTC completion timestamp |
Export Results
Results are available in the Apify Dataset.
You can export the dataset in supported formats such as:
- JSON
- CSV
- Excel (XLSX), using Apify's dataset export options
Important Notes
- The actor extracts publicly available information from the configured event-calendar pages.
- Event dates and times depend on the source page's available HTML metadata.
- Events without machine-readable dates may have an empty date field.
- Event descriptions, organizer contact details, email addresses, and phone numbers are not extracted by this version.
- The actor does not currently crawl individual event detail pages.
- The predefined CSS selectors may need maintenance if a chamber changes its website layout.
- Custom URLs must use one of the supported parser structures to return event records.
For questions, custom chamber integrations, or parser improvements, contact the developer through Apify.