Integrations · Make

Data source health alerts in Make

Datasource Pulse plugs into Make two ways: as a scheduled scenario built on Apify’s official Make app, or as an instant trigger where Datasource Pulse pushes a webhook the moment a data source degrades. Both run on your existing Apify account at $0.02 per check.

Path 1 · Instant trigger via custom webhook (recommended)

Datasource Pulse posts JSON on every state transition - one alert when a connector degrades, one notice when it recovers. In Make that’s a native instant scenario:

1. Add a Webhooks → Custom webhook module and copy its URL.
2. Put that URL in your Datasource Pulse input (an Apify schedule is the usual runner):

{
  "checks": [ ...your checks... ],
  "webhookUrl": "https://hook.make.com/...",
  "webhookFormat": "json",
  "webhookSecret": "optional · adds X-DP-Signature for verification"
}

3. Run it once so Make learns the payload structure, then route transition, connector_label, failure_class, message, and recommended_action into Slack, email, Telegram, or any Make module. No polling and no filter needed - only real transitions arrive.

Path 2 · Scheduled scenario with the Apify app

To keep the schedule in Make: start a scenario with the Apify app’s Run an Actor module, pick growth_wizard/datasource-pulse, paste the input below, wait for finish, then fetch the run’s dataset items and add a filter that passes only items where state is not healthy:

{
  "checks": [
    {
      "type": "credential",
      "id": "serpapi-main",
      "label": "SerpAPI · search quota",
      "vendor": "serpapi",
      "apiKey": "YOUR_SERPAPI_KEY",
      "quotaSoftCap": 4500,
      "impact": "Search enrichment stops at quota"
    },
    {
      "type": "actor",
      "id": "my-scraper",
      "label": "My scraper · output drift",
      "actorId": "username~my-scraper",
      "apifyToken": "APIFY_TOKEN_WITH_READ_SCOPES",
      "enableVolumeBaseline": true,
      "enableCostBaseline": true
    }
  ]
}

Each dataset item is one verdict: state, a stable failure_class enum, a human-readable message, and your own impact note echoed back, so the alert itself says what breaks downstream.

Common questions