Per-pair page

Connect Beds24 to Slack in two minutes.

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

Connect Beds24 and Slack See reverse direction

Trigger app

Beds24 as the trigger

Workflows fire when something happens in Beds24.

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

Beds24 → Slack

When something happens in Beds24, do it in Slack.

0 Beds24 triggers wired to 45 Slack actions.

Slack → Beds24

Or fire it the other way around.

13 Slack triggers wired to 4 Beds24 actions downstream.

See Slack → Beds24 →

How it works

Connect Beds24 and Slack in five steps.

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

1
Connect
Authorize Beds24 and Slack
Open Tiny Command, authorize Beds24 and Slack once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a Beds24 trigger
Drop the Beds24 → New event trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/beds24.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 Beds24 payload into the Slack inputs.
slack.add-reaction
5
Publish
Publish and forget
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about Beds24 + Slack.

How long does it take to connect Beds24 and Slack on Tiny Command?

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

Is the Beds24 ↔ Slack integration real-time?

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

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

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

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

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