A disconnected Calendly stops bookings, so visitors reach your calendar ending and can't pick a time. Reconnecting fixes a one-off drop. If it drops again the same day, that's a bug we've seen more than once and it needs us to look at your connection — don't rebuild the form.
Start with the plan check below, because a surprising number of these turn out to be Calendly's plan gate rather than a dropped connection.
The Calendly card in ROASForm is labeled Requires Paid Calendly Account, and that's a hard requirement from Calendly's side.
Requires Paid Calendly Account — Standard or above, on Calendly's side
Connect — reconnect from here, then re-select the event type on the form On Calendly's free plan a connection can look fine
and still fail the moment a visitor tries to book, because Calendly blocks third-party bookings there.
Your Calendly plan has to be Standard or above. You change that in Calendly, not in ROASForm.
You need at least one active event type. A paused or deleted event type has nothing to book.
In the sidebar, open Connect → Integrations.
On the Calendly card, connect again and complete Calendly's login.
Open the form, edit the calendar ending, and re-select the event type.
Book a test appointment on the published form, not the builder preview.
This is where it stops being a setup question. Don't rebuild the form or create a new one — send us these four things and we can trace the connection:
The subaccount name
The form name
When it last worked, and when it failed
A screenshot of the Calendly card showing it disconnected
We had several of these in September 2026, including accounts that couldn't take bookings at all. Repeated drops need an engineer on the connection itself.
Calendly says you've hit a rate limit. That limit is Calendly's and it applies to your Calendly account. Upgrading your ROASForm plan doesn't change it. If you have a webinar or a launch coming up, raise it with Calendly ahead of time.
Bookings work in preview but not on the live form. Test on the published URL. The preview doesn't create real appointments, so it isn't a valid check either way.
You'd rather not depend on Calendly. If you use GoHighLevel, you can book on its calendars directly. See GoHighLevel Calendar Integration.
