Short answer: Drop the "Beds24 → List Bookings" 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 |
|---|---|---|---|
Property ID propertyId | string | Optional | Filter by property ID |
Arrival From arrivalFrom | string | Optional | Filter bookings arriving after this date (YYYY-MM-DD) |
Arrival To arrivalTo | string | Optional | Filter bookings arriving before this date (YYYY-MM-DD) |
Filter filter | string | Optional | Predefined filter: arrivals, departures, new, current |
{"propertyId": "e.g. 12345","arrivalFrom": "2025-01-01","arrivalTo": "2025-12-31","filter": "arrivals"}
[{"id": 123456,"price": 500,"roomId": 111,"status": "confirmed","arrival": "2025-06-01","currency": "USD","numAdult": 2,"numChild": 0,"departure": "2025-06-05","guestName": "Doe","guestEmail": "john@example.com","propertyId": 12345,"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.