Resources · Make integration

Pushbullet Make integrationAutomate Pushbullet with Make.

What if the alerts that matter landed on your phone without you checking five tabs? The Pushbullet Make integration gives you 1 trigger and 4 actions to push notes, links and files to your devices. This guide shows how to connect your account and build a first useful scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Pushbullet Make integration do for you?

It links your Pushbullet account to Make, a no-code tool where you build a scenario (an automation made of bricks called modules). Other apps then send notes, links or files to your phone or browser, and anything you push can start a scenario of its own.

A phone alert for the events you care about. A form gets a new signup, a payment fails, a support ticket turns urgent: the app where it happens starts the scenario, and Push a note sends a short message to the device you pick.

A reading list that fills itself. You push a link to yourself while browsing on your phone. Watch objects picks it up the next time the scenario runs, and a second module files it in a sheet or a database, such as the one covered on the Airtable Make integration page.

The right file on the right screen. A report is generated by another app, and Push a file drops it on the laptop where you will open it. Delete a push then clears old items so the feed stays readable.

What Make does not give you here: there is no generic API call module for Pushbullet, so you work with these 5 modules only. The same app also has a node in n8n, detailed on the Pushbullet n8n integration page, and the n8n vs Make comparison helps you pick a tool.

Connect

How do you connect Pushbullet to Make?

  1. 01

    Add a Pushbullet module

    In your scenario, add any Pushbullet module and click Create a connection. A connection is your Pushbullet account linked to Make once, then reused by every Pushbullet module you add later. You can give it a name in Connection name.

  2. 02

    Save and sign in

    Click Save. Pushbullet opens a login window: choose Sign in with Google or Sign in with Facebook, whichever you used to create your Pushbullet account, and enter your credentials there.

  3. 03

    Approve the access

    Click Approve so Make can act on your account. If Pushbullet asks you to authenticate again or confirm access, do it. Back in Make, the connection appears in the module and the field lists fill in.

First scenario

Your first scenario: a phone alert from another app

GoalWhen something important happens in another app, Make sends a Pushbullet note to your phone.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big +. Pick the trigger of the app where the event happens: your form tool, your shop, your spreadsheet.

  2. 02

    Set up that trigger

    Connect that app and fill its fields. Make lists the forms, sheets or folders it can read once the connection exists, so you choose from a menu instead of typing names.

  3. 03

    Add Push a note

    Click the + to the right of the trigger, search for Pushbullet and pick Push a note. Connect your account, choose your phone as the device, then map a name or an amount from the first module into the message.

  4. 04

    Test with Run once

    Click Run once, then create a test entry in the other app. Each module shows the bundles it received (a bundle is one item passed along, like one form answer), and your phone should buzz.

  5. 05

    Schedule and switch on

    On the first module, open Scheduling. A new scenario runs every 15 minutes by default. Keep it or change it, then switch the scenario on so it runs without you.

Triggers

What starts a Pushbullet scenario

1 module starts a scenario when something happens in Pushbullet. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Pushbullet as soon as it happens.

Pushbullet1Watch objects

Watch objects

Scheduled trigger

In MakeTriggers when a new object (a note, link, file etc.) is added.

Every new object that lands in your Pushbullet account, whether a note, a link or a file, becomes a bundle that the rest of your scenario can use. It turns the things you push to yourself into input for other apps.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, so new pushes arrive in batches rather than the moment you send them.
When to use it
you share a link from your phone to yourself and want it saved in a sheet, a notes app or a task list.
Watch out
if the same scenario also pushes to Pushbullet, it may pick up its own pushes on the next run. Play it safe and keep watching and pushing in separate scenarios.
Modules

What each Pushbullet module does

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

Pushbullet1

Push a note

Action

In MakeSends a note to a selected device.

This one sends a short text message to a device you pick, the simplest way to get a heads-up from a scenario without opening email or chat.

When to use it
a signup, a failed payment or an urgent ticket in another app deserves a buzz on your phone.
Watch out
map only the few values you need into the message, otherwise the notification becomes too long to read at a glance.
Pushbullet3

Push a file

Action

In MakeSends a file to a selected device.

Delivers a file produced or fetched earlier in the scenario to one of your devices, ready to open on the screen where you actually need it.

When to use it
another app generates a PDF, an export or an image and you want it on your laptop without digging through a shared drive.
Watch out
on the Make Free plan, files are capped at 5 MB, so for a large export push a link instead.
Pushbullet4

Delete a push

Action

In MakePermanently removes an object.

Removes a push from your account for good. There is no trash to recover it from, so treat this module with care and test it on a harmless push first.

When to use it
once Watch objects has copied a pushed link into your reading list, you clear it so your Pushbullet feed only shows what is still pending.
Watch out
map the push identifier from the module that saw it, never a hand-typed value.
Need help

Need help automating Pushbullet with Make?

A person reads every message.

FAQ

Questions people ask next

01Is the Pushbullet Make integration free to use?
Yes. Pushbullet is a standard app in Make, so it works on the Free plan. That plan comes with limits worth knowing: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Make counts usage in operations, one operation being one module handling one bundle, so a note pushed to your phone costs one operation.
02What does it take to connect Pushbullet to Make?
A Make account and a Pushbullet account you sign in to with Google or Facebook. The documentation lists no other prerequisite. You add a Pushbullet module, click Create a connection, save, sign in with the account you use for Pushbullet and click Approve. If Pushbullet asks you to authenticate again, confirm it. The advanced settings for custom client credentials are optional and only matter if you registered your own Pushbullet app. Once the connection exists, every Pushbullet module in any scenario can reuse it.
03Does the Pushbullet trigger fire in real time?
No. Watch objects is a scheduled trigger, marked with a clock badge in the editor. Make checks your Pushbullet account on the scenario's schedule, every 15 minutes by default, and picks up everything pushed since the last check. On the Free plan the shortest interval is 15 minutes; paid plans go down to 1 minute. If you need an alert the moment something happens elsewhere, start the scenario on an instant trigger from the other app and use Push a note as the action.
04What if a Pushbullet module is missing in Make?
It depends on what you need. Make offers 5 Pushbullet modules: Watch objects plus four actions to push a note, a link or a file and delete a push. There is no generic API call module for this app, so anything beyond those five is out of reach inside the Pushbullet app itself. You can often get close by combining modules, for example sending a link instead of a large file. For a case that really needs more, the team can look at your scenario with you.
05Make or n8n for Pushbullet: which one fits?
It depends on the tool you already build in. Pushbullet exists in both tools. Make offers 5 modules built around a scheduled trigger, while n8n has a Pushbullet node. If your other automations live in Make, stay there so connections and scenarios are in one place. If your team already runs workflows in n8n, its Pushbullet node keeps everything together on that side. The honest criterion is where your other workflows already run, since this page does not rank the two tools.