This article covers which fields sync between Event Temple and Cloudbeds, and how records in each system map to each other.
Record mapping
When a booking is synced from Event Temple to Cloudbeds, the integration creates or updates the following records:
Event Temple | Cloudbeds (Groups & Events) |
Account | Profile |
Booking | Event |
Room Block | Allotment Block |
Account Contacts | Contact Persons on Profile |
Primary Contact | Primary Contact on Profile |
Accounts → Profiles
When a booking is synced, Event Temple creates a Profile in Cloudbeds based on the linked Account. The profile code in Cloudbeds will correspond to the Account in Event Temple.
You can see on each Account in Event Temple whether it has been linked to a Cloudbeds Profile.
Contacts → Contact Persons
All contacts associated with the Account are pushed to Cloudbeds as Contact Persons on the Profile. If a contact is marked as the primary contact in Event Temple, they are also marked as the primary contact on the Cloudbeds Profile.
Bookings → Events
Each synced booking creates an Event in Cloudbeds under the corresponding Profile. Events carry:
Start and end dates
Booking name
Status
Room Blocks → Allotment Blocks
Room blocks in Event Temple sync as Allotment Blocks in Cloudbeds, nested under the Event. The following information syncs with the block:
Room type and counts
Block dates
Pickup (updated via Fetch from PMS)
Pickup continues to sync back from Cloudbeds to Event Temple. Use the Fetch from PMS button on a booking to pull in the latest block and pickup data from Cloudbeds.