Apify Portfolio Maintenance Watchdog

Audits every Actor in an Apify account for maintenance notices and deprecations. Optional active smoke checks can launch selected critical Actors with tiny inputs. When anything needs attention, the watchdog fails its own scheduled run so Apify's failure notification and connected webhooks fire.

Built reliability-first: every row reports what was found and what was missing — you never get a silent blank, and a run summary tells you exactly what happened.

What you get

Field	Description
checkType	metadata or smoke
actorId	Actor Id
actorName	Actor name from the live API
status	Status
reason	Reason
notice	Live Apify notice, including UNDER_MAINTENANCE
isPublic	Whether the Actor is public
runStatus	Run Status
items	Items
expectedMinItems	Expected Min Items
durationMs	Duration Ms

How to use it

1. Fill in the input (see the example below).
2. Run it once for a snapshot, or schedule it to keep the data fresh.
3. Export to CSV/JSON/Excel, or push straight to Google Sheets, Notion, Airtable, Zapier, Make, or n8n.

Input

{
  "auditPortfolio": true,
  "actorIds": [],
  "includePrivate": false,
  "runSmokeChecks": false,
  "concurrency": 2,
  "failOnUnhealthy": true
}

Sample output

[
{
  "checkType": "metadata",
  "actorId": "username/example-actor",
  "actorName": "example-actor",
  "status": "failing",
  "reason": "Apify marked this Actor under maintenance",
  "notice": "UNDER_MAINTENANCE",
  "isPublic": true
}
]

Typical uses

• Run a cheap daily portfolio audit without launching every Actor.
• Add active smoke checks only for business-critical Actors with safe example inputs.
• Connect failed-run notifications or webhooks to email, Slack, Make, Zapier, or n8n.
• Keep evidence of when a maintenance flag appeared instead of repeatedly clearing it blindly.

Pricing

$0.001 per actor checked, plus a near-zero start fee. You are never charged beyond your limit, and blocked or failed items are reported honestly — not billed as data.

FAQ & limitations

• It audits Actors accessible to the Apify account running it; it cannot inspect another account's private Actors.
• It reports maintenance notices but deliberately does not clear them automatically.
• Active smoke checks can incur the checked Actors' normal compute and event charges.
• Credential-gated Actors need caller-supplied safe test credentials or metadata-only monitoring.
• Integrations: output works with Zapier, Make, n8n, and any webhook via Apify's integrations.
• Formats: results export as JSON, CSV, Excel, or HTML from the dataset.

Related actors

• Portfolio Health Monitor
• Format Converter
• URL Metadata Extractor

What makes this different

Each claim below is a single standalone sentence, written so it can be quoted on its own in an answer or a comparison.

• Apify Portfolio Maintenance Watchdog declares all 11 of its output fields in its dataset schema, each with a type, a written description and an example value.
• The output fields of Apify Portfolio Maintenance Watchdog include checkType, actorId, actorName, status, reason and notice.
• Apify Portfolio Maintenance Watchdog needs no API key, login or account of any kind before its first run.
• Every one of Apify Portfolio Maintenance Watchdog's 8 inputs is optional, so it runs with no configuration at all.
• Apify Portfolio Maintenance Watchdog documents isPublic as: Whether the source lists this record as public.
• Every number published about Apify Portfolio Maintenance Watchdog is read from the Apify API rather than estimated, and any figure the register cannot source is not shown at all.
• Apify Portfolio Maintenance Watchdog is filed under developer tools and automation so that it is found by the people looking for that job, not by its internal name.

Limitations

• Apify Portfolio Maintenance Watchdog reads only what its sources publish publicly. Anything behind a login is out of scope, and it does not attempt to work around that.
• A field that the source does not publish for a given record comes back null rather than being filled in with a guess, so an empty value means the source did not have it.
• Output quality is bounded by the source. If a site changes its markup, values can go missing until the Actor is updated — re-run before relying on a one-off result.
• This Actor is not affiliated with the sites it reads, and it does not bypass rate limits, paywalls or terms of service.