📅 Tech Events & CFP Scraper avatar

📅 Tech Events & CFP Scraper

Pricing

from $4.00 / 1,000 results

Go to Apify Store
📅 Tech Events & CFP Scraper

📅 Tech Events & CFP Scraper

Extract upcoming developer conferences, local meetups, and open Call for Papers (CFP) deadlines to build a comprehensive speaking schedule for your DevRel team.

Pricing

from $4.00 / 1,000 results

Rating

0.0

(0)

Developer

太郎 山田

太郎 山田

Maintained by Community

Actor stats

0

Bookmarked

3

Total users

1

Monthly active users

15 hours ago

Last modified

Share

Tech Events Calendar API | Conferences + CFP

Developer Relations teams and developer advocates can't afford to manually search the web for speaking opportunities. This scraper completely automates your tech events intelligence gathering by crawling multiple websites to extract structured data on global conferences, local meetups, and open Call for Papers (CFP) deadlines. Whether you are hunting for JavaScript summits, Python bootcamps, AI symposiums, or DevOps conventions, this tool builds a comprehensive, deduplicated schedule of exactly where your target developer audience is gathering. Stop missing out on critical submission windows and speaker slots. By scheduling this scraper to run weekly, you can automatically fetch the latest event announcements and speaking opportunities before CFP links expire. The scraped data provides everything you need to assess an event's exact value for your DevRel strategy: the official event name, start and end dates, city and country, specific topic tags, and the direct URL to submit your speaking proposals. Instead of relying on scattered email newsletters or manually copying contact details into spreadsheets, use this scraper to extract precise event details, organize your speaker pipeline, and dominate the tech conference circuit.

Store Quickstart

  • Start with store-input.example.json for a cheap single-topic first run.
  • If that matches your workflow, switch to store-input.templates.json and pick one of:
  • Quickstart (Dataset) for one-topic discovery
  • Multi-topic Scan for a broader calendar build
  • Webhook Alert for downstream event routing

Key Features

  • 📅 Multi-topic search — Search across JavaScript, Python, AI, DevOps, and 20+ topics
  • 🔄 Automatic deduplication — Events appearing in multiple topics are merged
  • 🌍 Global coverage — Conferences from all countries, including online events
  • 📝 CFP tracking — Call-for-papers URLs and deadlines included
  • 📊 Sorted by date — Clean chronological listing
  • 🏷️ Topic tagging — Each event tagged with all relevant topics

Use Cases

WhoWhy
Developer advocatesFind conferences to speak at or sponsor
DevRel teamsPlan conference attendance calendar
RecruitersDiscover events where target developers gather
Community managersTrack events in their technology ecosystem

Input

FieldTypeDefaultDescription
topicsarrayprefilledTopics to search for (e.g. ['javascript','ai','devops']).
yearinteger2026Year to search for events.
deliverystring"dataset"How to deliver results. 'dataset' saves to Apify Dataset (recommended), 'webhook' sends to a URL.
webhookUrlstringWebhook URL to send results to (only used when delivery is 'webhook'). Works with Slack, Discord, or any HTTP endpoint.
dryRunbooleanfalseIf true, runs without saving results or sending webhooks. Useful for testing.

Input Example

{
"topics": ["javascript", "python", "ai"],
"year": 2026
}

Output

FieldTypeDescription
metaobject
resultsarray
results[].namestring
results[].urlstring (url)
results[].startDatestring
results[].endDatestring
results[].citystring
results[].countrystring
results[].onlineboolean
results[].cfpUrlstring (url)
results[].cfpEndDatestring
results[].twitterstring
results[].topicsarray
results[].sourcestring

Output Example

{
"name": "PyCon US 2026",
"url": "https://us.pycon.org/2026/",
"startDate": "2026-05-15",
"endDate": "2026-05-23",
"city": "Long Beach",
"country": "US",
"online": false,
"cfpUrl": "https://us.pycon.org/2026/speaking/",
"cfpEndDate": "2025-12-18",
"topics": ["python"],
"source": "confs.tech"
}

API Usage

Run this actor programmatically using the Apify API. Replace YOUR_API_TOKEN with your token from Apify Console → Settings → Integrations.

cURL

curl -X POST "https://api.apify.com/v2/acts/taroyamada~tech-events-intelligence/run-sync-get-dataset-items?token=YOUR_API_TOKEN" \
-H "Content-Type: application/json" \
-d '{ "topics": ["javascript", "python", "ai"], "year": 2026 }'

Python

from apify_client import ApifyClient
client = ApifyClient("YOUR_API_TOKEN")
run = client.actor("taroyamada/tech-events-intelligence").call(run_input={
"topics": ["javascript", "python", "ai"],
"year": 2026
})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
print(item)

JavaScript / Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'YOUR_API_TOKEN' });
const run = await client.actor('taroyamada/tech-events-intelligence').call({
"topics": ["javascript", "python", "ai"],
"year": 2026
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Tips & Limitations

  • Run nightly as part of your supply-chain monitoring to catch new vulnerabilities early.
  • Pair with oss-vulnerability-monitor for CVE coverage layered on top of version tracking.
  • For monorepos, run per-package rather than recursing — easier to triage alerts by team owner.
  • Use snapshotKey to persist between runs and only alert on diffs.
  • Webhook delivery supports JSON payloads — pipe into your existing on-call routing.

FAQ

Is my build slowed down?

This actor runs on Apify infrastructure, not your CI runners. No impact on build times.

What's the freshness of data?

Depends on the source registry — typically 5–60 minutes behind upstream.

Can I filter by package ecosystem?

Yes — most DevOps actors accept an ecosystem or package-manager filter in their input schema.

Does this work with private registries?

No — this actor targets public registries (npm, PyPI, crates.io, etc.). Private registries require credential handling that's out of scope.

Can I integrate with GitHub Actions?

Yes — call this actor via Apify API inside a workflow job, parse the JSON output, and fail the build on threshold violations.

DevOps & Tech Intel cluster — explore related Apify tools:

Cost

Pay Per Event:

  • actor-start: $0.01 (flat fee per run)
  • dataset-item: $0.003 per output item

Example: 1,000 items = $0.01 + (1,000 × $0.003) = $3.01

No subscription required — you only pay for what you use.

⭐ Was this helpful?

If this actor saved you time, please leave a ★ rating on Apify Store. It takes 10 seconds, helps other developers discover it, and keeps updates free.

Bug report or feature request? Open an issue on the Issues tab of this actor.