# n8n Migration Metadata Preflight — Preview (`salim-operator-labs/my-actor`) Actor Preview for n8n workflow migrations: compare sanitized credential references and node versions against your target inventory. Flag missing IDs, ambiguous aliases and unlisted versions. No live n8n access or automatic mapping. Synthetic metadata only during preview. - **URL**: https://apify.com/salim-operator-labs/my-actor.md - **Developed by:** [Operator Labs](https://apify.com/salim-operator-labs) (community) - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing Pay per usage This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-usage ## What's an Apify Actor? Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Actors are written with capital "A". ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. The best way to integrate Actors is as follows. - **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use). - **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`. - **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`. - **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`. - **Any other language** — the [REST API](https://docs.apify.com/api/v2.md). For usage examples, see the [API](#api) section below. For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt). # README ## n8n Migration Metadata Preflight — Preview Compare workflow dependencies before a migration or handover. This independent tool checks sanitized credential references and node versions against an explicit target inventory. It is not affiliated with n8n. ### Preview scope and price Use synthetic metadata only during this preview. No creator event fee is charged. Apify platform usage is billed to the running user under their plan; this is not a promise of a zero-cost run. Suggested run settings: 128–1024 MB, timeout 60 seconds, maximum run cost $0.02. No live instance connection, automatic remapping or migration is performed. A paid release is planned at $0.25 per completed report after billing, support and payout checks. That price is a proposal, not an active checkout or a promise that this preview will remain available unchanged. ### Try the synthetic example Paste this in the JSON input editor: ```json {"nodes":[{"name":"Fetch","type":"example.fetch","typeVersion":1,"credentials":{"exampleApi":{"id":"source-id","name":"service-alias"}}}],"targetCredentials":[{"id":"target-id","name":"service-alias","type":"exampleApi"}],"targetNodeTypes":[{"type":"example.fetch","supportedVersions":[1,2]}]} ``` The result identifies target-id as a candidate requiring explicit confirmation, not an automatic fix. Change the target ID to source-id to see an exact ID/type match. Add a second same-name/type target credential to see ambiguity. Remove the target type to see node\_type\_not\_listed. ### What the report tells you - Credential ID/type matches, missing references and ambiguous aliases. - Node types and versions absent from the inventory you supplied. - Candidate target IDs for your own mapping review. The default dataset contains one result per source node. The run key-value store OUTPUT contains the full assessment. A successful platform run can still contain a rejected input report: check OUTPUT.status and the dataset, not just the green run badge. The current preview wrapper retains mode=private\_validation\_no\_billing; this is a development label, not a privacy guarantee. ### Limits and data Maximum 100 nodes, 100 target credentials and 100 node types; total input 1 MiB. Every node needs name, type, typeVersion and credentials (use {} if none). Credential references require id and name. Target credentials require id, name and type. Target node types require type and supportedVersions. Unknown fields are rejected, including parameters, pinData and connections. Do not upload raw workflow exports, execution data, personal information, tokens, passwords or credentials. Names and IDs can themselves contain secrets; a field allowlist cannot detect that. Apify stores run input, output and logs under its storage and retention settings. Do not assume this tool immediately deletes them. Use only invented sample values in the preview. The tool cannot verify inventory completeness, credentials, authentication, project permissions or runtime compatibility. An unlisted item means absent from your supplied inventory, not necessarily absent from the real instance. It does not alter inputs, apply mappings or contact n8n. ### Feedback and support Use this Actor’s Issues tab for a synthetic reproduction and expected/observed result. Never post secrets or real workflow exports. Operator Labs is operated with AI assistance. There is no guaranteed support response time during the preview. Refund handling for a future paid version is still being verified; no paid report orders are accepted now. ### Validation 16 local tests pass. Two private cloud tests verified an expected candidate result and rejection of an extra parameters field. These are development tests, not customer sales or evidence of production compatibility. # Actor input Schema ## `nodes` (type: `array`): Preview: invented values only. Only name, type, typeVersion and credential references; no parameters or secrets. ## `targetCredentials` (type: `array`): Preview: invented values only. Sanitized IDs, aliases and types only. ## `targetNodeTypes` (type: `array`): Preview: invented values only. Explicit type and supportedVersions; completeness not verified. ## Actor input object example ```json { "nodes": [ { "name": "Fetch", "type": "example.fetch", "typeVersion": 1, "credentials": { "exampleApi": { "id": "source-id", "name": "service-alias" } } } ], "targetCredentials": [ { "id": "target-id", "name": "service-alias", "type": "exampleApi" } ], "targetNodeTypes": [ { "type": "example.fetch", "supportedVersions": [ 1, 2 ] } ] } ``` # Actor output Schema ## `results` (type: `string`): No description # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "nodes": [ { "name": "Fetch", "type": "example.fetch", "typeVersion": 1, "credentials": { "exampleApi": { "id": "source-id", "name": "service-alias" } } } ], "targetCredentials": [ { "id": "target-id", "name": "service-alias", "type": "exampleApi" } ], "targetNodeTypes": [ { "type": "example.fetch", "supportedVersions": [ 1, 2 ] } ] }; // Run the Actor and wait for it to finish const run = await client.actor("salim-operator-labs/my-actor").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "nodes": [{ "name": "Fetch", "type": "example.fetch", "typeVersion": 1, "credentials": { "exampleApi": { "id": "source-id", "name": "service-alias", } }, }], "targetCredentials": [{ "id": "target-id", "name": "service-alias", "type": "exampleApi", }], "targetNodeTypes": [{ "type": "example.fetch", "supportedVersions": [ 1, 2, ], }], } # Run the Actor and wait for it to finish run = client.actor("salim-operator-labs/my-actor").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "nodes": [ { "name": "Fetch", "type": "example.fetch", "typeVersion": 1, "credentials": { "exampleApi": { "id": "source-id", "name": "service-alias" } } } ], "targetCredentials": [ { "id": "target-id", "name": "service-alias", "type": "exampleApi" } ], "targetNodeTypes": [ { "type": "example.fetch", "supportedVersions": [ 1, 2 ] } ] }' | apify call salim-operator-labs/my-actor --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,salim-operator-labs/my-actor" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/wORZDeFv66yhlPyh0/builds/Iit0oizg4vyTspQIc/openapi.json