Eventeny Vendor & Market Directory ScraperInstall

Summary

Scrapes Eventeny directories and detail pages for event, application, and organizer records by running the Apify actor. Provide one or more supported Eventeny start URLs, then use the optional filters and detail settings to shape the crawl.

Inputs

• Start URLs (required) — One or more Eventeny directory, application hub, event, application, ticket, or organizer URLs. A directory URL may include its own search or q query.
• Maximum items — Maximum number of event, application, and organizer records to collect; defaults to 200.
• Scrape detail pages — When enabled, opens discovered events and applications to collect details such as booth fees, deadlines, terms, files, questions, venue details, and organizer data. Direct detail URLs are always fully scraped.
• Search keywords — Keyword filter for directory URLs that do not already have a search or q query; defaults to craft fair.
• Application type — Selects the application hub feed: artists, exhibitors and vendors (vendor, default), volunteers, or ticketed events (ticket).
• Event category — Filters event directory URLs by category, such as festivals, art, food, markets, or fairs. Empty means all categories.
• Month — Restricts directory results to a month in YYYY-MM format; defaults to 2026-10.
• Location filter — Eventeny location key for the application hub, such as United States-Georgia or Canada; defaults to United States-Georgia.
• Include ticket tiers — For detailed events that sell tickets, includes published tier prices, taxes, processing fees, refund policies, and sale status; defaults to false.
• Include organizer profiles — Adds a separate record for each distinct event host, including public profile details and hosted events; defaults to false.
• Maximum concurrency — Sets parallel requests, from 1 to 30; defaults to 10.
• Debug mode — Saves bounded HTML and JSON diagnostics for failed requests in Apify's default key-value store; defaults to false.
• Authentication (required) — Choose an Apify API key connection or OAuth2 connection.

Output shape

A list of n8n items, generally one per Apify dataset record.

Each item contains a dataset record, with run status data merged into its JSON for regular node execution. When used as an AI tool, items contain dataset records without the run status fields. If Continue On Fail is enabled, a failed input item produces an item with an error field.

Examples

Example 1: Find vendor opportunities and their booth fees

Use an Eventeny directory or application hub URL, leave Application type as Artists, exhibitors & vendors, enable Scrape detail pages, and set a suitable Maximum items cap.

Example 2: Collect ticket prices for selected events

Start from event directory URLs, enable Scrape detail pages and Include ticket tiers, and set the category, month, or keyword filters as needed.

Links

• n8n community nodes installation guide