---
id: "9a24ff75-c519-402a-a825-5ae591325079"
name: "Slack Notification Fetching"
micro_summary: "Use `slack_get_notifications(view=\"all\", unread=False, limit=50)` to fetch Activity rows as JSON candidates with preliminary demotion/open-loop signals."
status: "resolved"
see_also: []
scope: "How to extract Slack Activity notifications from the logged-in app.slack.com web UI for triage without using Slack API tokens."
---
## Helper

Use `slack_get_notifications(view="all", unread=False, limit=50)`.

```python
import json
payload = json.loads(slack_get_notifications(view="all", limit=10))
```

## Parameters

- `view`: `"all"`, `"dms"`, `"mentions"`, or `"threads"`.
- `unread`: when true, requests Slack's Unreads filter before extraction.
- `limit`: maximum Activity rows to return.

## Returns

JSON with `ok`, `view`, `count`, and `items`. Each item includes row text, inferred kind, sender/snippet/channel/reaction where visible, links where present, and a `signals` object with a preliminary surface/review/quiet tier.

## Usage stance

This is the first-pass candidate generator for ONEplace-style triage, not a feed. Feed rows into demotion/open-loop helpers before surfacing anything.

## Verification

2026-06-01: `slack_get_notifications(view="all", limit=3)` returned `ok=true`, `count=3`, with app/reaction/DM kinds from the real Activity inbox.