Integrations · n8n

Monitor scrapers, APIs, and keys from n8n

Datasource Pulse runs as an Apify Actor, and Apify ships a verified community node for n8n - so a health pass over your scrapers, endpoints, and API keys is one node in a workflow. No custom code, no separate account: your existing Apify credential runs everything, billed at $0.02 per check.

Ready-made workflows

Three importable templates. Download the JSON, then in n8n choose Workflow → Import from File, connect your Apify credential, and replace the placeholders flagged in the sticky note inside each workflow.

Want proof the alarm rings before you trust it with production? We broke an endpoint on purpose and timed how long Slack took to hear about it.

How it works

Install the Apify node once (n8n Cloud: open the nodes panel, search “Apify”, Install; self-hosted: Settings → Community Nodes → @apify/n8n-nodes-apify). Then a single node runs the whole health pass: resource Actors, operation Run an Actor and Get Dataset, actor growth_wizard~datasource-pulse, and your checks as the Input JSON:

{
  "checks": [
    {
      "type": "credential",
      "id": "openai-prod",
      "label": "OpenAI · production key",
      "vendor": "openai",
      "apiKey": "YOUR_OPENAI_KEY",
      "impact": "LLM features fail when this key dies"
    },
    {
      "type": "actor",
      "id": "my-scraper",
      "label": "My scraper · output drift",
      "actorId": "username~my-scraper",
      "apifyToken": "APIFY_TOKEN_WITH_READ_SCOPES",
      "enableVolumeBaseline": true,
      "enableCostBaseline": true
    }
  ]
}

The node returns one item per check, so standard n8n routing applies from there. Each verdict carries state, a stable failure_class enum, a human-readable message, and your own impact note echoed back - so the alert answers “what breaks?” by itself. An IF node on state ≠ healthy feeds Slack, Gmail, or anything else n8n talks to.

Common questions