Import from n8n or Plain

What can I import into NodeHub?

You can inspect an n8n workflow export and save its supported steps as an unpublished NodeHub workflow draft. Plain imports read supported customer conversations and timeline data into a preview for review before applying a batch. A Plain import does not convert workflows, and an n8n import does not migrate your support inbox.

Open Workflows and choose the import option. Select Plain or n8n as the source and confirm your workspace and brand before continuing. A workspace owner or administrator manages Plain data imports.

How do I import an n8n workflow?

1. Export the workflow as JSON from n8n. Keep an unchanged copy so you can compare its branches, field mappings and behavior with the imported draft.
2. Upload it to the n8n import preview. Review the steps, connections and warnings. Supported configurations are translated; unsupported steps and expressions remain blocked for explicit configuration or replacement.
3. Save the disabled draft. The import does not turn on its schedule, webhook or other automatic trigger.
4. Reconnect each required account. Use NodeHub connection setup, verify the account, then select it on the intended step. Credentials are not imported as working accounts.
5. Resolve the reported problems. Check routing, HTTP authentication, field expressions, error handling and provider permissions. Follow the guidance beside each blocked step.
6. Test the actual draft and approve it. Inspect every relevant branch and its external result with controlled input. The current draft needs a successful test and human approval before publishing and activation. Changes to its behavior require review again.

Import support depends on the specific node and its configuration. Importing a graph does not establish feature parity with every n8n node or community package.

How do I import from Plain?

1. Select the Plain source. Use a key for the Plain workspace you intend to migrate, with the required workspace, thread and timeline read permissions.
2. Load a preview batch. Review the source workspace, mapped records, validation issues and counts. The key is used for that request and is not saved as a reusable NodeHub connection.
3. Apply the reviewed batch. Review the recorded job result before moving to the next batch. Follow the returned cursor and keep the same source workspace throughout the import.
4. Check the imported conversations. Inspect representative customer identities, thread history and messages in NodeHub. Configure and test your support channels separately before switching real inbound traffic.

A failed or incomplete source batch is refused before its history is applied. A preview is not proof that every record in Plain has been transferred. Use the import job results and remaining batches to verify progress.

What needs reconnecting or configuring?

Provider accounts, AI models and channel delivery need their own NodeHub setup. Use the connection catalog to check the supported actions and permissions for each service. Configure required inputs and choose the intended account on each workflow step.

Testing a write can change the connected service. Use test records you are authorized to change, inspect the provider result, and check whether a previous request completed before retrying it. Human approval before activation does not make a test run free of external effects.

How do I know the move is complete?

• Each expected import batch has a recorded result, and any skipped or rejected records have been reviewed.
• Representative conversations retain the expected customer identity and history.
• Required accounts and support channels pass their separate setup and delivery checks.
• Imported workflows pass representative tests, receive human approval and publish only after the team is ready.

Continue with the quickstart, connection guide or contact NodeHub when an import reports a gap you cannot resolve.