# US Chamber of Commerce Events Scraper (`moving_beacon-owner1/us-chamber-of-commerce-events-scraper`) Actor

Extract business networking events, chamber meetings, workshops, conferences, and other publicly listed events from selected US Chamber of Commerce calendars.

- **URL**: https://apify.com/moving_beacon-owner1/us-chamber-of-commerce-events-scraper.md
- **Developed by:** [Jamshaid Arif](https://apify.com/moving_beacon-owner1) (community)
- **Categories:** Developer tools, Automation, Lead generation
- **Features:** Limited permissions
- **Stats:** 6 total users, 2 monthly users, 14.7% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $9.99 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## 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.

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:

- `Worthington`
- `Dublin`
- `Tri-Village`
- `Hilliard`

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**

```json
{
  "startUrls": [
    "https://example.com/events"
  ]
}
```

**Custom parser format**

```json
{
  "startUrls": [
    {
      "url": "https://example.com/events",
      "label": "Example Chamber",
      "parser": "gz-title"
    }
  ]
}
```

Supported parser types:

- `gz-body`
- `gz-title`
- `mn-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

```json
{
  "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.

# Actor input Schema

## `sites` (type: `array`):

Select one or more chamber calendars. Leave empty to scrape all configured sites.

## `startUrls` (type: `array`):

Optional additional public event-calendar URLs.

## `maxItems` (type: `integer`):

Maximum number of event records to save. Set to 0 for no limit.

## `requestDelaySecs` (type: `number`):

Delay between requests in seconds.

## `requestTimeoutSecs` (type: `integer`):

HTTP request timeout in seconds.

## Actor input object example

```json
{
  "sites": [
    "Worthington",
    "Dublin",
    "Tri-Village",
    "Hilliard"
  ],
  "startUrls": [],
  "maxItems": 0,
  "requestDelaySecs": 1,
  "requestTimeoutSecs": 30
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("moving_beacon-owner1/us-chamber-of-commerce-events-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("moving_beacon-owner1/us-chamber-of-commerce-events-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call moving_beacon-owner1/us-chamber-of-commerce-events-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,moving_beacon-owner1/us-chamber-of-commerce-events-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/QI6aaiwz5IBcjVuEL/builds/aZk1pJU7PGM4JC5ch/openapi.json
