Quora Space Activity & Content Change Monitor: MCP config, n8n workflow and API

{
  "spaceUrls": [
    "https://cryptocurrency.quora.com/"
  ],
  "includeMetadata": true,
  "includeFeed": true,
  "scrapeDepth": "overview",
  "includeContributors": false,
  "maxFeedQuestionExpansions": 0,
  "includeFeedText": true,
  "includeMedia": false,
  "includeOutboundLinks": false,
  "includeRules": true,
  "includeTopics": true,
  "includeSettings": false,
  "onlyNewItems": false,
  "includeUnchanged": true,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  },
  "includeFieldEvidence": true,
  "maxItemsPerSource": 0
}

---
name: quora-space-activity-and-content-change-monitor
description: "Quora Space metadata, feed, contributor and content-change rows with run diagnostics. Runs the Apify Actor nimbryxo-studio/quora-space-activity-and-content-change-monitor. Use when the user needs Quora data with fields such as content_type, parser_strategy, parser_version, field_sources, fields_present, final_url and an Apify token is available."
compatibility: "Needs network access, curl, and an APIFY_TOKEN environment variable. Runs are billed to the token owner's Apify account."
metadata:
  actor: "nimbryxo-studio/quora-space-activity-and-content-change-monitor"
  store-url: "https://apify.com/nimbryxo-studio/quora-space-activity-and-content-change-monitor"
---

# Quora Space Activity & Content Change Monitor

Use this skill to fetch Quora data with the Apify Actor `nimbryxo-studio/quora-space-activity-and-content-change-monitor` and work with the returned rows.

## Before running

1. Check that `APIFY_TOKEN` is set in the environment. Never print it or write it to a file.
2. Build `input.json` from the user's request using the fields below. Keep limits small for a first run.
3. Confirm the search terms or URLs with the user if the request is ambiguous.

## Input fields

| Field | Type | Meaning |
| --- | --- | --- |
| `spaceUrls` | array | Direct /q/ Space routes or Space subdomain URLs. |
| `includeMetadata` | boolean | Emit one Space metadata row per successfully observed Space. |
| `includeFeed` | boolean | Emit bounded visible feed item rows. |
| `scrapeDepth` | one of `overview`, `detail` | Overview captures metadata/status only and disables feed, contributor, scroll, and load-more work. Detail preserves bounded monitoring traversal; it is not complete history. |
| `includeContributors` | boolean | Emit only contributors found inside explicitly labeled role regions. |
| `maxFeedQuestionExpansions` | integer | When Scrape Depth is detail, bounded number of question-type feed items to open and expand into full question fields (question_id, question_answer_count, question_view_count, question_details, question_created_at, question_updated_at). |
| `includeFeedText` | boolean | Include visible feed text evidence. |
| `includeMedia` | boolean | Include visible media URLs when present. |
| `includeOutboundLinks` | boolean | Include bounded outbound links from feed cards. |
| `includeRules` | boolean | Include explicitly headed rules or guidelines text. |
| `includeTopics` | boolean | Include visible topic links. |
| `includeSettings` | boolean | Opt in to explicitly labeled public/authorized Space settings and content-permission evidence; missing settings remain not_observed and admin-only submission queues are never scraped. |
| `onlyNewItems` | boolean | Suppress unchanged state events when configured with a state store. |
| `includeUnchanged` | boolean | Keep unchanged event rows when onlyNewItems is enabled. |

Example `input.json` (the Actor's published prefill):

```json
{
  "spaceUrls": [
    "https://cryptocurrency.quora.com/"
  ],
  "includeMetadata": true,
  "includeFeed": true,
  "scrapeDepth": "overview",
  "includeContributors": false,
  "maxFeedQuestionExpansions": 0,
  "includeFeedText": true,
  "includeMedia": false,
  "includeOutboundLinks": false,
  "includeRules": true,
  "includeTopics": true,
  "includeSettings": false,
  "onlyNewItems": false,
  "includeUnchanged": true,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  },
  "includeFieldEvidence": true,
  "maxItemsPerSource": 0
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/nimbryxo-studio~quora-space-activity-and-content-change-monitor/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d @input.json > results.json
```

The call waits for the run to finish and returns the dataset items as a JSON array. If the run needs more than 300 seconds the API answers with HTTP 408; then start the run with `POST /v2/acts/nimbryxo-studio~quora-space-activity-and-content-change-monitor/runs`, poll `GET /v2/actor-runs/{runId}` until `SUCCEEDED`, and read `GET /v2/datasets/{defaultDatasetId}/items`.

## Output

Each item is one record. Published fields include: `content_type`, `parser_strategy`, `parser_version`, `field_sources`, `fields_present`, `final_url`, `http_status`, `error`, `scrape_duration_ms`, `navigation_attempts`, `navigation_retries`, `proxy_resolution_state`, `session_input_state`, `browser_locale`, `navigation_retry_delays_seconds`, `records_emitted`, `input_accounting`, `session_cookie_count`, `session_cookie_expiry_state`, `run_duration_ms`.

Summarise what was found, cite the record URLs when present, and say how many items came back. Do not invent values for empty fields.