Per-pair page

Connect Bluesky to Slack in two minutes.

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

Connect Bluesky to Slack — start free See reverse direction

Trigger app

Bluesky as the trigger

Workflows fire when something happens in Bluesky.

Bluesky 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.

Bluesky → Slack

When something happens in Bluesky, do it in Slack.

0 Bluesky triggers wired to 45 Slack actions.

Slack → Bluesky

Or fire it the other way around.

13 Slack triggers wired to 3 Bluesky actions downstream.

See Slack → Bluesky →

How it works

Connect Bluesky and Slack in five steps.

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

1
Connect
Authorize Bluesky and Slack
Open TinyCommand, authorize Bluesky and Slack once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a Bluesky trigger
Drop the Bluesky → New event trigger onto the canvas. TinyCommand auto-registers the webhook.
POST /v1/webhooks/bluesky.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 Bluesky 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 Bluesky + Slack.

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

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

Is the Bluesky ↔ Slack integration real-time?

Yes. Both Bluesky 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 Bluesky 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 Bluesky events can trigger a Slack workflow?

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

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

No. There's a free tier that covers most Bluesky+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 → Bluesky instead?

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