One-Ping + Make (Integromat) Integration

Why Use One-Ping with Make?

Make (formerly Integromat) is a visual automation platform known for its powerful data transformation capabilities and flexible scenario builder. It connects hundreds of apps and services through a drag-and-drop interface, making it ideal for building complex notification workflows without writing code.

When paired with One-Ping, Make becomes a notification powerhouse. Instead of adding separate modules for each messaging platform in your scenario, you connect a single HTTP module to One-Ping's API and let it handle multi-channel delivery. This keeps your scenarios clean, reduces the number of operations consumed, and centralizes your notification configuration in the One-Ping dashboard.

Make's strength lies in its ability to handle complex data routing, transformation, and error handling, which pairs perfectly with One-Ping's simple API. You can build scenarios that dynamically select notification channels based on event severity, user preferences, or business rules, all within Make's visual editor.

Integration Capabilities

How to Set Up One-Ping in Make

HTTP Module Configuration

Here is the exact configuration for Make's HTTP module to call One-Ping. These settings go into the "Make a request" module:

URL: https://api.one-ping.com/send

Method: POST

Headers:
  Name: Authorization
  Value: Bearer YOUR_ONE_PING_API_KEY

  Name: Content-Type
  Value: application/json

Body type: Raw
Content type: JSON (application/json)

Request content:
{
  "message": "{{1.customer_name}} placed order #{{1.order_number}} for ${{1.total_price}}",
  "channels": ["telegram", "email", "slack"],
  "recipient": "{{1.customer_email}}"
}

In Make, the {{1.field_name}} syntax references data from the first module (your trigger). Click inside any field to open Make's data mapping panel where you can select fields from previous modules.

Example: Shopify Order Notification Scenario

This scenario watches for new Shopify orders and sends a multi-channel notification through One-Ping to your Slack workspace, Telegram group, and the customer's Email.

// Scenario: Shopify > HTTP (One-Ping)
// Module 1: Shopify - Watch Orders
// Module 2: HTTP - Make a request

{
  "message": "New order from {{1.customer.first_name}} {{1.customer.last_name}}!\n\nOrder: #{{1.order_number}}\nItems: {{1.line_items[].title}}\nTotal: ${{1.total_price}}\nShipping: {{1.shipping_address.city}}, {{1.shipping_address.country}}",
  "channels": ["slack", "telegram", "email"],
  "recipient": "{{1.customer.email}}",
  "metadata": {
    "order_id": "{{1.id}}",
    "source": "make-scenario"
  }
}

Example: Webhook-Triggered Alert

Receive any external webhook event and forward it as a multi-channel notification. This pattern works with any system that can send webhooks, including monitoring tools, payment processors, and custom applications.

// Scenario: Custom Webhook > HTTP (One-Ping)
// Module 1: Webhooks - Custom webhook
// Module 2: HTTP - Make a request

{
  "message": "Alert: {{1.event_type}}\n\nDetails: {{1.description}}\nSeverity: {{1.severity}}\nTimestamp: {{formatDate(now; 'YYYY-MM-DD HH:mm:ss')}}",
  "channels": ["telegram", "discord", "email"],
  "recipient": "[email protected]"
}

Advanced Make Patterns

Router for Priority-Based Channel Selection

Use Make's Router module to split your scenario into multiple paths. Each path can call One-Ping with different channel configurations based on the event's priority level or type:

// Router Path 1: Critical alerts (filter: severity = "critical")
{
  "message": "CRITICAL: {{1.alert_message}}",
  "channels": ["telegram", "email", "slack", "discord"],
  "recipient": "{{1.team_email}}"
}

// Router Path 2: Info alerts (filter: severity = "info")
{
  "message": "INFO: {{1.alert_message}}",
  "channels": ["slack"],
  "recipient": "{{1.team_email}}"
}

Error Handling with Fallback Notifications

Make's error handling routes let you catch failed One-Ping API calls and take corrective action. For example, if the primary notification fails, you can retry or send an error alert through an alternative channel:

// Add an error handler route to the HTTP module
// Error Handler: Resume directive + HTTP module

// Fallback notification (different channels)
{
  "message": "FALLBACK: Original notification failed. Error: {{2.error.message}}. Original message: {{1.message}}",
  "channels": ["email"],
  "recipient": "[email protected]"
}

Common Use Cases

• E-commerce notifications: Watch for new orders, refund requests, or inventory changes and alert your team on Slack while emailing the customer
• Form processing: Receive Typeform or Gravity Forms submissions via webhook and push notifications to your sales team on Telegram and Email
• Infrastructure monitoring: Connect Uptime Robot or Pingdom webhooks to alert your DevOps team on Discord and Telegram when services go down
• Scheduled reports: Use Make's schedule trigger to compile weekly data from Google Sheets or your database, then broadcast summaries to all channels
• Payment alerts: Watch for Stripe or PayPal events and send real-time payment notifications to your finance team across multiple platforms
• HR onboarding: Trigger welcome messages and onboarding notifications to new employees via Email and Slack when they are added to your HR system