Webinar Lead Prospecting Workflow avatar

Webinar Lead Prospecting Workflow

Pricing

Pay per event

Go to Apify Store
Webinar Lead Prospecting Workflow

Webinar Lead Prospecting Workflow

Find companies running webinars, demos, virtual events, and workshops, then enrich public host/contact signals for B2B prospecting.

Pricing

Pay per event

Rating

0.0

(0)

Developer

Stas Persiianenko

Stas Persiianenko

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

4 days ago

Last modified

Categories

Share

Find companies that are actively running webinars, demos, virtual events, workshops, and online roundtables. This Apify Actor turns search phrases, company domains, and direct event URLs into deduped B2B prospecting rows with event metadata, host company signals, public contact hints, and a lead score.

What does Webinar Lead Prospecting Workflow do?

Webinar Lead Prospecting Workflow is a packaged prospecting workflow for sales and marketing teams.

It discovers public webinar and event landing pages, parses the page content, extracts event and host-company signals, and enriches each row with public contact fields visible on the page.

Use it when you want a list of companies running webinars, not just a raw list of search results.

Who is it for?

  • SDR teams looking for companies investing in webinars or demos.
  • Agencies building outreach lists for B2B campaigns.
  • Sponsorship sellers finding event-active companies.
  • Event-tech vendors monitoring prospects that already use webinar channels.
  • RevOps teams that want repeatable enrichment instead of manual spreadsheet joins.

Why use it?

Manual webinar prospecting usually means searching Google, opening each result, checking if it is a real event, finding the host domain, and copying contact links.

This Actor packages those steps into one repeatable run.

It is especially useful when you need fresh event-led buying signals for outreach.

How the workflow works

  1. Submit search queries, company domains, direct event URLs, or any combination of the three.
  2. The Actor discovers candidate webinar, demo, workshop, event, resource, and learning pages.
  3. It fetches public landing pages with HTTP + Cheerio.
  4. It scores each page for webinar/event confidence.
  5. It extracts event, company, speaker, topic, and contact signals.
  6. It dedupes by host domain when requested.
  7. It saves one normalized lead row per qualified page.

Input options

InputTypeDescription
queriesarraySearch phrases such as cybersecurity webinar or HR software demo.
domainsarrayCompany domains to inspect for common event/resource paths.
eventUrlsarrayDirect webinar, event, demo, workshop, or registration URLs.
maxItemsintegerMaximum qualified lead rows to save.
maxSearchResultsPerQueryintegerMaximum search results inspected per query.
includeContactsbooleanExtract public emails, phones, socials, and contact-page links.
dedupeByDomainbooleanKeep one row per host domain.
countrystringOptional market hint appended to search queries.

Example input

{
"queries": ["cybersecurity webinar", "HR software demo"],
"domains": ["hubspot.com", "semrush.com"],
"eventUrls": [{ "url": "https://www.hubspot.com/webinars" }],
"maxItems": 50,
"maxSearchResultsPerQuery": 20,
"includeContacts": true,
"dedupeByDomain": true,
"country": "United States"
}

Output data

Each dataset item is a deduped webinar/event prospecting lead.

FieldDescription
eventTitleLanding page or event title.
eventUrlPublic event or webinar URL.
sourceDiscovery source, such as search, domain candidate, or direct URL.
sourceQueryQuery that found the page, when applicable.
startDateDate text detected on the page, when available.
isUpcomingWhether the parsed date appears upcoming.
isVirtualWhether the page looks like an online event/webinar.
webinarConfidence0-100 confidence score for webinar/event relevance.
hostCompanyInferred host company.
hostDomainHost domain used for dedupe and routing.
organizerNamePublic organizer hint when available.
speakerNamesPublic speaker/person hints when detected.
speakerTitlesPublic title hints such as CEO, Director, or Head of.
speakerCompaniesPublic company hints around speaker text.
topicsTopic and event keywords found on the page.
industryKeywordsIndustry terms useful for segmentation.
registrationCtaRegistration or attendance call-to-action text.
platformHintsWebinar platform hints such as Zoom, ON24, Webex, or HubSpot.
companyWebsiteNormalized company website.
publicEmailsPublic email addresses visible on the page.
phonesPublic phone numbers visible on the page.
socialLinksPublic LinkedIn, X/Twitter, Facebook, or YouTube links.
contactPageUrlContact page link detected on the host website.
leadScoreComposite prospecting score.
dedupeKeyDomain-based dedupe key.
scrapedAtExtraction timestamp.

Example output

{
"eventTitle": "Marketing Automation in 2025",
"eventUrl": "https://www.example.com/events/marketing-automation-webinar",
"source": "brave-search",
"sourceQuery": "marketing automation webinar",
"hostCompany": "Example",
"hostDomain": "example.com",
"isVirtual": true,
"webinarConfidence": 74,
"topics": ["webinar", "marketing", "automation"],
"platformHints": ["zoom"],
"publicEmails": ["events@example.com"],
"leadScore": 88
}

How much does it cost to find webinar leads?

This Actor uses pay-per-event pricing.

There is a small run start event and a per-row charge for each qualified webinar lead saved.

Before publication, final prices are calculated from cloud test costs and synchronized with the Apify platform pricing record.

Search query tips

Use buyer-intent and industry-specific phrasing.

Good examples:

  • cybersecurity webinar
  • HR software demo
  • B2B SaaS workshop
  • marketing automation virtual event
  • cloud security webinar
  • customer success roundtable

Domain mode tips

Domain mode works best when you already have a target account list.

The Actor checks common website paths such as:

  • /webinars
  • /webinar
  • /events
  • /resources/webinars
  • /resources/events
  • /learn/webinars
  • /demo

Direct URL mode tips

Use direct URL mode when you already have webinar or event landing pages from another source.

This is the most deterministic mode because the Actor does not need to search.

It is useful for normalizing lists from newsletters, partner portals, communities, or internal research.

Lead scoring

leadScore combines webinar confidence, public contact availability, contact-page availability, speaker hints, and whether a detected date appears upcoming.

Use higher scores first for outreach.

Use lower scores as research leads that may require manual review.

Integrations

Common workflows:

  • Export the dataset to Google Sheets for SDR review.
  • Send high-score leads to a CRM through Make or Zapier.
  • Combine hostDomain with an email enrichment workflow.
  • Feed eventUrl into website monitoring to track new webinars.
  • Use sourceQuery to measure which market keywords produce the best accounts.

API usage with Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/webinar-lead-prospecting-workflow').call({
queries: ['cybersecurity webinar'],
maxItems: 25,
});
console.log(run.defaultDatasetId);

API usage with Python

from apify_client import ApifyClient
client = ApifyClient('APIFY_TOKEN')
run = client.actor('automation-lab/webinar-lead-prospecting-workflow').call(run_input={
'queries': ['HR software demo'],
'maxItems': 25,
})
print(run['defaultDatasetId'])

API usage with cURL

curl -X POST "https://api.apify.com/v2/acts/automation-lab~webinar-lead-prospecting-workflow/runs?token=$APIFY_TOKEN" \
-H 'Content-Type: application/json' \
-d '{"queries":["marketing automation webinar"],"maxItems":25}'

MCP usage

Use the Apify MCP server with this Actor when you want Claude Desktop or Claude Code to run webinar prospecting directly.

MCP URL:

https://mcp.apify.com/?tools=automation-lab/webinar-lead-prospecting-workflow

Claude Code setup:

$claude mcp add apify-webinar-leads https://mcp.apify.com/?tools=automation-lab/webinar-lead-prospecting-workflow

Claude Desktop JSON config example:

{
"mcpServers": {
"apify-webinar-leads": {
"url": "https://mcp.apify.com/?tools=automation-lab/webinar-lead-prospecting-workflow"
}
}
}

Example prompts:

  • "Find companies running cybersecurity webinars and export the top 25 leads."
  • "Check these domains for demo or webinar pages and return contact links."
  • "Score upcoming HR software webinars for partner outreach."

Data quality notes

The Actor extracts public page signals.

Some webinar pages omit dates, hide speakers behind scripts, or use registration forms that do not expose contact details.

Use webinarConfidence and leadScore to prioritize records that have stronger signals.

Limitations

BrightTALK and ON24 directory scraping are not required in v1 because shallow checks returned 403 during research.

The Actor does not extract attendee lists, private registration data, login-gated content, or personal data that is not public on the page.

Search results can vary by region and time.

Troubleshooting

If a run returns too few rows, broaden the query or disable domain dedupe.

If contact fields are empty, the public page likely does not expose emails or phone numbers.

If a direct URL is skipped, verify that the page is public HTML and not blocked by a login or firewall.

Legality

This Actor only targets public pages supplied or discovered during the run.

You are responsible for using the data in compliance with applicable laws, website terms, and outreach regulations.

Do not use the Actor to collect private attendee lists or bypass login gates.

FAQ

Can it find every webinar on the internet?

No. It finds publicly discoverable pages from the inputs and search results inspected in the run.

Does it replace an email verification tool?

No. It extracts public emails visible on pages. Use a verification or enrichment workflow before sending outreach.

Can I use only domains?

Yes. Provide domains and leave queries empty.

Can I use only direct URLs?

Yes. Direct URLs are the simplest mode and work well when another workflow already discovered event pages.

Does it use residential proxies?

No residential proxy is required for the current HTTP-first workflow.

Why is a page marked not upcoming?

isUpcoming is based on parseable date text. If no reliable date is found, the value may be null.