n8n integration
Install the Monocrawl community node to call any endpoint from an n8n workflow, or import a manual workflow that makes one bounded retrieval through MCP.
Install the Monocrawl node
- In n8n, open Settings, then Community nodes, and choose Install. Enter n8n-nodes-monocrawl, confirm and install. Self-hosted n8n can install it now; on n8n Cloud it appears in the nodes panel once n8n completes its verification review.
- Add a Monocrawl API credential and paste an API key from your dashboard. Keys start with mn_. Testing the credential reads your credit balance, which is free.
- Add the Monocrawl node to a workflow and choose Get Data. Pick a Platform and an Endpoint; each endpoint shows its credit price, and the lists load from the live catalogue, so new endpoints appear without updating the node.
- Fill in the Parameters for that endpoint. Simplify, on by default, returns one n8n item per record; turn it off to read credits_used, request_id and the next-page cursor. Dry Run returns a free estimate instead of fetching data.
The node also works as a tool for n8n’s AI Agent: map its parameters with $fromAI() and the agent fills them in.
Or import the MCP workflow
- Import the JSON into n8n. It contains a Manual Trigger and no schedule.
- Create a Header Auth credential named x-api-key, with your Monocrawl API key as its value. Select it on the paid retrieval HTTP Request node; never paste a key into the workflow JSON.
- Use a dedicated key with a cumulative cap. The workflow permits one TikTok profile request up to one credit; edit the subject in Prepare retrieval only after reviewing the endpoint.
- Run Inspect endpoint first. Review parameters, current cost and availability. The preparation node refuses unavailable or more expensive operations. Execute the full workflow when you want that retrieval.
Read the MCP and HTTP outcomes
The HTTP Request nodes POST JSON-RPC to /mcp. The final Code node reads result.structuredContent and checks both isError and success. It returns the full envelope so you can preserve data, request_id, credits_used and warnings in the destination of your choice.
The nodes include response headers and status, so the JSON-RPC response is under $json.body. Never Error allows an HTTP error body to reach the explicit result check; connection failures still stop the workflow. Adding an IF node later should branch on the parsed envelope, not merely the HTTP 200 status.
Control retries and larger runs
Automatic retry is disabled. Prepare retrieval assigns an idempotency key from the n8n execution ID. A new execution has a new key: do not start a replacement execution after an uncertain result. Recover the original key and arguments from execution history first. Ensure n8n’s execution-history access and retention match your data policy.
For many inputs, add an explicit item limit and sequential loop. Track confirmed charges and stop on pending accounting. Each page is another retrieval with its own quote and key. Do not enable automatic pagination until the chosen endpoint’s continuation contract has been checked.