YieldWizard for Cloudbeds
Last updated September 22, 2026
YieldWizard is the AI asset manager for independent hotels. It reads your Cloudbeds data, works out what each date is worth, and writes rates and minimum stay rules back to Cloudbeds. You choose how it writes: either it proposes and waits for your click, or you set it to Automatic and it writes on its own. This page explains how to connect it, exactly what it reads and writes in each mode, and how to disconnect.
Creating your account
Go to yieldwizard.ai and create an account with your email address. If you are coming from the Cloudbeds Marketplace you can start from there instead: choose Connect App on the YieldWizard listing and you will be asked to sign in or create an account as part of the same flow.
Connecting Cloudbeds
The quickest way is from the Cloudbeds Marketplace. Open the YieldWizard listing in your Cloudbeds account and choose Connect App. Cloudbeds shows you exactly which permissions YieldWizard is asking for. Approve them, and Cloudbeds sends the credential to YieldWizard automatically. Your property is created for you and the first sync starts straight away. There is nothing to copy or paste.
You can also connect from inside YieldWizard: on the onboarding screen, or under Settings then Connections, choose Connect Cloudbeds and you will be taken to the same Cloudbeds approval screen.
If your account cannot use the Marketplace flow, there is a manual fallback. In Cloudbeds go to Account, then Apps and Marketplace, then API Credentials, and create a credential with the Revenue Management System integration type. Copy the key, which begins with cbat_, and paste it into YieldWizard. Choose the Revenue Management System type rather than a reporting type, because a read-only credential cannot apply the rate changes you approve.
The first sync usually takes a few minutes. Larger properties with several years of history can take longer.
What the integration does
YieldWizard reads your room types and inventory, your rate plans and their restrictions, your reservations, room blocks and allotments, and your folio transactions. It uses that history to work out what each date is worth, compares it to your own normal for that day of the week, and proposes a rate.
What it writes, and when
For pricing, YieldWizard writes two things and only two things: the nightly rate and the minimum length of stay. It writes them per rate plan, one plan at a time, so each room type receives its own number. It does not edit reservations, guests, inventory or availability as part of pricing, and every rate write is checked to confirm it did not move a minimum stay, and the other way round. The only other writes are the room and group hold changes described under Closing rooms and releasing group holds below, and those happen only when you tap a button.
There are two modes, set per property and per feature, and you can move between them at any time.
Approve first. YieldWizard shows you the change it wants to make and writes nothing until you click. This is where every property starts.
Automatic. You hand a feature the keys and it writes without asking again. Automatic minimum stays review your calendar once a day and writes the nights that need to change. Automatic rates review prices every hour. Both stay inside limits you set: a rate floor and ceiling you have to enter before anything can move, a cap on how many dates change in a day, a cap on how far one date can move, and a daily ceiling on how many times the same night can be rewritten. It never raises a minimum stay within 48 hours of arrival, and it never overwrites a longer minimum you set by hand.
In both modes YieldWizard sends the change to Cloudbeds and then reads the result back to confirm it actually landed. If Cloudbeds refuses a write, it is reported as failed, never as applied. If a minimum-stay change reaches some rate plans and is held on others, it is reported as partial and names the plans that were left alone, and the night stays in the change list rather than being counted done. If we cannot confirm the outcome yet, it stays pending and is re-checked on the next run rather than being guessed either way. Every change is listed with a timestamp, and every applied change can be reverted from the same screen.
There is a single off switch. Turning Automatic off stops the unattended writing immediately. It does not undo yesterday's changes, because silently reversing your calendar because a switch moved would be its own surprise; anything already written stays until you revert it or change it.
Alongside rates, YieldWizard can set minimum stay and closed to arrival rules, show occupancy, pace and pickup, track competitor rates, and build a profit and loss statement. Some features, such as charging no-show fees, are switched off by default and stay off until you turn them on.
Two limits worth knowing. Cloudbeds does not allow rates to be updated on derived rate plans, so YieldWizard tells you when a plan has to be edited in Cloudbeds directly rather than silently skipping it. And rate updates are queued by Cloudbeds, so a change can take a couple of minutes to confirm.
Closing rooms and releasing group holds
When it is switched on for your property, you can ask the YieldWizard assistant to close a room, or to give back the rooms a group is holding that nobody has booked. Neither ever happens on its own and neither happens from a sentence alone. The assistant first shows you exactly what would change, and Cloudbeds is only touched when you tap the button on that card. Automatic mode never does either.
Closing a room. Closing a room creates an out of service room block in Cloudbeds with the reason you gave, for the nights you chose. It refuses a room with a guest in it on any of those nights, and one request closes at most 30 room-nights and never every room of one type for more than 7 nights.
Reopening a room. Cloudbeds only lets a room block be taken off by deleting it, so reopening a room deletes its room block and nothing else. By default YieldWizard only removes blocks it created itself; a block made in Cloudbeds is removed only when you name that block. After either change YieldWizard reads your room blocks back from Cloudbeds and reports it as done only when it sees the change. The account owner decides which people on the team may close and reopen rooms.
Releasing a group hold. For a group allotment block, such as a wedding or an event, YieldWizard gives back only the held rooms that have not been booked. Each night you chose is set down to the number of rooms already booked from the hold, never below it, so rooms your group has booked and their reservations are never touched and nothing is cancelled. If the hold changed in Cloudbeds after you saw the preview, that night is left alone and you are asked to look again.
After each of these, YieldWizard reads Cloudbeds back to confirm the change landed, and only reports it as done when the numbers match. If Cloudbeds accepted the change but shows something different when read back, it says so and asks you to check, rather than calling it done. Every change is listed in History and a released group hold sends your general manager a note. A released group hold can be undone from History, which puts the hold back to the number of rooms it held before on every night that has not changed since.
Disconnecting
You can disconnect from either side. In Cloudbeds, open the YieldWizard app in your Marketplace and choose to disconnect it. In YieldWizard, go to Settings then Connections and choose Disconnect Cloudbeds. That control asks you to type the word disconnect first, because it stops every number in the product.
When you disconnect in Cloudbeds, the credential stops working immediately and YieldWizard stops reading your property. YieldWizard does not delete your account or your history at that point, because disconnecting is reversible and is sometimes done by accident. You will see a clear notice in the app telling you the connection is no longer live, and you can reconnect to pick up where you left off.
If you want your data removed as well, use the separate Delete this property control in YieldWizard settings, which deletes the property record and its stored data, or email us and we will delete your account entirely. Disconnect Cloudbeds by itself never deletes anything.
Getting help
Open Support inside YieldWizard, or email support@yieldwizard.ai. We answer within one business day, and same day for anything urgent such as a rate that did not apply correctly. If a connection has stopped working, tell us your property name and roughly when you last saw fresh numbers, which is usually enough for us to find it.