Documentation
Everything you need to get from purchase to running workflow. Life's too short for copy-pasting setup instructions from random forums.
Getting Started
Prerequisites
Before you can use a bottysplur workflow, you'll need:
-
✓
An n8n instance
Self-hosted or n8n Cloud. Version 1.0+ recommended.
-
✓
A GitHub account
Used to receive your repository invitation. Free account works fine.
-
✓
Required services (varies by workflow)
Each workflow README specifies what accounts/services are needed. Common ones: PostgreSQL, Telegram Bot, API keys.
After Purchase: Getting Access
Complete your Gumroad purchase
Enter your GitHub username during checkout. Double-check spelling—this is how we find you.
Check your email
Within 5 minutes, you'll receive a GitHub invitation to the private repository. Check spam if it doesn't appear.
Accept the invitation
Click the link in the email or go to github.com/notifications to accept.
Access your workflows
Once accepted, you'll have full access to the repository containing your workflow files and documentation.
Importing Workflows
Step 1: Download the JSON file
Navigate to the repository and find the workflow JSON file. Usually in the root directory or a /workflows folder.
-
→
Click on the
.jsonfile - → Click the "Raw" button or download icon
- → Save the file to your computer
Step 2: Import into n8n
Option A: Import from File
- 1. In n8n, go to Workflows in the left sidebar
- 2. Click Add Workflow (or the + button)
- 3. Click Import from File
- 4. Select the downloaded JSON file
Option B: Copy/Paste JSON
- 1. Open the JSON file in GitHub and copy all contents
- 2. In n8n, create a new workflow
- 3. Press Ctrl+V / Cmd+V to paste
Step 3: Configure Credentials
After importing, you'll see nodes with red warning indicators. These need credentials configured.
- → Click on each red node
- → Under "Credential to connect with", click "Create New"
- → Enter your API keys, tokens, or connection details
- → Save the credential
Check the workflow README for specific credentials required and how to obtain them.
Step 4: Test the Workflow
Always test in development first. Click "Execute Workflow" to run a test. Check the output of each node to verify data flows correctly before enabling the schedule or production triggers.
Getting Updates
When I improve a workflow or fix bugs, the updates appear in your GitHub repository. No re-purchase needed.
How to update your workflow
-
1.
Check the CHANGELOG
Review what changed. Look for "BREAKING" if anything requires action on your end.
-
2.
Download the updated JSON
Pull the latest version from the repository.
-
3.
Import as a new workflow (recommended)
Keep your old version as backup. Migrate credentials and configurations to the new one.
-
4.
Test before going live
Verify everything works before deactivating the old workflow.
Pro tip: Watch the repository
Click "Watch" on the GitHub repository and select "Releases only" to get notified when new versions are published.
Troubleshooting
GitHub invite not received
- → Check spam/junk folder
- → Wait 5-10 minutes (automation isn't instant)
- → Check github.com/notifications for pending invitations
- → Verify you entered the correct GitHub username at checkout
- → Still nothing? Contact support with your order number
Import errors in n8n
- → Unknown node type: Your n8n version may be outdated. Check the workflow README for minimum version.
- → Invalid JSON: Make sure you downloaded the raw file, not the HTML page. Use the "Raw" button.
- → File too large: Some workflows are complex. Try import from file instead of copy/paste.
Credential errors after import
- → Credentials don't transfer between n8n instances—you need to create new ones
- → Each red node needs its credential configured individually
- → Check the workflow README for specific API key requirements
Workflow runs but produces no output
- → Check each node's output—look for where data stops flowing
- → Verify webhook URLs are correctly configured if applicable
- → Check database connections are active and accessible
- → Review environment variables if the workflow uses them
Still stuck? Contact support with your order number, a description of the issue, and any error messages you're seeing.