Per-pair page

Connect Pushbullet to Slack in two minutes.

Real-time triggers from Pushbullet, ready-made actions in Slack. Filter, transform, and route without writing a line of code.

Connect Pushbullet to Slack — start free See reverse direction

Trigger app

Pushbullet as the trigger

Workflows fire when something happens in Pushbullet.

Pushbullet has no triggers yet. Use the catalog's universal Webhook trigger as the upstream.

Action app

Slack as the action

Workflows do something in Slack, instantly.

See all 45 actions →

Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

Pushbullet → Slack

When something happens in Pushbullet, do it in Slack.

0 Pushbullet triggers wired to 45 Slack actions.

Slack → Pushbullet

Or fire it the other way around.

13 Slack triggers wired to 3 Pushbullet actions downstream.

See Slack → Pushbullet →

How it works

Connect Pushbullet and Slack in five steps.

No code, no glue, no half-day setup. Each step is one click.

1
Connect
Authorize Pushbullet and Slack
Open TinyCommand, authorize Pushbullet and Slack once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a Pushbullet trigger
Drop the Pushbullet → New event trigger onto the canvas. TinyCommand auto-registers the webhook.
POST /v1/webhooks/pushbullet.event
3
Transform
Add a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
4
Action
Add the Slack action
Drop the Slack → Add Reaction action below it. Map fields from the Pushbullet payload into the Slack inputs.
slack.add-reaction
5
Publish
Publish and forget
Hit Publish. TinyCommand runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about Pushbullet + Slack.

How long does it take to connect Pushbullet and Slack on TinyCommand?

Under two minutes. Authorize Pushbullet and Slack once each, drop the Pushbullet trigger and Slack action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.

Is the Pushbullet ↔ Slack integration real-time?

Yes. Both Pushbullet and Slack expose webhooks, so events from one fire workflows in the other within seconds rather than on a polling interval.

Can I filter or transform data between Pushbullet and Slack?

Yes. Add a Filter node to only pass through matching events, a Switch node to branch by value, or an AI / Code node to transform payloads before they hit Slack.

What Pushbullet events can trigger a Slack workflow?

Use TinyCommand's universal Webhook trigger to receive Pushbullet events, then run any of the 45 Slack actions downstream.

Do I need a paid plan to use Pushbullet with Slack?

No. There's a free tier that covers most Pushbullet+Slack use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.

What if I want Slack → Pushbullet instead?

Build it the same way, in reverse. There's a dedicated /integrations/slack/with/pushbullet page with the reverse-direction triggers and actions.