Resources · Make integration

PingBell Make integrationAutomate PingBell with Make.

Need PingBell to ring when something happens in another tool? The PingBell Make integration gives you 4 modules: 3 actions and 1 search, with no trigger of its own. This page shows how to link your account, then walks you through a first scenario you can test right away.

Try the PingBell integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the PingBell Make integration do for you?

It lets Make, a no-code automation tool, send work to PingBell inside a scenario, which is the automation you build as a chain of modules. A module is one brick of that chain. PingBell brings four of them, all meant to act or look things up, so the event that starts the flow comes from another app or from a schedule.

Ring the right person when a form comes in. Start the scenario with a module from your form tool, then add Call a Notification so PingBell takes over for each new entry. Each new item travels as a bundle, one element passed from module to module.

Adapt the call to the data. When the content of the alert has to change with every record, Call a Dynamic Notification is the module whose name points to that job; map values from the earlier module into it.

Check what already exists. List PingBells is a search: it can return zero, one or several bundles, which you can then feed into the next step. For anything the listed modules skip, Make an API Call reaches any endpoint of the PingBell API with the same connection.

What the page cannot promise: the official documentation gives no field list and no limits for these modules, and it flags its own content as AI-generated, so check details in PingBell itself. PingBell may also have an n8n node; the n8n vs Make comparison helps you pick a tool, and the Make training covers the editor from scratch.

Connect

How do you connect your PingBell account to Make?

  1. 01

    Copy your API key in PingBell

    You need an active PingBell account first. Open the settings page in PingBell and click the API Key: it goes straight to your clipboard, ready to paste into Make.

  2. 02

    Add a PingBell module in Make

    In your scenario, add any PingBell module and click Create a connection. A connection is your PingBell account linked to Make once, then reused by every PingBell module you add later.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when you run several accounts. Paste the API key you copied, or follow the on-screen instructions, then save the connection.

First scenario

Build your first scenario with PingBell

GoalWhen a new record appears in another app, Make calls a PingBell notification.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + to add the first module. PingBell has no trigger, so this first slot goes to the app where the event happens.

  2. 02

    Pick the starting module

    Search for the app that holds the event, choose its module and click Create a connection to link that account. Fill its fields; Make lists what it can read once connected.

  3. 03

    Add Call a Notification

    Click the + to the right of the first module, search for PingBell and pick Call a Notification. Select your PingBell connection and map data from the first module into its fields.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open the bubble above each module to read the bundles it received and confirm PingBell got the call you expected.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each run of each module counts as an operation on your Make plan.

Modules

What each PingBell module does

PingBell gives you 4 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

PingBell1

Call a Dynamic Notification

ActionIn the docs only

This action gives you a PingBell call whose content can shift with each record, going by its name, since the docs describe no fields for it. You map values from earlier modules into it.

When to use it
pick it over Call a Notification when every alert must carry different details, like the name of the customer who just signed up.
Watch out
open the module in Make to see which fields it really asks for before you plan the mapping.
PingBell2

Call a Notification

ActionIn the docs only

Here you get the simplest way to make PingBell act from a scenario: one action, one call per bundle that reaches it. It is the natural second module after an event in another app.

When to use it
a fixed alert is enough, for instance telling the support team that a new ticket exists.
Watch out
every bundle arriving here triggers a call and an operation, so filter upstream if a search sends several items.
PingBell3

List PingBells

SearchIn the docs only

With this search you get back what PingBell holds under that name, as zero, one or several bundles that later modules can use one by one.

When to use it
before calling a notification, to check what exists in the account or to feed its results into another app.
Watch out
several results mean several bundles, so every module after it runs once per item and uses one operation each time.
PingBell4

Make an API Call

ActionIn the docs only

This module opens the whole PingBell API to your scenario: any endpoint can be called with the connection you already created, no new key needed.

When to use it
the three other modules do not cover what you need, and the PingBell API documents an endpoint that does.
Watch out
you write the request yourself, so keep the vendor's API reference open while you set it up.
Need help

Need help automating PingBell with Make?

A person reads every message.

FAQ

PingBell and Make: common questions

01Is the PingBell Make integration free?
Yes, on the Make side. PingBell is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. PingBell itself needs an active account; its own subscription terms are on the PingBell pricing page.
02What do you need to connect PingBell to Make?
An active PingBell account and its API key. You find the key on the settings page of PingBell, where one click copies it. Then, in Make, add a PingBell module, click Create a connection, give it a name if you like, and paste the key. The connection is stored once and every PingBell module in your scenarios can use it, so you only go through this step a single time per account.
03Does the PingBell Make integration react in real time?
It depends on what starts your scenario, because PingBell has no trigger module in Make. Its four modules only act or search. To launch a scenario, use a trigger from another app, which may be scheduled or instant depending on that app, or run the scenario on a schedule set on the first module. A new scenario checks every 15 minutes by default, and the Free plan cannot go below that interval. Paid plans allow a 1 minute interval.
04What if a PingBell module is missing in Make?
Use Make an API Call. With this module, any endpoint of the PingBell API can be called from your scenario using the connection you already set up. The official documentation lists no limits for the other modules and states that its content is AI-generated and may contain mistakes, so when a module does not behave as described, check the API reference and contact PingBell directly about their documentation. Every call made this way still counts as an operation on your Make plan.
05Should you use Make or n8n for PingBell?
It depends on the tool you already run. In Make, PingBell offers four modules: two ways to call a notification, a search that lists PingBells, and a universal API module. The same app often exists as an n8n node too. Compare what each side exposes for PingBell against the scenario you need, and stay in the platform where your other automations already live, since the connection and the habits carry over.
Same platform

Other docs you might need on this stack.

Browse all integrations