Apify Spend & Failure Monitor for n8n—Daily Threshold Alerts

Catch Apify spend spikes and failed runs before they become a problem

The Apify Spend & Failure Monitor for n8n—Daily Threshold Alerts workflow checks your Apify Actor run history on a daily schedule (or on demand), totals known USD spend, counts failed runs, and generates an attention report when your configured thresholds are exceeded.

What this workflow does

• Runs daily at 09:00 (or you can start it manually) to perform a monitoring check.
• Lets you set a lookback window (1–168 hours), a spend threshold (USD), and a failed-run threshold.
• Calculates the ISO timestamp for the lookback start and validates that thresholds are within safe limits.
• Calls the Apify API to retrieve up to 1,000 most recent Actor runs started after the calculated timestamp.
• Summarizes results by:
  • Summing known usageTotalUsd.
  • Counting run statuses FAILED, TIMED-OUT, and ABORTED.
  • Flagging attention when thresholds are exceeded or when cost data is missing.
• Outputs either a normal report or an attention report, which you can optionally format for Slack or email notifications.

Use cases

• Alert your team when Apify spend crosses a daily budget limit.
• Detect reliability issues by tracking increases in failed/timed-out/aborted Actor runs.
• Monitor cost visibility—raise attention when usageTotalUsd is missing for returned runs.
• Run ad-hoc checks during incident response or after configuration changes.

Technical details

• Integrates with Apify via an HTTP Request using your Apify API credential.
• Uses n8n nodes including: If, Set, Code, Sticky Note, HTTP Request, and Manual Trigger.
• Supports scheduled monitoring and optional downstream notification formatting for Slack or email.