Executive Appointment Alerts avatar

Executive Appointment Alerts

Pricing

from $33.50 / 1,000 executive appointment alerts

Go to Apify Store
Executive Appointment Alerts

Executive Appointment Alerts

Executive appointments and departures classified from GlobeNewswire release headlines: company, person, role and direction, with headline, date and link. Remembers deliveries so a scheduled run never bills a release twice. Pay per alert.

Pricing

from $33.50 / 1,000 executive appointment alerts

Rating

0.0

(0)

Developer

NexGen Watch

NexGen Watch

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

📰 Executive Appointment Alerts

Executive appointments and departures — person, role and direction, classified from the headline of the wire release itself. Each row carries the structured facts pulled from that headline plus the headline, the publish date and the release link — never the article body. Source: GlobeNewswire's public subject-coded and keyword RSS feeds (the Directors and Officers subject feed plus Company Announcement); public RSS only, no login, no paywall, robots honoured per feed.

Never billed twice (2026-09-17). Every alert delivered is remembered (release id and headline) in a named key-value store under historyId, so a run on a schedule delivers only releases it has not billed before; syndicated copies of the same release inside one scan are collapsed; releases older than maxAgeDays (default 30) are never billed. Measured yield on a fresh history: 9 alerts from 39 headlines on 2026-09-18.

Output is one event_alert row per result; billing is pay-per-event, the value event being one executive appointment alert (a $0.02 start fee per run, then $0.05 per executive appointment alert). Source: www.globenewswire.com.

No login, no API key and no CAPTCHA solving are involved: the source is read logged-out.

📊 Sample Output

Executive Appointment Alerts sample output — a table of real executive appointment alert rows (published_at, publisher, event_type, company) from run pA33wdYUsz3sbe7uJ on build 0.1.19

Real rows from run pA33wdYUsz3sbe7uJ on build 0.1.19 (2026-09-18), the same input as the Quick start below — every value is as the source published it (emails masked, long text shortened):

published_atpublisherevent_typecompanypersonrole
2026-09-17GlobeNewswire — Directors and Officersexecutive_appointmentA Different Kind of Tech Group: Rick MakosRick MakosCEO
2026-09-17GlobeNewswire — Directors and Officersexecutive_appointmentBlue Mantis Strengthens Operational Leadership to Support Next Phase oJason BernsteinChief Operating Officer
2026-09-17GlobeNewswire — Directors and Officersexecutive_appointmentEarthOpticsJames ClementChief Growth Officer
2026-09-17GlobeNewswire — Directors and Officersexecutive_appointmentGordon BrothersTron AllenManaging Director
2026-09-17GlobeNewswire — Directors and Officersexecutive_appointmentBayCareBrendan MalikVice President
2026-09-17GlobeNewswire — Directors and Officersexecutive_appointmentErnexa TherapeuticsRobert J. SpiegelBoard of Directors
2026-09-17GlobeNewswire — Directors and Officersexecutive_appointmentPetMedsJeff WillardCEO
2026-09-17GlobeNewswire — Directors and Officersexecutive_appointmentDuke RoboticsAvi LevinChief Financial Officer

The run finished with the status message: NORMAL: 9 executive-appointment alerts over 39 headlines. billable=9

✅ What you get

Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is null):

  • record_type (string) — e.g. event_alert
  • event_slug (string/null) — e.g. executive-appointment
  • headline (string/null) — e.g. A Different Kind of Tech Group: Rick Makos Named CEO of Hebron Holdings
  • published_at (string/null) — e.g. 2026-09-17
  • publisher (string/null) — e.g. GlobeNewswire — Directors and Officers
  • source_url (string/null) — e.g. https://www.globenewswire.com/news-release/2026/09/17/3364345/0/en/a-different-k
  • guid (string/null) — e.g. https://www.globenewswire.com/news-release/2026/09/17/3364345/0/en/a-different-k
  • observed_at (string/null) — e.g. 2026-09-18T00:16:54Z
  • event_type (string/null) — e.g. executive_appointment
  • company (string/null) — e.g. A Different Kind of Tech Group: Rick Makos
  • person (string/null) — e.g. Rick Makos
  • role (string/null) — e.g. CEO
  • direction (string/null) — e.g. appointment
  • companies (array/null) — e.g. ["A Different Kind of Tech Group: Rick Makos"]
  • acquirer (string/null) — null in every sample row
  • target (string/null) — null in every sample row
  • deal_value (string/null) — null in every sample row
  • expansion_type (string/null) — null in every sample row
  • location (string/null) — null in every sample row
  • company_a (string/null) — null in every sample row
  • company_b (string/null) — null in every sample row
  • partnership_type (string/null) — null in every sample row
  • product (string/null) — null in every sample row
  • category (string/null) — null in every sample row
  • terminal (string/null) — null in every sample row
  • scanned (integer/null) — null in every sample row
  • matched_no_date (integer/null) — null in every sample row
  • feed_errors (array/null) — null in every sample row
  • delivered (integer/null) — null in every sample row

Every run also writes a RUN_RECEIPT record to its key-value store with the source checks it made and the counts it charged — diagnostics never land in the paid dataset.

⚙️ Sample inputs

1. Quick start — the Store example (this is what the sample above came from)

{
"maxRecords": 25
}

The sample run charged exactly: 1 × $0.02 apify-actor-start + 9 × $0.05 executive_appointment_alert = $0.47 on the Free tier — every delivered row was billed.

2. A smaller, narrowed run

{
"maxRecords": 5,
"historyId": "default"
}

Caps the run at 5 rows — about $0.27 on the Free tier ($0.02 start + 5 × $0.05). historyId narrows what the source is asked for.

3. A full-size run

{
"maxRecords": 200
}

Up to 200 rows (the schema default for maxRecords) — about $10.02 on the Free tier ($0.02 start + 200 × $0.05) if the source has that many.

🧾 JSON sample record

One real record from run pA33wdYUsz3sbe7uJ, exactly as it lands in the dataset (emails masked, long text shortened):

{
"record_type": "event_alert",
"event_slug": "executive-appointment",
"headline": "A Different Kind of Tech Group: Rick Makos Named CEO of Hebron Holdings",
"published_at": "2026-09-17",
"publisher": "GlobeNewswire — Directors and Officers",
"source_url": "https://www.globenewswire.com/news-release/2026/09/17/3364345/0/en/a-different-kind-of-tech-group-rick-makos-named-ceo-of-hebron-holdings.html",
"guid": "https://www.globenewswire.com/news-release/2026/09/17/3364345/0/en/a-different-kind-of-tech-group-rick-makos-named-ceo-of-hebron-holdings.html",
"observed_at": "2026-09-18T00:16:54Z",
"event_type": "executive_appointment",
"company": "A Different Kind of Tech Group: Rick Makos",
"person": "Rick Makos",
"role": "CEO",
"direction": "appointment",
"companies": [
"A Different Kind of Tech Group: Rick Makos"
]
}

🔧 How it works

Source. The actor reads www.globenewswire.com — endpoints: https://www.globenewswire.com/RssFeed/subjectcode/11-x/feedTitle/GlobeNewswire, https://www.globenewswire.com/RssFeed/subjectcode/9-x/feedTitle/GlobeNewswire. Public pages and feeds only; nothing behind a login.

Transport. Plain HTTPS from the Apify platform, no proxy. robots.txt is read first and a disallowed path is never fetched.

Terminal states. A run ends NORMAL, CAPPED (your cap was reached), PARTIAL (something was withheld and the message says what), GENUINE_EMPTY (the source was read and truly had nothing in scope) or BLOCKED (the source refused or changed shape — the run FAILS loud and bills nothing). A zero-row run is never reported as a silent success.

Charging. Each executive appointment alert is charged at the moment it is pushed (executive_appointment_alert); a row that fails to charge is not delivered, so the dataset count always equals the charged count.

Classification. A headline is an alert only when it clearly states this event type; the classifiers are mutually exclusive (an M&A headline is never a partnership, and so on) and a headline that does not clearly state the event is skipped, unbilled. Entities (companies, person, role, location, deal value) are extracted from the headline only — a wire label such as "GlobeNewswire — Partnerships" is never taken as the company.

Feeds. GlobeNewswire's public RSS feeds each carry the 20 most recent releases in that subject or keyword tag, so a scheduled run sees a rolling window; sources can be replaced with any public RSS/Atom/JSON feed list.

Delivery memory. skipPreviouslyDelivered (default true) keeps the ids and headlines of everything billed under historyId in a named key-value store for 120 days; set it to false for a one-off full scan, or use a different historyId per client.

What is not done. No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.

⏰ Set it on a schedule

A single run is a snapshot. The value is the feed: open the actor in Apify Console → SchedulesCreate new, add this actor with the input you want, and pick a cadence:

  • Daily0 7 * * * (07:00 UTC): catch changes within a day.
  • Weekly0 7 * * 1: a Monday digest.

Each run is independent; keep the same input on the schedule so the results stay comparable. Schedules can also POST results to a webhook (Console → Integrations).

💰 Pricing example

EventFreeBronzeSilverGold
Actor Start (apify-actor-start)$0.02$0.02$0.02$0.02
Executive Appointment Alert (executive_appointment_alert)$0.05$0.04$0.04$0.03

Worked at the live Free-tier price:

  • 8 executive appointment alerts: $0.02 start + 8 × $0.05 = $0.42
  • 25 executive appointment alerts: $0.02 start + 25 × $0.05 = $1.27
  • 200 executive appointment alerts: $0.02 start + 200 × $0.05 = $10.02

A run that delivers zero rows charges the $0.02 start fee only. A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 1024 MB.

Yield on the sample run: NORMAL: 9 executive-appointment alerts over 39 headlines. billable=9. maxRecords is a hard ceiling on what is delivered and billed, never a target.

This actor reads public, logged-out pages and feeds published by www.globenewswire.com. It collects only what the source publishes to any visitor, keeps to the source's robots rules (checked on every run), identifies itself, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring.

❓ FAQ

Q: Do I need an API key or a login?
A: No. The source (www.globenewswire.com) is read logged-out; the input schema has no key field and the actor carries no secrets.

Q: Why did my run return 0 rows?
A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input; BLOCKED means the source refused and the run failed without billing a value event — retry later or narrow the input. A zero-row run bills the start fee only.

Q: How many rows can one run return?
A: Up to maxRecords (default 200). Raise the cap for a bigger run; you pay per delivered row.

Q: How fresh is the data?
A: Every run reads the source live at run time; nothing is cached between runs. Put it on a schedule for a continuous feed.

Q: What formats can I export?
A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration.

Q: How is this different from the other newswire event alerts actors?
A: Same output shape and billing model; this one covers www.globenewswire.com. The siblings under Related Actors cover the other sources or slices — run several on one schedule for a combined feed.

Q: Are there rate limits?
A: The actor paces itself against the source and honours its robots rules; there is no per-buyer limit beyond your Apify plan's concurrency.

🆘 Troubleshooting

  • Run FAILED with BLOCKED → the source refused the request or changed its page shape → nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id.
  • Status says CAPPED → your cap (maxRecords) was reached → raise it for a bigger run.
  • Input validation error on start → a field is outside the schema's allowed values → start from the Quick start block and change one field at a time.
  • Run TIMED-OUT → a very wide request on a slow day → raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset.
  • Company Expansion Alerts — Company expansions — new offices, plants, headquarters, market entries and hiring pushes — classified from GlobeNewswire subject and keyword feeds: c…
  • Merger & Acquisition Alerts — Announced mergers and acquisitions classified from GlobeNewswire release headlines: acquirer, target, deal value and stake, with headline, date and l…
  • Partnership Alerts — Announced partnerships, joint ventures, MOUs and integrations classified from GlobeNewswire release headlines: the parties, partnership type, headlin…
  • Product Launch Alerts — Product and service launches classified from GlobeNewswire release headlines: company, product, category, headline, date and link. Remembers what it…
  • 🏢 About NexGenData — NexGen Watch is NexGenData's fleet of 256 public monitoring and lookup actors built on official sources, pay-per-result. Browse the catalog at apify.com/nexgenwatch.

⭐ Found this useful?

If this actor saved you a manual check, a quick review on the Apify Store helps other teams find it. Feature request or a source that changed? Open it from the Issues tab — every one is read.