Events Eye Scraper

EventsEye Trade Show Scraper & MCP Connector

Pull trade shows and exhibitions from EventsEye.com — filtered by industry, region, country, or a specific city — together with full organizer, venue, and event details. No manual browsing, no copy-pasting listing pages, no clicking through hundreds of exhibition profiles.

Built for B2B sales teams, event organizers, market researchers, and anyone who needs a structured directory of global trade shows — in minutes, not days of scrolling.

Pick an industry, region, country, or city → get every matching trade show + organizer/venue details → deliver it straight into Notion, Slack, Jira, or your CRM.

---

⭐ Why This Actor?

• ✅ Filter any way you like — narrow by Industry, Region, Country, and City independently, or combine them. Leave any filter blank to include everything under it.
• ✅ Direct City Mode — specify a city (with country) and skip the industry filter entirely to pull every exhibition in that city across all industries in one pass.
• ✅ Full hierarchical crawl — when no city is given, the Actor walks EventsEye's own structure (Industry → Region → Country → City) so nothing in your filter is missed.
• ✅ Optional deep details — turn on detailed scraping to pull organizer name, address, phone, website, and email, plus venue address and related industries, straight from each exhibition's page.
• ✅ Never overshoots your quota — max_exhibitions caps the run cleanly across every branch of the crawl, so you always get a predictable dataset size.
• ✅ Deliver anywhere via MCP connectors — push scraped trade shows straight into Notion, Slack, Jira, GitHub, Airtable, and more.
• ✅ Export-ready — JSON, CSV, Excel, or direct API integration for your own pipeline.

---

📝 Use Cases & ROI

Use Case	Time Saved	What You Get
Trade show directory building	3–6 hrs/region	A structured list of every exhibition in an industry, region, or country
B2B outreach & lead sourcing	4–8 hrs/campaign	Organizer names, emails, phone numbers, and websites ready to contact
Market & competitor research	2–5 hrs/industry	Where and when competitors exhibit, and who organizes those events
Event calendar monitoring	1–3 hrs/city	Every upcoming trade show in a city, refreshed on demand
CRM / dashboard enrichment	2–4 hrs/batch	Clean structured records ready to import or push via a connector

---

🚀 How to Use

1. Open the Actor on Apify.
2. (Optional) Select an Industry, Region, and/or Country — leave any of them blank to include all.
3. (Optional) Type a specific City — combine with Country and leave Industry blank to trigger Direct City Mode, which pulls every exhibition in that city regardless of industry.
4. (Optional) Enable Scrape Exhibition Details to also fetch organizer and venue contact info (slower, one extra request per exhibition).
5. Set Maximum Exhibitions — 0 for unlimited, or a number to cap the run.
6. (Optional) Pick an MCP connector to deliver each trade show into Notion, Slack, Jira, etc.
7. Click Run — results stream into the dataset as each exhibition is scraped.
8. Download as CSV, Excel, or JSON — or let the connector push results into your tools automatically.

💡 First time with a connector? Run once with a connector selected — the run log prints the connector's available tool names and their exact input schema, so you know what to put in Connector tool name and Connector tool arguments.

---

🧩 Input Configuration

Field	Type	Required	Description
industry	String (select)	Optional	Filter to one industry from EventsEye's category list. Leave blank for all industries.
region	String (select)	Optional	Filter to one region (Africa - Middle East, America, Asia - Pacific, Europe). Leave blank for all regions.
country	String (select)	Optional	Filter to one country. Leave blank for all countries.
city	String	Optional	Type a specific city (e.g. Mumbai, Berlin). Combine with country and leave industry blank for Direct City Mode.
scrape_details	Boolean	Optional	Fetch organizer, venue address, and contact details from each exhibition's page. Default: false. Disable for faster runs.
max_exhibitions	Integer	Optional	Maximum exhibitions to scrape (0–100 in the Apify Console; set higher via API for larger runs). 0 = unlimited. Default: 50.
test_mode	Boolean	Optional	Quick-test flag intended to limit the crawl to the first region/country/city. Default: true.
mcpConnector	Connector	Optional	Deliver scraped exhibitions into a connector you've authorized (Notion, Slack, Jira, GitHub, Airtable, …).
deliveryMode	Enum	Optional	summary (one call listing all scraped exhibitions), chunked (split a long list across a few calls so services like Notion never time out), perEvent (one call per exhibition), or none. Default: summary.
mcpTool	String	Optional	Tool to call on the connector (e.g. create_page for Notion, send_message for Slack, create_issue for Jira/GitHub).
mcpArguments	Object	Optional	Arguments passed to the connector tool; string values support {placeholders}.
mcpMessageTemplate	String	Optional	Template rendered and exposed as the {message} placeholder in the tool arguments.

Example — Filter by industry, region, country, and city

{
    "industry": "Automobile - Automotive Industry",
    "region": "Asia - Pacific",
    "country": "India",
    "city": "Ahmedabad",
    "scrape_details": false,
    "max_exhibitions": 5,
    "test_mode": false
}

Example — Direct City Mode with full organizer/venue details

{
    "country": "Germany",
    "city": "Berlin",
    "scrape_details": true,
    "max_exhibitions": 0
}

Example — Scrape and post each trade show to Slack

{
    "country": "Germany",
    "city": "Berlin",
    "max_exhibitions": 25,
    "mcpConnector": "<your-slack-connector>",
    "deliveryMode": "perEvent",
    "mcpTool": "send_message",
    "mcpArguments": { "channel": "#trade-shows", "text": "{message}" },
    "mcpMessageTemplate": "*{exhibition_name}*\n{venue_name}, {city} — {date}\n{exhibition_url}"
}

Example — Scrape and create one Notion page summarizing a city (chunked for large result sets)

{
    "country": "India",
    "city": "Mumbai",
    "max_exhibitions": 0,
    "mcpConnector": "<your-notion-connector>",
    "deliveryMode": "chunked",
    "mcpTool": "create_page",
    "mcpArguments": {
        "parent": { "page_id": "<your-page-id>" },
        "pages": [
            {
                "properties": { "title": "Trade shows — {city} (part {part}/{partCount})" },
                "content": "Found {totalEvents} events in {city}:\n\n{events}"
            }
        ]
    }
}

Placeholders available in mcpArguments / mcpMessageTemplate

summary and chunked modes: {totalEvents} · {city} · {country} · {region} · {industry} · {events} (all exhibitions as text lines) · {message} chunked mode adds: {part} · {partCount} perEvent mode: {exhibition_name} · {description} · {venue_name} · {city} · {country} · {date} · {duration} · {exhibition_url} · {industry} · {category} · {message} — plus any detail field returned when scrape_details is on (organizer, organizer_website, organizer_email, event_website, …)

---

📦 Output Data

Every record always carries exhibition_name, city, date, and exhibition_url. The fields below are added depending on the scrape mode and whether scrape_details is enabled.

Field	Description
exhibition_name	Trade show / exhibition name
description	Short description shown alongside the listing
cycle_frequency	How often the show recurs (e.g. annual, biennial)
date / duration	Event dates and how long it runs
venue_name / venue_url	Venue name and its EventsEye profile link
city / country / region	Location of the exhibition
industry / category	Industry classification
exhibition_url	Link to the exhibition's EventsEye page
organizer	Organizer name (requires scrape_details)
organizer_address / organizer_phone / organizer_fax	Organizer contact details (requires scrape_details)
organizer_website / organizer_email	Organizer website and email (requires scrape_details)
event_website / event_email	Event-specific website and email (requires scrape_details)
venue_address	Full venue address (requires scrape_details)
related_industries	Other industries associated with the show (requires scrape_details)
audience	Target audience description (requires scrape_details)

Example Output

[
    {
        "exhibition_name": "AutoExpo Berlin",
        "description": "International automotive components fair",
        "cycle_frequency": "Annual",
        "venue_name": "Messe Berlin",
        "city": "Berlin",
        "date": "12 - 15 March 2027",
        "duration": "4 days",
        "exhibition_url": "https://www.eventseye.com/fairs/f-autoexpo-berlin-12345.html",
        "venue_url": "https://www.eventseye.com/fairs/v-messe-berlin-6789.html",
        "industry": "Automobile - Automotive Industry",
        "category": "Industrial Fairs",
        "region": "Europe",
        "country": "Germany"
    }
]

You can download the dataset in various formats such as JSON, HTML, CSV, or Excel. Note: organizer/venue detail fields are only present when scrape_details is enabled, and may come back missing if an exhibition's page doesn't publish them.

---

🔌 Integrations & Delivery

Deliver scraped trade shows into any MCP connector you've authorized in Apify — no glue code, no webhooks:

• Notion — create a page per city, industry batch, or exhibition (use chunked mode for large result sets so Notion never times out)
• Slack / Discord — post new trade shows or a daily summary to a channel
• Jira / GitHub / Linear — open a task per exhibition for outreach follow-up
• Airtable / Google Sheets — append a structured row per trade show
• …or any other MCP-compatible connector

Credentials stay private — delivery runs through the Apify MCP Proxy, so the Actor never sees your connector tokens. You can also consume the dataset directly via the Apify API, or wire it into n8n, Zapier, and Make.

⚙️ Delivery modes: summary sends the whole result set in one call, chunked splits a long list across a few calls/pages, and perEvent sends one call per exhibition. MCP delivery only runs on the Apify platform and never affects what's saved to the dataset — if delivery fails for any reason, your scraped data is already safely stored.

---

🛠️ How It Works

src/main.py reads the input and runs HierarchicalTradeShowScraper, which:

1. If a city and country are given without an industry, jumps straight to that city's page (Direct City Mode) and pulls every exhibition listed there, across all industries.
2. Otherwise, walks EventsEye's own hierarchy — Industry → Region → Country → City — using httpx + BeautifulSoup to parse each listing page, respecting any of the four filters you've set and paginating through long result tables.
3. For each exhibition row, parses name, description, cycle, venue, city, dates, and the exhibition URL, then merges in the industry/region/country context from that branch of the crawl.
4. If Scrape Exhibition Details is on, visits each exhibition's own page to pull organizer contact info, venue address, related industries, and audience.
5. Pushes each exhibition to the dataset as soon as it's parsed, respecting max_exhibitions across every branch of the crawl.
6. Once scraping finishes, if a connector is configured, delivers the collected exhibitions via MCP (summary, chunked, or perEvent) — this step never discards or blocks the dataset that was already saved.

Built with: Apify SDK for Python · BeautifulSoup4 · httpx · MCP

---

🆘 Support

For issues, custom scraping requests, or feature suggestions: Email: bhavin.shah@techforceglobal.com

💡 Want to scrape multiple event platforms at once with advanced filters? Check out the Smart Event Scraper — it combines AllEvents, EventsEye, District, EventBrite, Meetup, and Conference Alerts into a single actor.

---

Need a Custom Pipeline?

Want multi-region batch runs, scheduled refreshes, deeper enrichment, or a full data-warehouse integration?

📅 Book a Free 15-min Consultation

---

Made with ❤️ by Techforce Specialists in High-Performance Web Scrapers and AI Automation.

---

Disclaimer

This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by EventsEye.com or its operators. All trademarks are property of their respective owners. The Actor collects only publicly available trade show listings and exhibition details, and does not log into, or scrape behind the authentication of, any platform. Use the data responsibly and in compliance with applicable laws (including GDPR/CCPA) and the terms of the platforms you operate on.