<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/ae6c792333a94e65b83805b0c897a8eb&quot; frameborder=&quot;0&quot; width=&quot;1658&quot; height=&quot;1243&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1243</height><width>1658</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1243</thumbnail_height><thumbnail_width>1658</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/ae6c792333a94e65b83805b0c897a8eb-3d71654ae84c4542.gif</thumbnail_url><duration>670.101</duration><title>CloudBeds Groups and Events Integration Walkthrough</title><description>This Loom explains how to connect Event Temple to CloudBeds using the Groups and Events module and demonstrates the workflow for syncing accounts and room blocks. It covers field mappings, including Event Temple profiles to CloudBeds profiles, bookings to events, room blocks to allotment blocks, and contacts nested under the profile, noting there is no financial data syncing. It also shows how to check live room type availability in Event Temple via the top right availability view in GRC for specific date ranges, and how tentative status pushes to CloudBeds without holding inventory while definite status holds inventory automatically. The example uses a Petco account and an Elise Silver contact, and it demonstrates syncing a block for the 29th to the 30th with room rates for Deluxe King and Deluxe Queen (with available counts of six and five) before switching the block to definite.</description></oembed>