How to import an n8n workflow
Every Kitvert download includes one or more workflow files in its n8n/ folder. Importing takes a couple of minutes. Most of the work is adding your credentials and testing.
Before you start
- Open the kit's
README.mdand keep it next to n8n - Have your keys ready: checkout platform, Notion integration token, email sender (SMTP or Gmail)
- Create the Notion database first, so you can pick it in the Notion node
On n8n Cloud
- Open your workspace and create a new, empty workflow.
- Open the menu (top right), choose Import from File and select the JSON from the kit's
n8n/folder. - Open each node that shows a warning and create or select the credential it needs.
- In each Notion node, pick your database and map the properties (see Notion setup).
- Click Execute workflow and send a test event: a test purchase, a test email or a test form submission.
- When the test row appears in Notion, switch the workflow to Active.
On self-hosted n8n
- Import the file the same way.
- Check that
WEBHOOK_URLis set to your public URL, so the webhook node shows an address the internet can reach. - Paste the production webhook URL (not the test one) into Lemon Squeezy, Gumroad or your form tool.
- Test, then activate.
Test and production webhook URLs
n8n gives each webhook two URLs. The test URL only listens while you have the editor open and have clicked Execute. The production URL works once the workflow is active. Use the test URL while mapping fields, then swap in the production URL before going live.
Questions
Why does my imported workflow show red credential warnings?
Credentials are never included in exported JSON, for security. Open each node with a warning, choose Create New Credential, and paste your own key.
The webhook never fires. What's wrong?
Usually one of three things: the workflow isn't activated, you pasted the test URL instead of the production URL into your checkout platform, or (self-hosted) the URL isn't reachable from the internet.
Can I import into an older n8n version?
Often yes, but nodes newer than your version will show as unknown. Update n8n, or replace the unknown node with its older equivalent.
Updated