Short answer: Drop the "Beds24 → Create Booking" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Room ID roomId | string | Required | The room/unit ID for the booking |
Arrival Date arrival | string | Required | Check-in date (YYYY-MM-DD) |
Departure Date departure | string | Required | Check-out date (YYYY-MM-DD) |
Guest First Name guestFirstName | string | Required | Guest's first name |
Guest Last Name guestName | string | Required | Guest's last name |
Guest Email guestEmail | Optional | Guest's email address | |
Number of Adults numAdult | string | Optional | Number of adults |
{"roomId": "e.g. 111","arrival": "2025-06-01","departure": "2025-06-05","guestFirstName": "{{trigger.guestFirstName}}","guestName": "{{trigger.guestName}}"}
[{"id": 123457,"roomId": 111,"status": "confirmed","arrival": "2025-06-01","numAdult": 2,"departure": "2025-06-05","guestName": "Doe","guestEmail": "john@example.com","guestFirstName": "John"}]
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.