Co-editing, Atlas drafts, and n8n import

Live co-editing

Several people in the project can edit the same workflow at once. Their avatars show in the top bar, and you see their changes as they make them. There is no lock and no "someone else is editing" wall.

Anyone in the project can view a workflow and its executions. Editors can change, test, and run it. Publishing a workflow that launches ads or sends email needs an admin.

Atlas drafts, you approve

You can ask Atlas in chat to build a workflow, or to change one. Describe the job the way you would brief a teammate: "Every Monday, make five static ads for the spring sale and schedule them on Instagram for the week."

Atlas drafts it. You see the draft on the canvas, check each node, and test it like any other draft. Atlas never publishes a workflow, turns on its triggers, or runs it without your approval. Going live is always your call.

Import from n8n

If you already have workflows in n8n, bring them in. Open a workflow, then from the menu in the top bar choose Import from file or Import from URL and pick an n8n JSON file.

Core n8n nodes map to their Pinnora versions. That includes Manual trigger, Schedule, Webhook, If, Switch, Merge, Set, Wait, HTTP request, Code, and Loop over items. A node Pinnora does not have comes in as a switched-off placeholder that keeps its original settings, so you can see what it did and replace it.

Export to n8n

Download from the workflow menu saves the workflow as n8n-compatible JSON. Connections are saved as references, never as passwords or keys. You can also copy a set of nodes and paste them into another workflow.

Reuse a workflow inside another

The Execute workflow node lets one workflow call another in the same project. Build a step once, such as "write a caption and post it", start it with When executed by another workflow, and call it from as many workflows as you like.