My Actors Issues Notifier đź”” avatar

My Actors Issues Notifier đź””

Pricing

Pay per usage

Go to Apify Store
My Actors Issues Notifier đź””

My Actors Issues Notifier đź””

Up your Apify game 🔥 Get notified when users open/re-open issues on your Apify actors. This actor monitors your actors for new open/re-opened issues and automatically writes them to a JSON dataset, ready for external integrations (Telegram, Slack, Jira, n8n or custom webhooks..) - 100% Open Source

Pricing

Pay per usage

Rating

5.0

(1)

Developer

Azzouzana

Azzouzana

Maintained by Community

Actor stats

2

Bookmarked

1

Total users

1

Monthly active users

24 days ago

Last modified

Share

đź”” My Actors Issues Notifier

An Open Source actor that pulls your Apify Console for new open/reopened actor issues on your account and writes webhook-ready rows to the default dataset - connect Telegram, Slack, and more from Integrations.

How it works

  1. POST /public/authentication/resume — uses console ApifyRT cookie → short-lived uiToken
  2. Socket.IO subscribe to userOwnedPublicActorsIssuesPub (paginated)
  3. Keeps issues with status === "OPEN"
  4. Named KV store apify-console-open-issues:
    • firstRunComplete — false until the first successful poll finishes (To not detect already open issues while running this for the first time)
    • seenIssueIds — currently open issue IDs (closed IDs are removed each run)
  5. First run (firstRunComplete unset): save open ids + set flag — no dataset push
  6. Later runs: for each new open id, GET /actor-issues/{issueId}/comments (last array entry) → dataset row (type: "new_open_issue"), then refresh seenIssueIds
  7. On resume/socket errors: one dataset row (type: "fetch_failure")

Dataset records

New issue (type: "new_open_issue"):

FieldTypeDescription
typestringAlways "new_open_issue"
notifiedAtstringISO timestamp when the record was pushed
issueIdstringIssue _id from Console
titlestringIssue title
statusstringIssue status (e.g. "OPEN")
objectTypestringe.g. "PAID_ACTOR"
objectIdstringLinked object id (often same as actor _id)
createdAtstringIssue creation time (ISO)
urlstringDirect link to the issue in Console
actorTitlestringActor display title (fallback: actor name or objectId)
reporterstringReporter display name or username
lastCommentstring | nullText of the last entry in /actor-issues/{issueId}/comments (HTML stripped)

Example dataset output:

[
{
"type": "new_open_issue",
"notifiedAt": "2026-06-02T10:33:00.204Z",
"issueId": "12345678910",
"title": "test an open issue",
"status": "OPEN",
"objectType": "PAID_ACTOR",
"objectId": "987654321",
"createdAt": "2026-06-02T10:26:17.375Z",
"url": "https://console.apify.com/actors/VzKtdb1t0Qnc07X8V/issues/12345678910",
"actorTitle": "SofaScore scraper PRO⚡",
"reporter": "dumy_username",
"lastComment": "This is an open issue with dummy run"
}
]

Failure (type: "fetch_failure"):

FieldDescription
stepe.g. authentication/resume, socket.io subscribe
errorMessageError detail
notifiedAtISO timestamp

Each new or failed notification is a row in this actor’s default dataset. Use that for integrations—no extra code required in this repo.

Configuration

Actor input

InputRequiredNotes
apifyRtYesApifyRT cookie from console.apify.com

Copy ApifyRT from DevTools → Application → Cookies → https://console.apify.com.

Create a scheduled task and set apifyRt in the task input so the actor runs on a interval (e.g. every 10–15 minutes).

Webhooks (Telegram, Slack, etc.)

Open the actor’s Integrations tab in Apify Console: https://console.apify.com/actors/u45C6wzQQgsbqaeie/integrations

There, you can connect your preferred communication app (Slack, Telegram, WhatsApp, etc.) or ticketing system (Jira, Trello, Linear, etc.) using either Apify's native integrations or custom webhooks.

  • Trigger on actor run succeeded
  • Point the integration at this actor’s default dataset and map fields such as title, actorTitle, reporter, and url etc in your custom message template.

📬 Contact & Support

Have feedback, a question, or just want to say hi? We'd love to hear from you!


Made with ❤️ for the data community.