MCP Output Router — Send Any Dataset to Your Own Apps
Write a dataset into Notion, Slack, Supabase, a CRM or anything else you have connected as an Apify MCP connector. Your credentials never touch the Actor: the platform injects them server-side. Dry run by default, and every row reports whether the destination accepted it.
MCP Output Router — Send Any Dataset to Your Own Apps returns 5 documented output fields, including tool, reason, unmapped, args and status. Every field carries a declared type, a written description and an example value. 2 runs are recorded on Apify.
- 5
- Output fields
- 7
- Inputs
- 2
- Runs
- 2026-10-15
- Last run
01 — output
What it returns
Every field the extractor writes to its dataset, with its type, a written description and an example value.
| Field | Type | What it holds | Example |
|---|---|---|---|
| tool | string | number | boolean | array | objectnull | Tool as recorded for this row. | [] |
| reason | string | number | boolean | array | objectnull | Why this row carries its status. | matched |
| unmapped | arraynull | Unmapped as recorded for this row. | [] |
| args | string | number | boolean | array | objectnull | Args as recorded for this row. | [] |
| status | string | number | boolean | array | objectnull | Outcome recorded for this row. | ok |
02 — sample
One record
Assembled from the example values declared on the schema above, not invented at render time.
{
"tool": "[]",
"reason": "matched",
"unmapped": [],
"args": "[]",
"status": "ok"
}03 — input
What you give it
| Input | Type | Description |
|---|---|---|
| connector | stringoptional | The app to write to. Authorise it once in Settings → API & Integrations, then pick it here. The Actor never sees your credentials — the platform injects them server-side. |
| datasetId | stringoptional | The dataset id from a previous run (its defaultDatasetId). Leave empty to use 'items' below instead. |
| items | arrayoptional | Rows supplied directly, one object per row. Used only when 'datasetId' is empty. |
| toolName | stringoptional | Leave empty and the Actor picks the only tool that looks like a write action, and tells you which it chose. Name one to be exact — a name that does not exist is refused rather than substituted. |
| fieldMap | stringoptional | JSON mapping from the tool's argument names to your row's field names, e.g. {"title":"name"}. Leave empty and row fields whose names the tool already declares are passed through unchanged. |
| maxItems | integeroptional | Hard limit on tool calls. The best rows first when it bites. |
| dryRun | booleanoptional | ON by default. Reports the tools the connector offers, which one would be called, and the exact arguments for the first row. Turn it off deliberately when the plan looks right. |
04 — run
Run MCP Output Router on your own input
It runs in the cloud on Apify. Nothing to install, and you are billed per result returned rather than per attempt.
05 — questions
Asked before running it
5 of 5 fields described
- What does MCP Output Router — Send Any Dataset to Your Own Apps return?
- It returns 5 documented output fields: tool, reason, unmapped, args and status. Each field declares its type, a description of what it holds, and an example value.
- What input does MCP Output Router — Send Any Dataset to Your Own Apps take?
- All 7 inputs are optional and ship with usable defaults, so it runs as-is. They are listed with their types below.
- Does MCP Output Router — Send Any Dataset to Your Own Apps need an API key or login?
- No. None of its inputs is a credential, and it reads only public data. Nothing to sign up for before the first run.
- How do I run MCP Output Router — Send Any Dataset to Your Own Apps?
- It runs on Apify. Start it from its listing with the inputs above, or call the Apify API with the Actor's ID. Results land in a dataset you can export as JSON, CSV or Excel, or read through the Apify API into your own pipeline.