One-Ping + n8n Integration: Automate Multi-Channel Notifications

Why Use One-Ping with n8n?

n8n is one of the most popular open-source workflow automation platforms, and it pairs perfectly with One-Ping's multi-channel notification API. Instead of configuring separate nodes for Telegram, Email, Slack, and Discord in every workflow, you can use a single HTTP Request node pointed at One-Ping to reach all your channels at once.

This combination gives you the power of n8n's 400+ app integrations as triggers, with One-Ping handling the notification delivery across every channel your team or users need. Whether you are monitoring servers, processing e-commerce orders, or building internal alerts, the One-Ping + n8n stack eliminates repetitive notification logic from your workflows.

What You Can Build

How to Set Up One-Ping in n8n

n8n HTTP Request Node Configuration

Here is the exact configuration for the HTTP Request node in n8n. This example sends a notification to Telegram, Email, and Slack when triggered:

// HTTP Request Node Settings
Method: POST
URL: https://api.one-ping.com/send

// Headers
Authorization: Bearer {{ $credentials.onePingApiKey }}
Content-Type: application/json

// JSON Body
{
  "message": "New order #{{ $json.order_id }} from {{ $json.customer_name }} - ${{ $json.total }}",
  "channels": ["telegram", "email", "slack"],
  "recipient": "{{ $json.customer_email }}",
  "metadata": {
    "order_id": "{{ $json.order_id }}",
    "source": "n8n-workflow"
  }
}

Ready-Made n8n Templates

One-Ping provides pre-built n8n workflow templates that you can import directly into your n8n instance. These templates are tested, documented, and ready to use. Simply replace the API key and customize the message format to match your needs.

Template: E-commerce Order Notification

This template listens for WooCommerce or Shopify webhook events and sends order confirmation notifications to your team on Slack and to the customer via Email and Telegram.

// n8n Workflow JSON (importable)
{
  "nodes": [
    {
      "name": "Webhook Trigger",
      "type": "n8n-nodes-base.webhook",
      "parameters": {
        "path": "order-created",
        "httpMethod": "POST"
      }
    },
    {
      "name": "Send via One-Ping",
      "type": "n8n-nodes-base.httpRequest",
      "parameters": {
        "method": "POST",
        "url": "https://api.one-ping.com/send",
        "headers": {
          "Authorization": "Bearer YOUR_API_KEY"
        },
        "body": {
          "message": "Order #{{ $json.id }}: {{ $json.line_items[0].name }} - ${{ $json.total }}",
          "channels": ["telegram", "email", "slack"],
          "recipient": "{{ $json.billing.email }}"
        }
      }
    }
  ]
}

Template: Server Down Alert

Monitor your infrastructure with a cron-based health check. If the endpoint returns an error or times out, One-Ping fires alerts to Discord, Telegram, and Email simultaneously.

// Health Check Workflow
// Trigger: Cron node (every 5 minutes)
// Step 1: HTTP Request to your server health endpoint
// Step 2: IF node - check if status != 200
// Step 3: One-Ping notification

{
  "message": "ALERT: Server {{ $json.server_name }} is DOWN. Status: {{ $json.status_code }}. Checked at {{ $now.toISO() }}",
  "channels": ["discord", "telegram", "email"],
  "recipient": "[email protected]"
}

Advanced: Dynamic Channel Selection in n8n

One of the most powerful patterns with One-Ping in n8n is dynamically selecting which channels to notify based on the event type or severity. You can use n8n's expression editor to build the channels array conditionally.

// Dynamic channel selection using n8n expressions
{
  "message": "{{ $json.alert_message }}",
  "channels": {{ $json.severity === "critical"
    ? ["telegram", "email", "slack", "discord"]
    : ["slack"] }},
  "recipient": "{{ $json.team_contact }}"
}

Use Cases Perfect for n8n + One-Ping

The combination of n8n's workflow automation and One-Ping's unified notification API is ideal for a wide range of scenarios. Here are some of the most popular use cases our users build:

• E-commerce alerts: Order confirmations, shipping updates, abandoned cart reminders sent to customers via their preferred channel
• DevOps monitoring: Server health checks, deployment notifications, error rate alerts pushed to your ops team on multiple platforms
• Lead management: New form submissions or CRM updates that notify your sales team instantly on Slack and Telegram
• Appointment reminders: Scheduled notifications sent 24 hours and 1 hour before appointments via Email and SMS
• Inventory alerts: Stock level monitors that notify purchasing teams when items drop below thresholds
• Payment notifications: Stripe or PayPal webhook events routed through One-Ping to confirm payments on multiple channels

Comparing One-Ping vs. Individual n8n Notification Nodes