How to Get Apify Actor Failure Alerts in Slack

Set up Slack alerts for Apify actor failures including customer PPE runs. Step-by-step guide to connecting Slack with ApifyForge Monitor for real-time failure notifications in your team channel.

By Ryan ClintonLast updated: March 2026

To get Apify actor failure alerts in Slack, connect your Slack workspace to ApifyForge Monitor and add Actor.addWebhook() to your actors. Every failure, timeout, and abort event from any user's run is then sent directly to your chosen Slack channel with the actor name, error message, run ID, and console link. Slack alerts are available on the Developer ($9/month) and Pro ($29/month) plans.

Why Slack for actor monitoring

Email alerts work, but Slack is where most development teams already spend their time. Slack alerts for actor failures give you:

  • Instant visibility without checking email or the Apify dashboard
  • Team-wide awareness — everyone in the channel sees the failure
  • Threaded discussion — diagnose the issue directly in the alert thread
  • Mobile notifications — get alerted on your phone when a critical actor fails
  • Searchable history — find past failures with Slack search

For solo developers, email may be enough. For teams managing a portfolio of PPE actors, Slack is the faster response channel.

Two approaches to Slack alerts

Direct Slack webhook (limited)

Apify supports static webhooks that can POST to a Slack incoming webhook URL. This is the simplest approach, but it has a significant limitation: static webhooks only fire for the actor owner's own runs. Customer-triggered PPE runs are not covered.

To set this up, create a Slack incoming webhook in your workspace, then add it as a static webhook in the Apify console for each actor. The alert format is raw JSON — not formatted for readability.

ApifyForge Monitor (all users)

ApifyForge Monitor catches failures from every user (including paying customers) and sends formatted alerts to your Slack channel. The alerts include the actor name, error message, run ID, and a direct link to the run in the Apify console.

The key difference: ApifyForge Monitor uses ad-hoc webhooks registered inside the actor code, which fire for all users. Direct Slack webhooks use static webhooks, which only fire for the owner.

Setting up Slack alerts with ApifyForge Monitor

Step 1: Sign up and add monitoring code

If you have not already, sign up at apifyforge.com/connect and add the webhook call to your actors:

await Actor.addWebhook({
  eventTypes: ['ACTOR.RUN.FAILED', 'ACTOR.RUN.TIMED_OUT', 'ACTOR.RUN.ABORTED'],
  requestUrl: 'https://apifyforge.com/api/webhooks/apify-failures',
});
typescript

Step 2: Connect Slack from your dashboard

Go to your ApifyForge dashboard and click "Add Slack workspace." Authorize ApifyForge Monitor to post to your chosen channel. You can select any public or private channel in your workspace.

Step 3: Choose your channel

Select the Slack channel where you want failure alerts to appear. Common patterns:

  • #apify-alerts — dedicated channel for all actor failure alerts
  • #actor-name-alerts — per-actor channels for high-volume actors
  • #engineering — existing team channel for general awareness

Step 4: Verify the connection

Trigger a test failure on one of your monitored actors (run with invalid input or a known failing URL). Verify the alert appears in your Slack channel within seconds.

What Slack alerts look like

ApifyForge Monitor sends formatted alerts to Slack with clear structure:

  • Header: The actor name and failure type (FAILED, TIMED_OUT, ABORTED)
  • Error message: The full error text or custom status message from Actor.setStatusMessage()
  • Run details: Run ID, duration, timestamp
  • Direct link: Click to open the failed run in the Apify console

On Developer plans, alerts also include the exit code with a diagnostic label (OOM, timeout, exception). On Pro plans, alerts include the triggering user ID.

Channel organization patterns

For developers managing multiple actors, organize your Slack alerts by category:

  • Single channel: Best for portfolios under 10 actors. All alerts in one place.
  • Per-category channels: Group actors by type (scrapers, enrichers, monitors). Example: #scraper-alerts, #enricher-alerts.
  • Per-actor channels: For high-revenue actors with many customers. Keeps alert noise contained.
  • Severity-based routing: (coming soon) Route TIMED_OUT to a low-priority channel and FAILED to a high-priority channel.

Pricing for Slack alerts

Slack integration is available on:

  • Developer plan ($9/month) — 25 monitored actors, email + Slack alerts, exit code diagnostics
  • Pro plan ($29/month) — unlimited actors, email + Slack alerts, user ID tracking, custom integrations

The Free plan ($0/month) includes email alerts only. Upgrade to Developer or Pro to add Slack.

For the full setup walkthrough, see the Setup Guide. To understand what exit codes mean in your Slack alerts, see Exit Codes Explained.

Last updated: March 2026

Frequently Asked Questions

Can I get Slack alerts for free?

Slack alerts require the Developer ($9/month) or Pro ($29/month) plan. The Free plan includes email alerts for up to 3 actors. You can start with email on the Free plan and upgrade to add Slack when you need it.

Can I send alerts to multiple Slack channels?

Currently, ApifyForge Monitor sends all alerts to a single configured Slack channel. Per-actor or per-category channel routing is on the roadmap. In the meantime, you can use Slack's workflow builder to route alerts from the main channel to sub-channels based on keywords.

What is the difference between Apify's direct Slack webhook and ApifyForge Monitor's Slack integration?

Apify's static webhooks send raw JSON to a Slack incoming webhook URL, but only for the actor owner's runs. ApifyForge Monitor sends formatted, readable alerts to your Slack channel for every user's runs, including paying customers. ApifyForge Monitor covers the PPE customer failure gap that static webhooks cannot.

Do Slack alerts include the same information as email alerts?

Yes. Slack alerts contain the same fields as email alerts: actor name, run status, error message, run ID, duration, and console link. On Developer and Pro plans, both channels also include exit code diagnostics. On Pro plans, both include the triggering user ID.

Start Monitoring Your Actors

ApifyForge Monitor is free for up to 3 actors. 1 line of code, zero Apify credits.

Get started free