← All guides
n8n By Editorial · Skillaisle ([email protected]) · Published Oct 18, 2026 · Steps checked against official docs on Oct 18, 2026

How to import and configure an n8n workflow from JSON

Import a workflow JSON file into n8n, connect your own credentials, test it, and publish it so schedules and webhooks run in production.

n8n stores workflows as JSON, so a workflow someone shares with you is usually a single .json file. These steps work the same on n8n Cloud and on a self-hosted instance.

Before you import: check the file

Exported workflow JSON includes credential names and IDs. The IDs aren’t secret, but the names might reveal something. HTTP Request nodes created from a cURL command can also contain authentication headers. Open the file in a text editor and look for anything like that before you import a stranger’s workflow or share your own. Skillaisle flow files are stripped of credentials, credential IDs and webhook URLs before we publish them.

Step 1: Import the JSON

Pick whichever is easiest:

  • From a file: open a new workflow, then open the Workflow menu in the canvas header and choose Import from File….
  • From a URL: in the same menu, choose Import from URL and paste a link to the raw JSON file.
  • Copy and paste: copy the JSON text and paste it into the editor with Ctrl + V (Cmd + V on a Mac).

For moving workflows between instances from the command line, n8n recommends its n8n CLI and package format, which is in preview. The older server CLI import commands still work but are planned for deprecation.

Step 2: Connect your credentials

Imported nodes that talk to other services need your own credentials:

  1. Open each node that shows a warning.
  2. In its credential dropdown, pick an existing credential or create a new one. You can also create credentials first from the Create button in the side menu by choosing Credential.
  3. Enter the details the service asks for. When you save, n8n tests the credential to confirm it works.

Give credentials names that say which app, type and purpose they are for. On credentials for web APIs, the Allowed HTTP Request Domains field limits which domains the credential can be sent to from an HTTP Request node. Set it to specific domains if you can.

Step 3: Change the settings to your own

Go through each node and replace anything that belongs to the original author: URLs, spreadsheet IDs, email recipients, schedule times, channel names. Sticky notes in a workflow often say what to change.

Step 4: Test it

Click Execute workflow to run it once manually and check the output of each node. Fix any node that fails before you go further.

Step 5: Publish it

n8n saves your edits automatically, but they stay a draft until you publish. Click Publish in the canvas header (or press Shift + P), optionally name the version, then click Publish in the dialog. Publishing makes the workflow live:

  • Schedules run at the times you set.
  • Webhook and form triggers switch to their production URLs.
  • Events from connected apps trigger the workflow.

Publishing happens in the background, and the button shows Publishing until n8n confirms it. If a trigger fails to activate, for example because a connected app was unavailable, the button reports a partial or failed publish; hover over it to see which trigger failed, then publish again to retry. Later edits don’t go live until you publish again.

Try it with a free flow

Our Weekly Uptime Check flow needs no credentials, so it’s a quick way to practise: import it, change the URL in the Fetch page node, run it once, then publish.

Sources

Products change. If a step no longer matches what you see, the official page above is the reference.

Related on Skillaisle