PUSHBULLET n8n INTEGRATION: AUTOMATE PUSHBULLET WITH N8N

The Create Note action is your go-to for sending push notifications programmatically. This action allows you to compose and send a Pushbullet note—complete with title and body text—to your devices, specific channels, or contacts. It's the foundation of most notification workflows.

Key parameters:

• Credential to connect with: A required dropdown to select your authenticated Pushbullet account. You'll see your configured account listed here.
• Resource: Required dropdown set to "Push"—this defines that you're working with Pushbullet push notifications.
• Operation: Required dropdown set to "Create"—indicating you're sending a new push.
• Type: Required dropdown set to "Note"—specifying this will be a text-based notification.
• Title: Text input field for the notification's subject line. Keep it concise and descriptive.
• Body: Larger text field for the main content of your note. This is where you include the detailed message.
• Target: Optional dropdown to specify the destination—send to all devices (Default), a specific device, or a channel.

Use cases:

• Send automated alerts when your e-commerce store receives a new order via WooCommerce
• Push daily summary reports from your analytics dashboard to your phone
• Create instant notifications when a specific keyword appears in monitored emails

This action is perfect when you need to keep yourself or your team informed about events happening across your digital ecosystem. Combine it with any n8n trigger to create responsive notification workflows.

The Get Many action retrieves multiple pushes from your Pushbullet history in a single operation. This is essential for workflows that need to analyze, process, or act upon your existing notifications—whether for reporting, cleanup, or synchronization purposes.

Key parameters:

• Credential to connect with: Required dropdown to select your Pushbullet account credentials.
• Resource: Required dropdown set to "Push" to work with push notifications.
• Operation: Required dropdown set to "Get Many" for bulk retrieval.
• Return All: Optional toggle switch. When enabled, retrieves all available pushes regardless of the limit setting.
• Limit: Optional text field (default: 100) that sets the maximum number of pushes to retrieve when "Return All" is disabled.
• Filters: Expandable section allowing you to add criteria to narrow down which pushes are retrieved.

Use cases:

• Build a daily digest workflow that collects all pushes from the last 24 hours
• Create an archiving automation that backs up your push history to Google Sheets
• Analyze notification patterns by pulling push data into a reporting dashboard

When you need to process multiple notifications programmatically—whether for analysis, backup, or cleanup—the Get Many action provides the data access you need.

The Push: Delete action permanently removes a specific push from your Pushbullet account. This is crucial for maintaining a clean notification history, implementing retention policies, or building cleanup workflows that automatically remove outdated or processed notifications.

Key parameters:

• Credential to connect with: Required dropdown to select your authenticated Pushbullet account.
• Resource: Required dropdown set to "Push" to target push notifications.
• Operation: Required dropdown set to "Delete" for removal operations.
• Push ID: Required text field where you must enter the unique identifier of the push you want to delete. This ID can be obtained from the Get Many action or from webhook payloads.

Use cases:

• Automatically delete pushes older than 30 days to maintain a clean history
• Remove processed notifications after they've been logged to your database
• Clean up test pushes created during workflow development

Combine this action with Get Many to build sophisticated cleanup workflows. For instance, retrieve all pushes, filter for those older than a certain date, and delete them in a loop—all automated.

The Update Push action modifies an existing push notification. While Pushbullet pushes are generally immutable in content, this action allows you to mark pushes as dismissed—useful for managing notification states across your devices and keeping your Pushbullet feed organized.

Key parameters:

• Credential to connect with: Required dropdown to select your Pushbullet account for authentication.
• Resource: Required dropdown set to "Push" to work with push notifications.
• Operation: Required dropdown set to "Update" for modification operations.
• Push ID: Required text field for the unique identifier of the push you want to update.
• Dismissed: Optional toggle switch that, when enabled, marks the push as dismissed across all your devices.

Use cases:

• Auto-dismiss notifications after they've been processed by another part of your workflow
• Mark alerts as resolved once the underlying issue has been addressed
• Build a notification acknowledgment system that syncs dismissal states

This action is particularly valuable when you're building workflows that manage notification lifecycle states. Instead of deleting pushes, you can dismiss them to maintain history while keeping your notification feed clean.