n8n Import

A workflow that already works is worth more than a workflow you have to describe from scratch. The trouble is who it belongs to. It runs on one person's n8n instance, or it is a marketplace template nobody on your team has time to wire up. n8n Import is how that workflow becomes something the whole team runs.

Start with the workflow itself. Paste an n8n marketplace URL (like https://n8n.io/workflows/1234), upload the JSON you exported from your own n8n, or paste the JSON directly. Runwork pulls the workflow apart into what it actually does: the trigger, the steps in order, and every service it touches along the way.

Then your own agent does the work, in whatever tool that person already uses. It reads your workspace first, so it knows which of your integrations are connected and builds against those. If the template sends mail through Mailchimp and your team runs SendGrid, it uses SendGrid, and nobody re-authorizes anything. If a step has no equivalent in your workspace, it tells you what it found and asks what you want to use instead.

What you end up with is a running thing, not a diagram. The logic lands as workflows and automations, the triggers become schedules that run in your team cloud, and when it helps, your agent puts an app around it so the person who needs the output presses a button instead of reading nodes.

From there it belongs to the team. It has an address people can find, roles decide who runs it and who can change it, every change is a version you can roll back, and it keeps running whether or not the person who imported it is at their desk. There is no instance to host and nothing to patch.

Changes later go the same way as the import. You ask your agent for the extra step, it ships a new version, and the whole team has it. Nobody drags a node.