Q: Getting started with your web hosting

## Alles zit in je dashboard Je hoeft geen apart bedieningspaneel te leren. Log in, klik je hostingdienst aan en klik op **Beheer**. Daar staat alles: je e-mailadressen, je databases, je bestanden, je DNS, je PHP-versie. ![Het beheermenu van je webhosting, met de groepen E-mail, Website, Databases, Bestanden en Domeinen, Beveiliging, en Backup en Herstel.](/images/docs/webhosting-toegang.svg) ## Het menu, groep voor groep | Groep | Wat erin staat | |---|---| | **E-mail** | E-mailaccounts, Doorstuurregels, Autoresponders, Catch-All, E-mail Filters | | **Website** | DNS Beheer, Redirects, Domein Pointers, Cron Jobs, PHP-versie | | **Databases** | MySQL Databases, phpMyAdmin | | **Bestanden & Domeinen** | Bestandsbeheer, FTP Accounts, Domeinen | | **Beveiliging** | SSL Certificaten, Spam Filter, Beveiligde Mappen, SSH Sleutels, Geblokkeerde IPs | | **Backup & Herstel** | Backups | ## De eerste drie dingen **1. Zet je website erop.** Via Bestandsbeheer in de browser, of met FTP als je vaker iets wijzigt. Zie *Je website erop zetten*. **2. Maak je e-mailadressen aan.** Onder E-mailaccounts. Zie *E-mail instellen*. **3. Controleer je DNS.** Wijzen de nameservers van je domein naar ons? Alleen dan doen de records die je hier invult iets. Zie *DNS beheren*. ## Waar je verder over leest - *Je website erop zetten* — bestandsbeheer, FTP en SSH - *E-mail instellen* — adressen, doorsturen, autoresponders en filters - *Databases aanmaken en beheren* - *PHP-versie kiezen* - *SSL en https* - *Back-ups maken en terugzetten* - *Wat er in je pakket zit* — de grenzen, en wat "onbeperkt" betekent ## Als je van een andere partij komt Wij verhuizen je website en e-mail kosteloos. Je hoeft niets te downloaden of te exporteren; laat weten waar je nu zit en wij nemen contact op. Het overzetten gebeurt vóórdat de DNS omgaat, zodat je site niet offline raakt.

Question 1

Installing n8n on your VPS — Complete Guide

Accepted Answer

## What is n8n?

n8n is a powerful open-source workflow automation platform — similar to Zapier or Make, but self-hosted on your own VPS. With 400+ native integrations, built-in AI capabilities, and a visual drag-and-drop editor, you have full control over your automations and your data.

![n8n Workflow Editor](/images/vps-apps/n8n-template/hero-workflow.png)

---

## System Requirements

| Component | Minimum | Recommended | Enterprise |
|-----------|---------|-------------|------------|
| RAM | 2 GB | 4 GB | 8 GB |
| CPU | 1 vCPU | 2 vCPU | 4 vCPU |
| Storage | 25 GB NVMe | 50 GB NVMe | 100 GB NVMe |
| OS | Ubuntu 24.04 | Ubuntu 24.04 | Ubuntu 24.04 |

---

## Step 1: Order VPS with n8n Template

The easiest way to install n8n is via our **1-click installation**:

1. Go to the [VPS Configurator](/en/configurator/vps)
2. Choose your desired package (minimum 2 GB RAM)
3. Select **n8n** as the application template
4. Complete your order

After payment, your VPS is automatically provisioned with the complete n8n stack.

---

## Step 2: What Gets Installed Automatically?

Our 1-click installation configures the following components:

- **Docker Engine** — Containerized deployment for reliability
- **PostgreSQL 16** — Professional database backend (more reliable than SQLite)
- **Caddy 2 Web Server** — Reverse proxy with automatic HTTPS via Let's Encrypt
- **n8n (latest)** — The latest version of n8n in a Docker container
- **Daily Backups** — Automatic backup every night at 03:00 (7 days retained)
- **Update Script** — Easy updates with a single command

All components are installed in `/opt/n8n/`.

---

## Step 3: First Access to n8n

Once the installation is complete:

1. Open your browser and go to `http://YOUR-VPS-IP`
2. n8n displays the registration screen
3. **The first user to register automatically becomes the owner/admin**
4. Fill in your name, email address, and password
5. You're now ready to build workflows!

> **Important:** Create your admin account as soon as possible after installation. Anyone with access to the IP address can otherwise claim the first account.

---

## Step 4: Connect Your Own Domain (Recommended)

For a professional setup with HTTPS:

### Set Up DNS
Create an **A record** at your domain provider:
```
n8n.yourdomain.com  →  A  →  YOUR-VPS-IP
```

### Configure Caddy
Connect via SSH to your VPS and edit the Caddyfile:
```bash
sudo nano /opt/n8n/Caddyfile
```

Replace the existing content with:
```
n8n.yourdomain.com {
    reverse_proxy n8n:5678
}
```

Restart Caddy:
```bash
cd /opt/n8n && docker compose restart caddy
```

Caddy automatically obtains a free SSL certificate via Let's Encrypt. After a few seconds, your n8n is accessible at `https://n8n.yourdomain.com`.

---

## Step 5: Updating n8n

To update n8n to the latest version:

```bash
sudo /opt/n8n/update.sh
```

This script:
- Downloads the latest n8n Docker image
- Restarts the containers automatically
- Cleans up old Docker images
- Your workflows and data remain fully preserved

---

## Step 6: Managing Backups

### Automatic Backups
Every night at 03:00, an automatic backup is made of:
- The PostgreSQL database
- The n8n configuration and data

Backups are stored in `/opt/n8n/backups/` (last 7 days).

### Manual Backup
You can also make a manual backup:
```bash
sudo /opt/n8n/backup.sh
```

### Restoring a Backup
To restore a backup:
```bash
# Stop n8n
cd /opt/n8n && docker compose down

# Restore the database
gunzip < /opt/n8n/backups/BACKUP-FILE.sql.gz | docker exec -i n8n-postgres psql -U n8n

# Start n8n again
docker compose up -d
```

---

## Directory Structure

The complete n8n installation is located in `/opt/n8n/`:

```
/opt/n8n/
├── docker-compose.yml    # Docker configuration
├── Caddyfile             # Web server configuration
├── .env                  # Environment variables
├── update.sh             # Update script
├── backup.sh             # Backup script
├── backups/              # Backup files
└── data/                 # n8n workflow data
```

---

## FAQ

**How many workflows can I run?**
Unlimited! There are no limits on the number of workflows or executions. The only limitation is your VPS capacity.

**Can I install n8n manually?**
Yes, but we recommend the 1-click installation. Manual installation requires Docker, PostgreSQL, and a reverse proxy — our template configures all of this automatically.

**What if I need more resources?**
You can upgrade your VPS at any time via your dashboard. RAM and CPU upgrades require a short reboot, storage can be expanded online.

**Does n8n run on Windows?**
Our VPS templates run on Ubuntu 24.04 (Linux). n8n itself runs in a Docker container, so the OS doesn't matter for n8n.

Question 2

Stream Monitor: monitoring your audio stream

Accepted Answer

## What is the Stream Monitor?

The Stream Monitor is a comprehensive monitoring tool that lets you track the health and availability of your audio streaming service in real time. The monitor checks your stream at regular intervals and automatically detects issues such as outages, silence, and quality degradation.

![Stream Monitor Dashboard](/images/help/stream-monitor-enterprise.png)

The Stream Monitor is available as an add-on to your audio streaming package and is offered in three subscription tiers: **Basic**, **Pro**, and **Enterprise**.

---

## Subscription Tiers

The Stream Monitor is available in three tiers, each with more features:

### Basic

- **Check interval:** every 5 minutes
- Online/offline status detection
- Uptime statistics (24 hours, 7 days, 30 days)
- Email notifications on outages
- Incident history

### Pro

All Basic features, plus:

- **Check interval:** every 1 minute
- **Silence detection** — detects when your stream is silent (configurable threshold)
- **Metadata monitoring** — tracks what's currently playing and detects stuck metadata
- Advanced incident types (silence, bitrate drop, stuck metadata)

### Enterprise

All Pro features, plus:

- **Check interval:** every 30 seconds
- **Multi-mount point monitoring** — monitor multiple mount points (e.g., main, mobile, fallback) simultaneously
- **Webhook notifications** — receive real-time notifications via webhook with HMAC-SHA256 signing
- **Maintenance windows** — schedule times when notifications are suppressed

---

## The Dashboard

After activation, you can find the Stream Monitor in your dashboard under **Services > [Your Streaming Service] > Manage > Stream Monitor**.

### Status Page

The main page shows an overview of your stream:

- **Current status** — Online, Offline, Silent, Degraded, or Error
- **Protocol** — Shoutcast or Icecast
- **Subscription tier** — Basic, Pro, or Enterprise
- **Last check** — time of the most recent check
- **Uptime percentages** — availability over 24 hours, 7 days, and 30 days

### Check History

A visual timeline shows the results of recent checks. Each check records:

- Status (online/offline/silent/degraded/error)
- Response time in milliseconds
- Bitrate (kbps)
- Audio level (dB)
- Current track (artist and title)
- Listener count
- AutoDJ status

### Active Incidents

When an issue is detected, an incident appears on the dashboard. Incidents include:

- **Type** — offline, silence, bitrate drop, stuck metadata, AutoDJ failover, high latency
- **Severity** — warning or critical
- **Start time** and duration
- **Description** of the issue

You can **acknowledge** incidents to indicate you're aware of them.

---

## Setting Up Notifications

### Email Notifications

By default, notifications are sent to your account email address. You can customize this:

1. Go to **Stream Monitor > Settings**
2. Enable **Notifications**
3. Enter a **Notification email address**
4. Set the **Cooldown period** (default: 15 minutes) — this prevents you from being flooded with notifications

### Webhook Notifications (Enterprise)

For advanced integrations, you can set up webhook notifications:

1. Go to **Stream Monitor > Settings**
2. Enter your **Webhook URL**
3. Webhooks are sent with an **HMAC-SHA256 signature** in the `X-Maenda-Signature` header

**Webhook payload example:**

```json
{
  "event": "incident.offline",
  "timestamp": "2025-02-25T12:00:00Z",
  "monitor": {
    "id": "mon_123",
    "serviceId": "svc_456",
    "streamUrl": "https://stream.example.nl:8000/live",
    "tier": "enterprise"
  },
  "incident": {
    "id": "inc_789",
    "type": "offline",
    "severity": "critical",
    "status": "active",
    "startedAt": "2026-02-25T12:00:00Z",
    "description": "Stream is unreachable"
  },
  "check": {
    "status": "offline",
    "responseTimeMs": 10000,
    "bitrate": null,
    "audioLevelDb": null,
    "isSilent": false,
    "nowPlaying": null
  }
}
```

**Webhook events:**
- `incident.{type}` — new incident detected (e.g. `incident.offline`, `incident.silence`)
- `incident.resolved.{type}` — incident resolved (e.g. `incident.resolved.offline`)

Every webhook also includes the headers `X-Maenda-Event` (the event name) and `X-Maenda-Signature` (the HMAC-SHA256 signature).

The webhook retries up to 3 times with increasing delay (1s, 5s, 15s) on failed delivery.

### Protection against false alerts

A brief hiccup isn't necessarily an outage. That's why the monitor only creates an offline incident after several consecutive failed checks (configurable). This prevents false alarms from a one-off spike, while a real outage is still reported quickly. The individual checks are always recorded, so your uptime figures stay accurate.

---

## Silence Detection (Pro & Enterprise)

Silence detection recognizes when your stream is technically online but not broadcasting audio. This is essential for radio streams where silence can be a serious issue.

### How It Works

The monitor analyzes 32KB of audio data from your stream and calculates:

- **Byte variance** — how varied the audio data is
- **Shannon entropy** — information content of the audio signal
- **dB level** — estimated sound level (RMS and peak)

Silence is detected when byte variance is below 50 AND entropy is below 5.0 bits.

### Adjusting Thresholds

1. Go to **Stream Monitor > Settings**
2. Adjust the **Silence threshold** (default: -50 dB)
3. Set the **Silence duration** (default: 30 seconds) — how long silence must last before an incident is created

---

## Multi-Mount Point Monitoring (Enterprise)

If your stream has multiple mount points (e.g., `/live`, `/mobile`, `/fallback`), you can monitor them all simultaneously.

### Setup

1. Go to **Stream Monitor > Settings**
2. Add your **Mount points** as a list
3. Each mount point is checked individually
4. Incidents are tracked per mount point

---

## Maintenance Windows (Enterprise)

Schedule periods when notifications are suppressed, for example during planned maintenance or nightly tests.

### Setup

1. Go to **Stream Monitor > Maintenance Windows**
2. Select the **day** (Monday through Sunday)
3. Set the **start and end hour**
4. During maintenance windows, no notifications are sent, but checks continue normally

---

## Supported Protocols

The Stream Monitor supports the two most commonly used streaming protocols:

### Shoutcast

- Fully supported with ICY metadata
- Automatic listener detection via the statistics page
- AutoDJ detection

### Icecast

- Fully supported with ICY metadata
- Support for multiple mount points
- Metadata parsing for now-playing information

Both protocols support:
- HTTPS/TLS connections
- Automatic redirect following
- Bitrate detection via ICY headers
- Artist and title information

---

## Incident Types

The Stream Monitor can detect the following issues:

| Type | Description | Minimum Tier |
|------|-------------|--------------|
| **Offline** | Stream is unreachable | Basic |
| **Silence** | Audio is silent (below threshold) | Pro |
| **Bitrate drop** | Bitrate is lower than expected | Pro |
| **Stuck metadata** | Same track displayed for too long | Pro |
| **AutoDJ failover** | AutoDJ has taken over (live DJ dropped) | Pro |
| **High latency** | Response time is abnormally high | Basic |

---

## Uptime Statistics

The Stream Monitor automatically calculates uptime percentages:

- **24 hours** — availability over the past day
- **7 days** — availability over the past week
- **30 days** — availability over the past month

These percentages are calculated based on the number of successful checks relative to the total number of checks. Maintenance windows are excluded from the calculation.

---

## Frequently Asked Questions

### How quickly am I notified of an outage?

This depends on your subscription tier:
- **Basic:** maximum 5 minutes
- **Pro:** maximum 1 minute
- **Enterprise:** maximum 30 seconds

### Can I use the Stream Monitor without a streaming package?

No, the Stream Monitor is an add-on that is linked to an existing audio streaming package at Maenda Media.

### What happens during a maintenance window?

Checks are still performed and recorded, but no notifications are sent. Incidents are still created for record-keeping.

### How do I verify the webhook signature?

The webhook contains an `X-Maenda-Signature` header with the format `sha256=<hex>`. Calculate the HMAC-SHA256 of the request body with your secret key and compare it with the value in the header.

### Can I export historical data?

Yes, via the Stream Statistics page you can export data as CSV or PDF. This includes listener counts, bandwidth, and peaks over the selected period.

### Does the monitor also detect video issues?

No, the Stream Monitor is specifically designed for audio streams (Shoutcast/Icecast). Video streaming has a separate statistics panel.

Question 3

Setting up an SSH key on your VPS

Accepted Answer

## Accessing your VPS: SSH keys

On a Maenda Media VPS you log in over SSH using an **SSH key**. Password login over SSH is disabled for security reasons: the password shown in your dashboard is a **console password** and only works on the web console (emergency access through your browser). This article shows you how to create an SSH key, attach it to your VPS and log in securely — all within a few minutes.

## Why SSH keys instead of a password?

An SSH key is a cryptographic key pair: a **private key** that stays on your computer, and a **public key** that is placed on the server. When you log in, your computer mathematically proves it holds the private key — no secret ever travels across the wire.

| | Password | SSH key |
|---|---|---|
| Guessable by attackers | Yes (brute force) | No |
| Captured by phishing | Possibly | No |
| Revocable per device | No | Yes |
| Log in without typing | No | Yes |

Because automated attacks on port 22 try passwords around the clock, password login over SSH is disabled by default on our VPS plans.

## Step 1: Create an SSH key

Open a terminal (Windows: **PowerShell**, macOS/Linux: **Terminal**) and run:

```bash
ssh-keygen -t ed25519
```

Press **Enter** to accept the default location. You can optionally set a passphrase — an extra lock on your private key, which we recommend.

This works on Windows 10 and newer, macOS and Linux without any extra software. Two files are created:

- `id_ed25519` — your **private key**. Never share or upload it anywhere.
- `id_ed25519.pub` — your **public key**. This is what you paste into the dashboard.

## Step 2: Copy your public key

Display your public key and copy the entire line (it starts with `ssh-ed25519`):

**Windows (PowerShell):**

```powershell
type $env:USERPROFILE\.ssh\id_ed25519.pub
```

**macOS / Linux:**

```bash
cat ~/.ssh/id_ed25519.pub
```

## Step 3: Add the key via the dashboard

1. Log in to your Maenda Media dashboard
2. Go to **Services** and open your VPS
3. Choose **Manage** → **Console & Access**
4. Scroll to the **SSH Keys** section
5. Paste your public key into the field and click **Add**

The key is placed on your VPS immediately — no restart required.

## Step 4: Log in

Connect from the same computer on which you created the key:

```bash
ssh root@<your-vps-ip>
```

You'll find your VPS IP address on the **Console & Access** page. SSH automatically finds your key in `~/.ssh/`. If you set a passphrase, you'll be asked for it once.

## Multiple keys and removing keys

You can add as many keys as you like — for example one per device (laptop, workstation). If several people work on the same VPS, give each person their own key. To revoke a key, use the same dashboard section: click the trash icon next to the key. That device immediately loses access while all other keys keep working.

## The web console as emergency access

If something goes wrong — a bad firewall rule, broken SSH configuration, lost key — you can always reach your VPS through the **web console** in the dashboard (**Manage** → **Console & Access**). Log in there with the username and the **console password** shown in the dashboard. The web console works independently of SSH and of your VPS network configuration.

## Frequently asked questions

### Why doesn't my password work over SSH?

That's intentional: password login over SSH is disabled on our VPS plans. The password in your dashboard is a console password and only works on the web console. Over SSH you log in with an SSH key — follow the steps above.

### I lost my SSH key — what now?

No problem. Open the **web console** in the dashboard and log in with your console password. Then create a new key on your (new) computer with `ssh-keygen -t ed25519` and add the public key via **Console & Access** → **SSH Keys**. Optionally remove the old key from the list afterwards.

### Can I use the same key for multiple VPS servers?

Yes. You can place your public key on as many servers as you like; this is safe because the public key is not a secret. Add it per VPS through the dashboard.

### What's the difference between the public and private key?

The **private key** (`id_ed25519`) is secret and always stays on your computer. The **public key** (`id_ed25519.pub`) can be seen by anyone and is placed on servers. Only the combination of the two grants access. If anyone ever asks for your private key, it is always a scam.

### Does this work from my phone or tablet?

Yes, using an SSH app such as Termius (iOS/Android). Create a key pair in the app, copy the public key and add it through the dashboard, just like on a computer.

Question 4

Building n8n Workflows — User Guide

Accepted Answer

# Building n8n Workflows — User Guide

This guide walks you through using n8n to build powerful automation workflows step by step. From simple tasks to complex AI-driven processes.

---

## The n8n Interface

After logging into your n8n installation, you'll see the **dashboard** with an overview of all your workflows.

![n8n workflow editor — visual drag-and-drop interface](/images/vps-apps/n8n-template/hero-workflow.png)

The interface consists of:

| Component | Description |
|-----------|-------------|
| **Canvas** | The central workspace where you place and connect nodes |
| **Node Panel** | Left panel with all available nodes and integrations |
| **Toolbar** | Top bar with options to test, activate, and save |
| **Execution Log** | Bottom right for viewing previous executions |
| **Settings** | Workflow settings like name, tags, and error handling |

---

## Your First Workflow

Let's build a simple workflow that sends a weather report email every morning.

### Step 1: Create a new workflow

1. Click **"+ New Workflow"** in the top right
2. Name your workflow, e.g., *"Daily Weather Report"*
3. You start on an empty canvas with a **trigger node**

### Step 2: Set up the trigger

The trigger determines **when** your workflow starts:

- **Schedule Trigger** — At fixed times (e.g., every day at 07:00)
- **Webhook** — When a URL is called
- **Event-based** — On an app event (e.g., new email)

For our weather report, we choose **Schedule Trigger**:

```
Trigger: Schedule
Rule: Every day at 07:00
Timezone: Europe/Amsterdam
```

### Step 3: Add nodes

1. Click the **+** icon to the right of the trigger
2. Search for **"HTTP Request"** in the node panel
3. Configure the node:

```
Method: GET
URL: https://api.openweathermap.org/data/2.5/weather
Query Parameters:
  q: Amsterdam
  appid: your-api-key
  units: metric
  lang: en
```

4. Add a **"Send Email"** node after the HTTP Request
5. Connect the HTTP Request output to the Email node

### Step 4: Test and activate

1. Click **"Test Workflow"** to run the workflow manually
2. Check the output of each node in the **execution log**
3. When everything works, click the **"Active"** toggle to enable the workflow

---

## Commonly Used Nodes

Here are the nodes you'll use most frequently:

### Triggers

| Node | Usage |
|------|-------|
| **Schedule Trigger** | Run workflows at fixed times |
| **Webhook** | Start workflows via HTTP request |
| **Email Trigger (IMAP)** | React to incoming emails |
| **Cron** | Advanced schedules with cron expressions |

### Data & Logic

| Node | Usage |
|------|-------|
| **IF** | Conditional logic (if/then) |
| **Switch** | Multiple paths based on value |
| **Merge** | Combine data from multiple sources |
| **Set** | Add or modify fields |
| **Code** | Custom JavaScript or Python code |
| **Split In Batches** | Process large datasets in parts |

### Communication

| Node | Usage |
|------|-------|
| **Send Email** | Send emails via SMTP |
| **Slack** | Messages to Slack channels |
| **Telegram** | Messages via Telegram bot |
| **Discord** | Messages to Discord servers |

### Data Storage

| Node | Usage |
|------|-------|
| **Google Sheets** | Read/write to spreadsheets |
| **Airtable** | Database-like storage |
| **PostgreSQL** | Execute SQL queries directly |
| **MySQL** | MySQL database operations |

---

## AI Workflows with LangChain

n8n has built-in AI capabilities via **LangChain integration**. Build AI agents that autonomously execute tasks.

![AI Agent workflow in n8n with LangChain nodes](/images/vps-apps/n8n-template/ai-agent-workflow.png)

### AI Nodes Overview

![Available AI nodes in the n8n panel](/images/vps-apps/n8n-template/ai-nodes-panel.png)

The key AI nodes:

| Node | Function |
|------|----------|
| **AI Agent** | Autonomous agent that can use tools |
| **Basic LLM Chain** | Simple prompt → response chain |
| **Conversational Agent** | Agent with conversation memory |
| **OpenAI Chat Model** | GPT-4, GPT-3.5 models |
| **Anthropic Chat Model** | Claude models |
| **Vector Store** | Storage for embeddings (RAG) |
| **Text Splitter** | Split documents for embeddings |

### Example: AI Customer Service Agent

Here we build an AI agent that answers customer questions based on your knowledge base:

![AI Agent configuration with tools and memory](/images/vps-apps/n8n-template/ai-agent-config.png)

**Workflow setup:**

1. **Webhook Trigger** — Receives customer questions via API
2. **AI Agent** — Processes the question with:
   - **Chat Model**: OpenAI GPT-4 or Anthropic Claude
   - **Memory**: Window Buffer Memory (remembers last 10 messages)
   - **Tools**:
     - *Vector Store Tool* — Searches your knowledge base
     - *HTTP Request Tool* — Fetches live product info
     - *Calculator* — For price calculations
3. **Respond to Webhook** — Returns the answer

```
System Prompt:
"You are a customer service representative for [company].
Answer questions based on the knowledge base.
Be friendly and professional.
If you don't know the answer, refer to support@company.com."
```

### Multi-Agent Workflows

For more complex scenarios, combine multiple AI agents:

![Multi-agent workflow example](/images/vps-apps/n8n-template/multi-agent-example.jpg)

Examples:

- **Content Pipeline**: Agent 1 (research) → Agent 2 (writing) → Agent 3 (review)
- **Data Analysis**: Agent 1 (data fetching) → Agent 2 (analysis) → Agent 3 (report)
- **Customer Service**: Router Agent → Specialist Agent (technical/billing/general)

---

## Writing Custom Code

With the **Code** node, you can run JavaScript or Python for complex logic:

### JavaScript Example

```javascript
// Filter and transform all items
const results = items.map(item => {
  const data = item.json;
  return {
    json: {
      name: data.firstName + ' ' + data.lastName,
      email: data.email.toLowerCase(),
      isActive: data.lastLogin > Date.now() - 30 * 24 * 60 * 60 * 1000,
      label: data.totalOrders > 10 ? 'VIP' : 'Standard'
    }
  };
});

return results;
```

### Python Example

```python
# Data analysis with Python
import json
from datetime import datetime

results = []
for item in items:
    data = item['json']
    # Calculate age in days
    created = datetime.fromisoformat(data['createdAt'])
    age_days = (datetime.now() - created).days
    
    results.append({
        'json': {
            'id': data['id'],
            'age_days': age_days,
            'status': 'new' if age_days < 30 else 'existing'
        }
    })

return results
```

---

## Managing Credentials

Credentials (API keys, passwords) are securely stored in n8n:

1. Go to **Settings** → **Credentials**
2. Click **"+ Add Credential"**
3. Choose the type (e.g., *OpenAI API*, *Gmail OAuth*, *Slack Bot*)
4. Fill in the required details
5. Click **"Save"**

**Security tips:**

- Credentials are encrypted in the database
- Use **environment variables** for sensitive values
- Create separate credentials per environment (test/production)
- Limit API keys to only the required permissions

---

## Organizing Workflows

### Tags

Use tags to categorize workflows:

- `production` — Active, tested workflows
- `development` — Workflows in development
- `marketing` — Marketing automation
- `finance` — Financial processes

### Folders

Organize workflows in folders by department or project.

### Versioning

n8n supports **workflow versioning**:

- Each save creates a new version
- You can revert to previous versions
- Export workflows as JSON for version control in Git

```bash
# Export workflow as JSON backup
curl -X GET https://your-n8n.com/api/v1/workflows/WORKFLOW_ID \
  -H "X-N8N-API-KEY: your-api-key" \
  -o workflow-backup.json
```

---

## Error Handling

Make your workflows robust with proper error handling:

### Error Trigger

Create a separate workflow that starts on errors:

1. Use the **Error Trigger** node
2. Send a notification via Slack/email on errors
3. Log error details to a spreadsheet

### Try/Catch Pattern

1. Add an **IF** node after a risky operation
2. Check for successful output
3. Route errors to an alternative path

### Retry Logic

For API nodes, you can set up automatic retries:

```
Retry On Fail: Enabled
Max Tries: 3
Wait Between Tries: 1000ms
```

---

## Useful Tips

1. **Sticky Notes** — Add notes to your canvas to document workflows
2. **Sub-workflows** — Split complex workflows into smaller, reusable parts
3. **Expressions** — Use `{{ $json.field }}` to dynamically reference data
4. **Pinned Data** — Pin test data for consistent testing
5. **Keyboard shortcuts**:
   - `Ctrl+S` — Save
   - `Ctrl+Enter` — Run test
   - `Tab` — Open node panel
   - `Ctrl+Shift+E` — Open execution log
6. **Webhook URLs** — In production, always use the *Production URL*, not the test URL
7. **Rate Limiting** — Add `Wait` nodes between API calls to respect rate limits

---

## More Information

- **n8n Documentation**: [docs.n8n.io](https://docs.n8n.io)
- **Community Forum**: [community.n8n.io](https://community.n8n.io)
- **Workflow Templates**: [n8n.io/workflows](https://n8n.io/workflows)
- **LangChain in n8n**: [docs.n8n.io/langchain](https://docs.n8n.io/langchain)

Need help building a specific workflow? Contact our support team via the chat window at the bottom right or send an email to support@maenda.media.

Question 5

Getting started with your web hosting

Accepted Answer

## Alles zit in je dashboard

Je hoeft geen apart bedieningspaneel te leren. Log in, klik je hostingdienst aan en klik op **Beheer**. Daar staat alles: je e-mailadressen, je databases, je bestanden, je DNS, je PHP-versie.

![Het beheermenu van je webhosting, met de groepen E-mail, Website, Databases, Bestanden en Domeinen, Beveiliging, en Backup en Herstel.](/images/docs/webhosting-toegang.svg)

## Het menu, groep voor groep

| Groep | Wat erin staat |
|---|---|
| **E-mail** | E-mailaccounts, Doorstuurregels, Autoresponders, Catch-All, E-mail Filters |
| **Website** | DNS Beheer, Redirects, Domein Pointers, Cron Jobs, PHP-versie |
| **Databases** | MySQL Databases, phpMyAdmin |
| **Bestanden & Domeinen** | Bestandsbeheer, FTP Accounts, Domeinen |
| **Beveiliging** | SSL Certificaten, Spam Filter, Beveiligde Mappen, SSH Sleutels, Geblokkeerde IPs |
| **Backup & Herstel** | Backups |

## De eerste drie dingen

**1. Zet je website erop.** Via Bestandsbeheer in de browser, of met FTP als je vaker iets wijzigt. Zie *Je website erop zetten*.

**2. Maak je e-mailadressen aan.** Onder E-mailaccounts. Zie *E-mail instellen*.

**3. Controleer je DNS.** Wijzen de nameservers van je domein naar ons? Alleen dan doen de records die je hier invult iets. Zie *DNS beheren*.

## Waar je verder over leest

- *Je website erop zetten* — bestandsbeheer, FTP en SSH
- *E-mail instellen* — adressen, doorsturen, autoresponders en filters
- *Databases aanmaken en beheren*
- *PHP-versie kiezen*
- *SSL en https*
- *Back-ups maken en terugzetten*
- *Wat er in je pakket zit* — de grenzen, en wat "onbeperkt" betekent

## Als je van een andere partij komt

Wij verhuizen je website en e-mail kosteloos. Je hoeft niets te downloaden of te exporteren; laat weten waar je nu zit en wij nemen contact op. Het overzetten gebeurt vóórdat de DNS omgaat, zodat je site niet offline raakt.

Guides

Installing n8n on your VPS — Complete Guide

Stream Monitor: monitoring your audio stream

Getting started with your web hosting

Knowledge Base

VPS Applications

Web hosting

VPS

Domain names

Email security

Security

Streaming & monitoring

Didn't find what you were looking for?