OtherReal-timeUpdated May 2026

Beds24

Beds24 hospitality booking automation

Beds24 is the property-management system used by short-term rental hosts and small hotels to sync inventory and bookings across OTAs (Airbnb, Booking.com, Vrbo, Expedia) and a direct-booking engine. Tiny Command exposes four actions, no triggers (Beds24 supports outbound notifications configured in the account settings pointing at a webhook URL; for booking-arrived workflows, configure those to fire at a Tiny Command webhook trigger): List Properties, List Bookings (with filters by property, arrival date range, status), Get Booking (full detail with guest, dates, room assignment, payment status, channel reference), Create Booking (direct booking entry — not OTA-routed). The connection uses a Beds24 API key from the account settings. The booking model carries OTA-channel attribution (channel_id, channel_reference) so workflows that fan out booking-confirmation messaging can branch by source — Airbnb bookings get an Airbnb-specific welcome flow, direct bookings get the higher-touch onboarding. List Bookings filtered by arrival_date is the foundation for arrival-day automation: morning workflow runs at 6am, fetches today's arrivals, fans out check-in messages, prep tasks for cleaners, key codes for smart locks.

Connect Beds24

0triggers

4actions

≈ 2 minto set up

Freetier · no card

Actions

Do anything Beds24 can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

Action	What it does	Inputs
Create Booking	Creates a direct booking (not through an OTA) with guest details, dates, room, total price. Useful for "phone reservation taken at the front desk → log to Beds24 PMS" workflows. OTA bookings flow in automatically from Beds24's channel manager.	7 fields	View →
Get Booking	Returns the full booking record by ID — guest, dates, room assignment, payment status, OTA channel attribution if synced from Airbnb/Booking.com/Vrbo. The lookup for arrival-day workflows that need fresh booking detail before sending check-in messaging.	1 fields	View →
List Bookings	Paginated bookings filterable by property, arrival date, status, and channel. The base query for "today's arrivals", "this week's revenue", or "all bookings for property X this month" reporting and operations workflows.	4 fields	View →
List Properties	Returns every property in the account with name, location, room count, and current activity summary. Useful for multi-property hosts running per-property workflows or for inventorying the property portfolio.	0 fields	View →

Recipes

Pre-built Beds24 workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Beds24 → Slack alerts

AI-triage every Beds24 event, ping the right channel only when it matters.

Beds24 → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

Beds24 → Notion database

Turn Beds24 into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect Beds24 once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every Beds24 field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the Beds24 integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect Beds24 to Tiny Command?

Open the Tiny Command workflow builder, drop in a Beds24 node, and click Connect. Authorize Beds24 once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What Beds24 triggers does Tiny Command support?

Tiny Command focuses on outbound actions for Beds24 today. Use Tiny Command's universal Webhook or Schedule trigger to start Beds24 workflows, then run any Beds24 action you need.

What Beds24 actions can I run from a workflow?

4 Beds24 actions are available out of the box, covering other operations like "Create Booking". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the Beds24 integration real-time?

Beds24 actions execute synchronously inside your workflow. Tiny Command waits for Beds24's API to confirm before continuing to the next step, so downstream nodes can rely on the result.

Do I need to write code to use Beds24 with Tiny Command?

No. Every Beds24 trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Beds24 API endpoint directly.

How much does the Beds24 integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The Beds24 integration itself has no per-app surcharge.