# Datasource Pulse · full site text

> Complete text content of https://datasourcepulse.com/ in one file, for LLMs and agents. The curated index is at https://datasourcepulse.com/llms.txt.

Last updated: 2026-07-26

---

Datasource Pulse
The Problem How it Works Integrations Pricing Blog For Agents
Run it on Apify (https://apify.com/growth_wizard/datasource-pulse)

System Operational
x402-payable · no approval

# Know when any data connector fails silently.

Even when everything looks "up." Monitor API credentials, usage quotas, and scraper output quality across your whole pipeline on a schedule you choose. One alert when it degrades, one notice when it recovers.
Run it on Apify (https://apify.com/growth_wizard/datasource-pulse)
$0.02 per check • No subscription

slack_alerts / #data-ops

Datasource Pulse 10:42 AM
Recovered: GitHub · main PAT
GitHub PAT validity + core rate-limit remaining. Rate limit reset.

Datasource Pulse 3:14 AM
Failing: OpenAI · production key
Failure class: quota_exhausted
Impact: Summarization worker will crash on next batch.
Action required: Rotate key or increase billing limit at platform.openai.com

## Your pipeline degrades silently.

Your SerpAPI quota runs out. Your GitHub PAT expires over the weekend. The TikTok or LinkedIn Actor your pipeline depends on ships a changed output schema. Its maintainer's decision, not yours. None of it crashes your app. Your output just gets quietly worse until a customer notices. Datasource Pulse notices first.

### Catch expiration before it breaks

Rotate a key on your schedule, not after a customer complains.

### Track quota proactively

Know when you're at 80% before you hit the 100% wall.

### Catch output schema changes

A maintainer renames one field and your tables fill with nulls → you'll know the run it happens, not weeks later.

### Reduce incident response time

One message the moment something degrades, not hours later.

### Maintain downstream SLAs

Your data products stay reliable even when your vendors aren't.

### Visibility across your stack

One check instead of logging into every vendor console separately.

## The steady pulse of reliable infrastructure.

Datasource Pulse runs on a schedule you choose. It probes your connectors, compares them to the last known state, and fires exactly one deduplicated alert when things change.

### 1. Scheduled Trigger

Runs every 1-6 hours, or triggered on-demand by an AI agent.

### 2. Probe Data

Checks credential health, quotas, or scraper output quality across any source you point it at.

### 3. State Check

Compares result to previous memory. Detects degradation or recovery.

### 4. One Alert

Fires a single Slack message on change. Logs a record to your dataset.

### No alert storms.

If a connector fails, you get one alert. If it's still failing on the next run, we stay quiet. You only hear from us again when it escalates (like a quota going from 80% to 100%) or when it recovers.

- Includes the specific failure classification (e.g., quota_exhausted ) so you know exactly what to fix.
- Echoes your custom impact note verbatim so the on-call engineer knows what broke downstream.

POST /webhook

{
"transition": "healthy -> failing",
"connector_id": "serpapi-main",
"failure_class": "quota_exhausted",
"message": "SerpAPI failing...",
"impact": "Search indexing halted",
"metadata": {
"quota_used_pct": 100.0
}
}

Probe Type 1

## Credential & Quota Health

We make the cheapest authenticated call per vendor: enough to prove your token is alive and read your current usage. Know when you're at 80% capacity before you hit the wall.

-

#### Catch Dead Tokens

Validates API keys, OAuth refresh tokens, and Bearer tokens without consuming expensive credits.

-

#### Custom Quota Soft Caps

Evaluate warnings against your budget line, not the vendor's billing wall. Get notified before an unexpected spike costs you thousands.

### Any endpoint. The current 35+ pre-wired list is a head start, not a limit.

OpenAI Anthropic GitHub Stripe SerpAPI Resend X/Twitter Reddit Gemini Groq Mistral Cohere Perplexity Together OpenRouter Firecrawl Exa Tavily Bright Data ScrapingBee ZenRows ElevenLabs Deepgram AssemblyAI Replicate Hugging Face Pinecone Supabase Airtable Google OAuth + Any HTTP endpoint

Not on the list? One generic_http check monitors anything with a URL: your own API, a partner feed, your database's REST or health endpoint. And the pre-wired list keeps growing.
Example: OpenRouter
"type": "credential",
"vendor": "openrouter",
"quotaSoftCap": 50.00

Probe Type 2

## Scraper Output Quality

Official APIs are locked down, so your pipeline probably depends on third-party scrapers (TikTok, Google Maps, LinkedIn) built by someone else. When their maintainer pushes a breaking schema change, your app quietly consumes garbage data.

Datasource Pulse monitors the Actors you don't own.
Success / Failure Rate
7-day and 30-day rolling baselines

Output Schema Drift
Alerts immediately if field names change

Actor Staleness
Detects abandoned or outdated scrapers

Volume Drops
Catches silent empty-result runs

Cost Spikes
Warns if compute time suddenly balloons

dataset_record.json

{ "check_type": "actor", "connector_label": "Compass Google Maps", "state": "failing", "failure_class": "schema_drift", "message": "Output schema changed.", "metadata": { "missing_fields": [ "reviewsCount", "price" ], "new_fields": [ "review_metrics" ], "actor_id": "compass~google-maps" } }

Alert fired before your ETL job ingested the missing fields.

Built for Agents

## Agent-first architecture.

AI agents build autonomous data pipelines. Datasource Pulse is the drop-in reliability check that tells them when their tools are broken.

### API & MCP Ready

Discoverable and callable as a tool via the Apify API and MCP. Takes a structured JSON input manifest, returns exactly one status record per connector.
Agent access docs →

### Machine-Readable Errors

No parsing human error strings. A stable failure_class enum ( dead_token, schema_drift, rate_limited ) lets agents branch logic automatically.

### x402 Payments · Live

Agents buy health checks from our API today: $0.02 in USDC on Base, no account of any kind. Listed in Coinbase’s x402 Bazaar, settled on-chain, verifiable by anyone.
How the first payment went → Live payment feed on x402scan (https://www.x402scan.com/recipient/0x7cCb91a3ad4c45097bDA4C3C29d2Cc89fA93Ab36)

## Radically simple pricing.

Pay for the check, not the result. A dead token or exhausted quota still bills, because catching that failure is exactly the value you're paying for.

### Pay per event

No subscriptions. No per-run minimums.

- Charge applies on attempt (failures count)
- Subset recheck: preflight expensive jobs by checking just one key
- Set a hard max cost ceiling per run
- x402 agentic payments supported (USDC on Base)
Total = number of checks × $0.02

$0.02
per connector checked
Run it on Apify (https://apify.com/growth_wizard/datasource-pulse)
Runs on your Apify account.

Light Setup
3 connectors, every 6h
~$7 / mo

Standard
5 connectors, every 3h
~$24 / mo

Heavy
10 connectors, hourly
~$144 / mo

Datasource Pulse

The heartbeat monitor for your data supply chain.

Datasource Pulse monitors API credentials, usage quotas, and scraper output quality across your data pipeline. It knows when your SerpAPI quota runs out, when your GitHub PAT expires, and when the TikTok or LinkedIn Actor your pipeline depends on ships a changed output schema. Its maintainer’s decision, not yours. One alert when something degrades, one notice when it recovers. Runs on your schedule as an Apify Actor · $0.02 per check, billed per connector, no subscription.

Run it on Apify (https://apify.com/growth_wizard/datasource-pulse) Blog · For Agents · n8n · Zapier · Make llms.txt · llms-full.txt

© 2026 Datasource Pulse

Monitor after you adopt. Audit before you adopt with Audit Tools (https://audit-tools.ai) · independent, evidence-backed evaluation of Apify actors. From the maker of Demand Discovery AI (https://demanddiscovery.ai).

---

# Page: https://datasourcepulse.com/blog

Datasource Pulse
The Problem How it Works Integrations Pricing Blog For Agents
Run it on Apify (https://apify.com/growth_wizard/datasource-pulse)

Blog · Datasource Pulse

# Field notes from the data supply chain.

What we learn running health checks on APIs, keys, and scrapers: staged failures, agents that pay their own way, and the quiet ways data pipelines break.

July 24, 2026 · Featured

## An AI agent just paid our API two cents. No account. No card. No human.

An AI agent hit our x402 endpoint, paid $0.02 in USDC on Base, and got a live connector health verdict back. The payment settled on a public blockchain, so the payer, the receiver, and the amount are all checkable. On-chain proof inside.
Read the post →
July 25, 2026 · n8n

## We broke an endpoint on purpose

We pointed one of our n8n templates at a deliberately broken endpoint and watched the Slack alert land in about a minute. Every check is JSON you design: any endpoint, key, or actor, with 35+ vendors pre-wired as a head start.
Read the post →

Datasource Pulse

The heartbeat monitor for your data supply chain.

Datasource Pulse monitors API credentials, usage quotas, and scraper output quality across your data pipeline. It knows when your SerpAPI quota runs out, when your GitHub PAT expires, and when the TikTok or LinkedIn Actor your pipeline depends on ships a changed output schema. Its maintainer’s decision, not yours. One alert when something degrades, one notice when it recovers. Runs on your schedule as an Apify Actor · $0.02 per check, billed per connector, no subscription.

Run it on Apify (https://apify.com/growth_wizard/datasource-pulse) Blog · For Agents · n8n · Zapier · Make llms.txt · llms-full.txt

© 2026 Datasource Pulse

Monitor after you adopt. Audit before you adopt with Audit Tools (https://audit-tools.ai) · independent, evidence-backed evaluation of Apify actors. From the maker of Demand Discovery AI (https://demanddiscovery.ai).

---

# Page: https://datasourcepulse.com/blog/an-ai-agent-just-paid-us

Datasource Pulse
The Problem How it Works Integrations Pricing Blog For Agents
Run it on Apify (https://apify.com/growth_wizard/datasource-pulse)

July 2026 · Datasource Pulse

# An AI agent just paid our API two cents. No account. No card. No human.

This week an AI agent called our API, was told the price, paid it, and got what it paid for. The whole exchange took a few seconds. Nobody created an account, nobody typed a card number, nobody was awake. The price was two cents.

Full disclosure, first: the agent was ours. We built it to prove the pipe end to end with real money before saying a word publicly. That is also why this post can exist: the payment settled on a public blockchain, so you can check the payer, the receiver, and the amount yourself. The links are below. The pipe neither knows nor cares whose agent is calling, and that is the entire point.

## The 30-year-old error code that finally works

HTTP has reserved status code 402, “Payment Required,” since the 1990s. It sat unused for three decades because software had no way to just pay. x402, an open standard launched by Coinbase and others, finally fills it in: when a machine hits a paid endpoint, the 402 response carries exact payment instructions. The machine pays in USDC (a digital dollar), retries the request with the receipt attached, and gets its answer. No checkout page, no OAuth dance, no invoice at the end of the month.

## Why a monitoring API wants to be paid this way

Datasource Pulse answers one question: is this data connector actually working? Agents have exactly that question at exactly one moment, right before committing to an expensive run. That preflight is now a two-cent purchase: POST a credential or an actor id to our endpoint, pay $0.02, and get back a machine-readable verdict with a stable failure class an agent can branch on.

A machine about to spend real money on a scrape first buys a health check on its own dependency. Machines buying insurance for machines, two cents at a time. We find this both completely sensible and slightly surreal.

## Check the receipts

- The settlement, on the public record: the transaction on Base (https://basescan.org/tx/0xb3f2cb9bd5a839d40d1d9bf816f381a00e616f0ebc5115c01270afba2fb2faa5)
- Every payment to our receiving address, as it happens: our page on x402scan (https://www.x402scan.com/recipient/0x7cCb91a3ad4c45097bDA4C3C29d2Cc89fA93Ab36)
- The listing: Coinbase’s public x402 catalog (the Bazaar) carries our endpoint, its price, and its full input and output schemas, so any agent can discover it through the discovery API without ever visiting this site.
- The endpoint itself: POST https://datasourcepulse.com/api/x402/check · calling it without payment returns the 402 envelope, which is also the price list.

## For the technical readers

Standard HTTPS. The POST returns 402 with an x402 v1 envelope: $0.02 in USDC on Base, settled through the Coinbase facilitator, 90-second timeout, input and output schemas included in the envelope and mirrored in the public listing. With x402-fetch it is a wrapped fetch call and nothing else. The paid response is a machine-readable verdict: state, failure class, message, recommended action, and probe latency.

## What happens next

The rail is live, the listing is public, and the endpoint does not know whose agent is calling. If you are building an agent that depends on third-party data, give it two cents and let it check its own dependencies before it trusts them.

Datasource Pulse watches the data sources your product depends on: credentials, quotas, and scraper output quality. One alert when something degrades, one notice when it recovers.
Run it on Apify (https://apify.com/growth_wizard/datasource-pulse) Back to datasourcepulse.com

Datasource Pulse

The heartbeat monitor for your data supply chain.

Datasource Pulse monitors API credentials, usage quotas, and scraper output quality across your data pipeline. It knows when your SerpAPI quota runs out, when your GitHub PAT expires, and when the TikTok or LinkedIn Actor your pipeline depends on ships a changed output schema. Its maintainer’s decision, not yours. One alert when something degrades, one notice when it recovers. Runs on your schedule as an Apify Actor · $0.02 per check, billed per connector, no subscription.

Run it on Apify (https://apify.com/growth_wizard/datasource-pulse) Blog · For Agents · n8n · Zapier · Make llms.txt · llms-full.txt

© 2026 Datasource Pulse

Monitor after you adopt. Audit before you adopt with Audit Tools (https://audit-tools.ai) · independent, evidence-backed evaluation of Apify actors. From the maker of Demand Discovery AI (https://demanddiscovery.ai).

---

# Page: https://datasourcepulse.com/blog/we-broke-an-endpoint-on-purpose

Datasource Pulse
The Problem How it Works Integrations Pricing Blog For Agents
Run it on Apify (https://apify.com/growth_wizard/datasource-pulse)

July 2026 · Datasource Pulse

# We broke an endpoint on purpose. Slack knew within a minute.

This week we imported one of our own n8n templates into a fresh n8n cloud workspace, pointed it at a web address we knew would fail, and pressed run. About a minute later a Slack channel got the message below. That is the whole product in one sentence: something you depend on broke, and the right room heard about it before any human went looking.

Full disclosure, as usual: the outage was staged. The check points at a URL that answers 404 on purpose, because the only way to trust an alarm is to hear it ring before there is a real fire. Everything else was production grade: a real n8n workspace, the real Datasource Pulse actor on Apify, a real two-cent charge, and a real Slack message.

🚨 Datasource Pulse · Test endpoint · reachable

State: failing · unexpected_response

Expected HTTP 200, got 404.

Automated with this n8n workflow

Recreated as a graphic for legibility. The wording is verbatim from the real alert.

## Sixty seconds, four boxes

The workflow is four nodes and no code. A schedule fires. The Apify node runs one Datasource Pulse health pass, which is where the two cents go. An IF node reads the verdict and lets healthy results die quietly. Anything else becomes a Slack message carrying the state, the failure class, and what was expected versus what actually came back.

The part that makes this work is that the verdict is built for branching, not for reading. Every check returns state, failure_class and a one-line message as stable strings, so the entire routing logic in n8n is one condition: state ≠ healthy. No parsing, no regex, no glue function.

## Three templates, import and go

The one we fire-drilled above is one of three ready-made workflows. Each is a JSON file you import into n8n, connect your Apify account to with one OAuth click, and point at your own scrapers, keys, or actors. Costs are billed by Apify per check, with no subscription:

- Scraper health check → Slack · Watches a scraper and the endpoint it feeds, every six hours, and posts unhealthy verdicts to a channel. 2 checks × 4 runs a day ≈ $4.90 a month.
- Daily API key + quota watchdog → Gmail · Validates three API keys once a day and emails you before a dead key takes the pipeline down with it. 3 keys × 1 run a day ≈ $1.83 a month.
- Actor output drift monitor → email · Checks one Apify actor a day for schema drift, volume drops, and staleness, and emails on anything unhealthy. 1 actor × 1 run a day ≈ $0.61 a month.

Full setup steps, the input JSON reference, and the verdict schema live on the n8n integration page.

## You design the checks. The list is just the head start.

One thing the templates can make easy to miss: none of this is fixed to a vendor list. Every check is a small block of JSON that you write, so Datasource Pulse watches whatever you point it at. Any HTTP endpoint, any API key, any Apify actor, including services we have never heard of. If it has a URL, it can have a health check.

The 35+ vendors that come pre-wired (OpenAI, Anthropic, Stripe, GitHub, and the rest) are there so your first checks take thirty seconds instead of an afternoon, with each vendor’s credential and quota quirks already handled. We keep wiring more, but the list is a head start, not a limit: anything missing from it is one generic_http block away, today, without waiting on us. And if you are an agent reading this, the same applies to you: the input schema is public, and any check you can describe in JSON is a check you can run.

## Four things that will bite you, so they bite you here instead

We import-tested these in a clean workspace this week and hit every one of the following. Learn from our morning:

- Imports merge into whatever workflow is open. Create a fresh empty workflow first, then use Import from File, or you will find three schedules sharing one canvas.
- Operation names drift between node versions. The current Apify node calls the right operation “Run an Actor and Get Dataset”. If an older tutorial names something close but not identical, trust the dropdown, not the tutorial. Our templates are current as of this week.
- Create the Apify credential from inside the node. The “Connect to Apify” button in the node panel gets you the right credential type with one OAuth click.
- Leave Timeout and Build Tag empty. Empty means sensible defaults: wait as long as the check needs, run the newest build.

## An alarm you have never heard ring is a liability

Whatever monitoring you set up, in n8n or anywhere else, break something on purpose once. Point a check at a URL that does not exist, watch the alert arrive, then swap in the real thing. The thirty seconds of staged failure is what turns “we have monitoring” into “we have monitoring we have heard.”

Datasource Pulse watches the data sources your product depends on: credentials, quotas, and scraper output quality. One alert when something degrades, one notice when it recovers.
Run it on Apify (https://apify.com/growth_wizard/datasource-pulse) Get the n8n templates Back to datasourcepulse.com

Datasource Pulse

The heartbeat monitor for your data supply chain.

Datasource Pulse monitors API credentials, usage quotas, and scraper output quality across your data pipeline. It knows when your SerpAPI quota runs out, when your GitHub PAT expires, and when the TikTok or LinkedIn Actor your pipeline depends on ships a changed output schema. Its maintainer’s decision, not yours. One alert when something degrades, one notice when it recovers. Runs on your schedule as an Apify Actor · $0.02 per check, billed per connector, no subscription.

Run it on Apify (https://apify.com/growth_wizard/datasource-pulse) Blog · For Agents · n8n · Zapier · Make llms.txt · llms-full.txt

© 2026 Datasource Pulse

Monitor after you adopt. Audit before you adopt with Audit Tools (https://audit-tools.ai) · independent, evidence-backed evaluation of Apify actors. From the maker of Demand Discovery AI (https://demanddiscovery.ai).

---

# Page: https://datasourcepulse.com/agents

Datasource Pulse
The Problem How it Works Integrations Pricing Blog For Agents
Run it on Apify (https://apify.com/growth_wizard/datasource-pulse)

For agents · Datasource Pulse

# Agent access

Three ways for an agent (or the human wiring one up) to run Datasource Pulse: Apify’s official MCP server, the plain Apify API, or the x402 endpoint that needs no account of any kind. Every snippet below is copy-paste ready; the example check pings a public URL, so no secrets are required to try it.

From the blog · July 24, 2026

An AI agent just paid our API two cents. No account. No card. No human.

The full story of the first agent payment: $0.02 in USDC on Base, settled on a public blockchain, with the transaction receipt inside.
Read the post →

## MCP

Apify runs an official MCP server; the URL below scopes it to this Actor, so a connected agent sees Datasource Pulse as a callable tool with its full input schema. Works today in any MCP client. Bring an Apify token; clients that support OAuth can omit the header and sign in instead.

{
"mcpServers": {
"datasource-pulse": {
"url": "https://mcp.apify.com/?tools=growth_wizard/datasource-pulse",
"headers": {
"Authorization": "Bearer YOUR_APIFY_TOKEN"
}
}
}
}

## Direct API (curl)

One synchronous call: run the Actor and get the dataset back. The response is one status record per connector checked, with a stable failure_class enum an agent can branch on.

curl -X POST \
"https://api.apify.com/v2/acts/growth_wizard~datasource-pulse/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"checks": [{
"type": "credential",
"id": "public-ping",
"label": "Public ping - GitHub Zen",
"vendor": "generic_http",
"url": "https://api.github.com/zen",
"successStatusCode": 200
}]
}'

## LangChain

Via Apify’s official LangChain integration. The tool exposes the same JSON input; results come back as the run’s dataset records.

# pip install langchain-apify
# export APIFY_API_TOKEN=your_token
from langchain_apify import ApifyActorsTool

tool = ApifyActorsTool("growth_wizard/datasource-pulse")
result = tool.invoke(input={"run_input": {"checks": [{
"type": "credential",
"id": "public-ping",
"vendor": "generic_http",
"url": "https://api.github.com/zen",
"successStatusCode": 200
}]}})

## x402: no account at all

A single health check for $0.02 in USDC on Base, paid per request. No Apify account, no API key, no signup. Calling the endpoint unpaid returns a standard x402 v1 envelope carrying the price, the pay-to address, and the full input and output schemas: the 402 is the documentation.

curl -si -X POST https://datasourcepulse.com/api/x402/check \
-H "Content-Type: application/json" -d '{}'
# -> HTTP 402 + JSON envelope: price, pay-to, input/output schemas
Paying takes one wrapped fetch:

// npm i x402-fetch viem
import { wrapFetchWithPayment } from "x402-fetch";
import { privateKeyToAccount } from "viem/accounts";

const account = privateKeyToAccount(process.env.WALLET_KEY);
const payFetch = wrapFetchWithPayment(fetch, account);

const res = await payFetch("https://datasourcepulse.com/api/x402/check", {
method: "POST",
headers: { "Content-Type": "application/json" },
body: JSON.stringify({
vendor: "generic_http",
url: "https://api.github.com/zen",
successStatusCode: 200,
}),
});
console.log(await res.json()); // { state, failure_class,... }
The endpoint is listed in Coinbase’s public x402 catalog (the Bazaar), and every settlement is public: live payment feed on x402scan (https://www.x402scan.com/recipient/0x7cCb91a3ad4c45097bDA4C3C29d2Cc89fA93Ab36) · how the first payment went.

This origin also publishes its x402 manifest at /.well-known/x402.json: the standard DiscoveredResource envelope with full input and output schemas, so an agent can learn what is payable here without a facilitator or a prior transaction.

Datasource Pulse watches the data sources your product depends on: credentials, quotas, and scraper output quality. One alert when something degrades, one notice when it recovers.
Run it on Apify (https://apify.com/growth_wizard/datasource-pulse) Back to datasourcepulse.com

Datasource Pulse

The heartbeat monitor for your data supply chain.

Datasource Pulse monitors API credentials, usage quotas, and scraper output quality across your data pipeline. It knows when your SerpAPI quota runs out, when your GitHub PAT expires, and when the TikTok or LinkedIn Actor your pipeline depends on ships a changed output schema. Its maintainer’s decision, not yours. One alert when something degrades, one notice when it recovers. Runs on your schedule as an Apify Actor · $0.02 per check, billed per connector, no subscription.

Run it on Apify (https://apify.com/growth_wizard/datasource-pulse) Blog · For Agents · n8n · Zapier · Make llms.txt · llms-full.txt

© 2026 Datasource Pulse

Monitor after you adopt. Audit before you adopt with Audit Tools (https://audit-tools.ai) · independent, evidence-backed evaluation of Apify actors. From the maker of Demand Discovery AI (https://demanddiscovery.ai).

---

# Page: https://datasourcepulse.com/integrations/n8n

Datasource Pulse
The Problem How it Works Integrations Pricing Blog For Agents
Run it on Apify (https://apify.com/growth_wizard/datasource-pulse)

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.

### Scraper health check → Slack alert

Every 6 hours: one pass over your scraper and the endpoint it feeds. Unhealthy verdicts become Slack messages with the failure class and what breaks downstream.

Cost on your Apify account: 2 checks × 4 runs/day ≈ $4.90/month
Download workflow JSON

### Daily API key + quota watchdog → Gmail

Every morning: validates your keys against the live vendor APIs (35+ vendors pre-wired, plus generic_http for any endpoint you add) and checks usage against your own budget caps. A silently revoked key or a blown quota lands in your inbox, not in production.

Cost on your Apify account: 3 keys × 1 run/day ≈ $1.83/month
Download workflow JSON

### Actor output drift monitor → email

Daily: baselines a watched actor’s recent runs and alerts on volume drops, cost spikes, and staleness - the quiet failure modes where a scraper keeps running but the data degrades.

Cost on your Apify account: 1 actor × 1 run/day ≈ $0.61/month
Download workflow JSON

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

### Can n8n monitor an Apify actor for silent failures?

Yes. An actor check baselines recent runs and flags volume drops, cost spikes, and staleness - failure modes that never throw an error. It works for your own actors and for public actors you depend on.

### How do I get alerted in n8n when an API key stops working?

A credential check calls the vendor’s live API with your key and classifies the result: dead credential, rate limited, quota exhausted, or healthy. Schedule it daily and route anything unhealthy to your alert channel - the API key + quota watchdog template above is exactly that.

### What does it cost?

$0.02 per check per run, billed through your Apify account (pay-per-event, no subscription). A daily three-key watchdog is about $1.83/month.

Also available: Zapier · Make · agent access (MCP, API, x402)
Run it on Apify (https://apify.com/growth_wizard/datasource-pulse) Back to datasourcepulse.com

Datasource Pulse

The heartbeat monitor for your data supply chain.

Datasource Pulse monitors API credentials, usage quotas, and scraper output quality across your data pipeline. It knows when your SerpAPI quota runs out, when your GitHub PAT expires, and when the TikTok or LinkedIn Actor your pipeline depends on ships a changed output schema. Its maintainer’s decision, not yours. One alert when something degrades, one notice when it recovers. Runs on your schedule as an Apify Actor · $0.02 per check, billed per connector, no subscription.

Run it on Apify (https://apify.com/growth_wizard/datasource-pulse) Blog · For Agents · n8n · Zapier · Make llms.txt · llms-full.txt

© 2026 Datasource Pulse

Monitor after you adopt. Audit before you adopt with Audit Tools (https://audit-tools.ai) · independent, evidence-backed evaluation of Apify actors. From the maker of Demand Discovery AI (https://demanddiscovery.ai).

---

# Page: https://datasourcepulse.com/integrations/zapier

Datasource Pulse
The Problem How it Works Integrations Pricing Blog For Agents
Run it on Apify (https://apify.com/growth_wizard/datasource-pulse)

Integrations · Zapier

# API and scraper health alerts in Zapier

Two ways to wire Datasource Pulse into Zapier: run scheduled health checks through Apify’s official Zapier integration, or let Datasource Pulse push state-change alerts into a Zap the moment something breaks. Both use your existing accounts - no new integration to install.

## Path 1 · Instant alerts via webhook (recommended)

Datasource Pulse fires a JSON POST on every state transition - when a connector degrades and once when it recovers, not a message per run. Point that at a Zapier catch hook and every alert becomes a Zap trigger:

1. In Zapier, create a Zap with the Webhooks by Zapier trigger, event Catch Hook, and copy the hook URL.
2. In your Datasource Pulse input (wherever you run it - an Apify schedule works well), set:

{
"checks": [...your checks... ],
"webhookUrl": "https://hooks.zapier.com/hooks/catch/...",
"webhookFormat": "json",
"webhookSecret": "optional · adds X-DP-Signature for verification"
}
3. The hook receives top-level fields like transition, connector_label, failure_class, message, and recommended_action - map them straight into Slack, email, PagerDuty, a ticket, or any of Zapier’s apps. No polling, no filter step needed: only real transitions arrive.

## Path 2 · Scheduled checks inside a Zap

If you’d rather keep the schedule in Zapier: trigger with Schedule by Zapier, add the Apify app’s run-actor action for growth_wizard/datasource-pulse with the input below, fetch the run’s dataset items, then add a Filter step that only continues when state is not healthy:

{
"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": "credential",
"id": "feed-endpoint",
"label": "Data endpoint · reachable",
"vendor": "generic_http",
"url": "https://example.com/api/data",
"successStatusCode": 200
}
]
}
Each dataset item is one verdict with state, a stable failure_class enum (dead credential, rate limited, quota exhausted, schema drift, stale data, and more), and a plain-language message. Checks cost $0.02 each on your Apify account.

## Common questions

### Can Zapier tell me when an API key stops working?

Yes - Datasource Pulse validates keys against the live vendor APIs. 35+ vendors come pre-wired (OpenAI, Anthropic, Stripe, GitHub, SerpAPI and more), and any other endpoint takes one generic_http check, so the list is a head start, not a limit. Either path above turns an unhealthy verdict into any Zapier action you like.

### Which path should I pick?

The webhook path alerts only on change and saves Zap tasks; run the checks on an Apify schedule. Pick the scheduled path when you want everything visible in one Zap, or when the verdict should drive a multi-step workflow every run.

### How do I verify an alert really came from Datasource Pulse?

Set webhookSecret and every POST carries an X-DP-Signature HMAC header your receiver can check before acting.

Also available: n8n (with ready-made templates) · Make · agent access (MCP, API, x402)
Run it on Apify (https://apify.com/growth_wizard/datasource-pulse) Back to datasourcepulse.com

Datasource Pulse

The heartbeat monitor for your data supply chain.

Datasource Pulse monitors API credentials, usage quotas, and scraper output quality across your data pipeline. It knows when your SerpAPI quota runs out, when your GitHub PAT expires, and when the TikTok or LinkedIn Actor your pipeline depends on ships a changed output schema. Its maintainer’s decision, not yours. One alert when something degrades, one notice when it recovers. Runs on your schedule as an Apify Actor · $0.02 per check, billed per connector, no subscription.

Run it on Apify (https://apify.com/growth_wizard/datasource-pulse) Blog · For Agents · n8n · Zapier · Make llms.txt · llms-full.txt

© 2026 Datasource Pulse

Monitor after you adopt. Audit before you adopt with Audit Tools (https://audit-tools.ai) · independent, evidence-backed evaluation of Apify actors. From the maker of Demand Discovery AI (https://demanddiscovery.ai).

---

# Page: https://datasourcepulse.com/integrations/make

Datasource Pulse
The Problem How it Works Integrations Pricing Blog For Agents
Run it on Apify (https://apify.com/growth_wizard/datasource-pulse)

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

### Can Make monitor scrapers that fail silently?

Yes. An actor check baselines recent runs and flags volume drops, cost spikes, and staleness - the cases where a scraper still finishes green but returns thin or stale data. Works for your own actors and public actors you depend on.

### Quota warnings before a hard stop?

Set quotaSoftCap on a credential check - your own budget line in the vendor’s native unit - and you get a warning when usage crosses 80% of it (configurable), with the vendor-account percentage shown alongside.

### What does it cost?

$0.02 per check per run through your Apify account, pay-per-event. A daily two-check scenario is about $1.22/month.

Also available: n8n (with ready-made templates) · Zapier · agent access (MCP, API, x402)
Run it on Apify (https://apify.com/growth_wizard/datasource-pulse) Back to datasourcepulse.com

Datasource Pulse

The heartbeat monitor for your data supply chain.

Datasource Pulse monitors API credentials, usage quotas, and scraper output quality across your data pipeline. It knows when your SerpAPI quota runs out, when your GitHub PAT expires, and when the TikTok or LinkedIn Actor your pipeline depends on ships a changed output schema. Its maintainer’s decision, not yours. One alert when something degrades, one notice when it recovers. Runs on your schedule as an Apify Actor · $0.02 per check, billed per connector, no subscription.

Run it on Apify (https://apify.com/growth_wizard/datasource-pulse) Blog · For Agents · n8n · Zapier · Make llms.txt · llms-full.txt

© 2026 Datasource Pulse

Monitor after you adopt. Audit before you adopt with Audit Tools (https://audit-tools.ai) · independent, evidence-backed evaluation of Apify actors. From the maker of Demand Discovery AI (https://demanddiscovery.ai).

---

- Index for LLMs: https://datasourcepulse.com/llms.txt
- Crawl policy: https://datasourcepulse.com/robots.txt · Sitemap: https://datasourcepulse.com/sitemap.xml