One-Ping + Zapier Integration: No-Code Notifications

Why Use One-Ping with Zapier?

Zapier is the world's most popular no-code automation platform, connecting over 5,000 apps with simple "if this, then that" workflows called Zaps. By combining Zapier with One-Ping, you can turn any app event into a multi-channel notification without writing code or managing complex integrations.

Without One-Ping, sending notifications to multiple channels in Zapier requires creating separate action steps for each channel: one for Slack, one for Email, one for Telegram. Each step consumes a Zapier task, and each channel needs its own configuration. With One-Ping, you replace all of those steps with a single webhook call that fans out to every channel you need. Fewer steps, fewer tasks consumed, simpler Zaps.

Popular Zapier + One-Ping Automations

How to Connect One-Ping with Zapier

Zapier Webhook Configuration

Here is the exact setup for the "Webhooks by Zapier" Custom Request action step. Copy these settings into your Zap:

Method: POST

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

Headers:
  Authorization  |  Bearer YOUR_ONE_PING_API_KEY
  Content-Type   |  application/json

Data (raw JSON):
{
  "message": "New payment of ${{amount}} from {{customer_email}}",
  "channels": ["telegram", "email", "slack"],
  "recipient": "{{customer_email}}"
}

Replace {{amount}} and {{customer_email}} with Zapier's dynamic data fields from your trigger step. Click the "+" icon in each field to map data from the previous step.

Example: New Stripe Payment Notification

This Zap triggers when a new payment is received in Stripe and sends notifications via One-Ping to your team on Slack and Telegram, and a receipt to the customer via Email.

// Trigger: Stripe > New Payment
// Action: Webhooks by Zapier > Custom Request

{
  "message": "Payment received: ${{1. Amount / 100}} from {{1. Customer Email}}. Invoice: {{1. Invoice ID}}",
  "channels": ["slack", "telegram", "email"],
  "recipient": "{{1. Customer Email}}",
  "metadata": {
    "payment_id": "{{1. ID}}",
    "source": "zapier"
  }
}

Example: New Google Form Response Alert

Notify your team every time someone submits a contact form, support request, or application through Google Forms.

// Trigger: Google Forms > New Response in Spreadsheet
// Action: Webhooks by Zapier > Custom Request

{
  "message": "New form submission from {{1. Name}}:\n\nEmail: {{1. Email}}\nSubject: {{1. Subject}}\nMessage: {{1. Message}}",
  "channels": ["slack", "telegram"],
  "recipient": "[email protected]"
}

Advanced Zapier Patterns with One-Ping

Multi-Step Zaps with Conditional Channels

Use Zapier's Filter or Paths feature to send different notifications based on conditions. For example, high-value orders (over $100) get sent to all channels, while smaller orders only go to Email:

// Path A: Order total >= $100
{
  "message": "HIGH-VALUE ORDER: ${{total}} from {{customer_name}}",
  "channels": ["telegram", "email", "slack", "discord"],
  "recipient": "{{customer_email}}"
}

// Path B: Order total < $100
{
  "message": "New order: ${{total}} from {{customer_name}}",
  "channels": ["email"],
  "recipient": "{{customer_email}}"
}

Using Zapier's Formatter for Rich Messages

Add a Formatter step before the One-Ping webhook to format dates, numbers, or combine multiple fields into a structured notification message. This ensures your notifications look clean and professional on every channel.

Benefits of One-Ping over Native Zapier Notifications