Skybee Booking for Calendly - Booking Block, Popup & Elementor Widget

No. Calendly's embed code works in a Custom HTML block. This plugin is for when you want to see the calendar while you edit, change options without code, let Authors and Contributors add booking pages, open popups by themselves, or track bookings. See "Calendly's embed code or this plugin?" above.

No. Skybee Booking for Calendly is an independent plugin by Hendra Setiawan and is not made by, affiliated with or endorsed by Calendly. "Calendly" is a trademark of Calendly LLC.

No. The plugin works with the public link of your booking page, the same one you would share by email. Nothing has to be connected or synced.

Yes. Booking pages are set up at calendly.com; a free Calendly account is enough.

No. The block and the widget work as soon as you paste a Calendly link. The Get started page under the Calendly menu is a shortcut: save your link there once and every new block and widget starts with it, and a shortcode without a link uses it. Each block or widget can still use a different link.

An event link (https://calendly.com/your-name/30min) shows that event's calendar. Your profile link (https://calendly.com/your-name) shows all your events and lets the visitor pick one. In Calendly, open the event and choose Share → Copy link. If you paste Calendly's embed code instead, the plugin picks the link out of it.

Yes. Each block, widget or shortcode has its own Calendly link, so one page can show your 30-minute call and another your workshop. To let visitors choose from all your events, paste your profile link instead.

If a visitor is logged in to your site, the plugin passes their name and email to Calendly, so the booking form is already filled in. It's on by default. Switch it off for one booking page in its options, or for new booking pages under Calendly → Settings. Visitors who aren't logged in see Calendly's normal form.

Yes, on WordPress.com plans that can install plugins. Since April 2026 that's every paid plan, once the plan's hosting features are activated (installing a plugin does that). On the free plan you can't install plugins or keep Calendly's embed code, so link to your Calendly page or add a button that opens it.

You can set a background, text and button colour in the block, widget or shortcode. Calendly applies them on its paid plans. On a free Calendly plan the booking page keeps Calendly's own colours. That is a Calendly rule, not something the plugin can change.

Not unless you switch that line on in the button's options. Calendly's branding inside the booking page itself depends on your Calendly plan.

In the block sidebar, pick Button that opens a popup. Your page shows a button that opens the calendar over the page. Pick Floating button for a button that stays in the bottom corner of the page while the visitor scrolls. With the shortcode, use mode="popup" or mode="floating".

Yes. Under Open by itself, choose after a delay, when the visitor is about to leave (exit intent, desktop only) or after scrolling part of the page. You can open it only once per visitor, not again after the visitor booked, and hide the button so the calendar only opens by itself. With the shortcode: [calendly_booking url="..." mode="popup" open_trigger="exit" show_once="1" hide_button="1"].

Calendly loads inside the booking page and sets its own cookies, as it does on calendly.com. If you want nothing requested from Calendly until the visitor agrees, turn on Load the booking page on click under Calendly → Advanced: the calendar then shows a short message and a button first. You can also hide Calendly's cookie banner from the block, and cover Calendly in your own cookie notice instead. The External services section above lists what is sent where.

In Elementor, add the Calendly Booking widget. It has the same options as the block and a Style tab for the buttons. In Divi, Bricks and other builders, put [calendly_booking url="..."] in the builder's shortcode, text or HTML element. Calendly → Shortcode builds the shortcode for you. The same shortcode works in the classic editor and in widgets.

The plugin never replaces another plugin's shortcode. If the name is already taken on your site, Calendly → Settings says so, and you can use the block or the Elementor widget instead.

You don't need to learn them: Calendly → Shortcode writes the shortcode from the options you choose. For reference: url (required), mode (inline, popup, floating), hide_profile, hide_details, hide_cookie_banner, prefill (1 or 0), width and min_height (px), box_align (left, center, right), button_text, button_style (inherit or basic), badge_color, badge_text_color, badge_branding (floating button), background_color, text_color, primary_color (hex colours), open_trigger (click, delay, exit, scroll), open_delay (seconds), open_scroll (percent of the page), show_once, hide_after_booking, hide_button (automatic opening only), title (accessible name of the booking page).

In your Calendly account, as always. The plugin shows your booking page; everything visitors book is stored by Calendly. If you would like to see bookings inside WordPress, click Request this feature under Calendly → Bookings, or say so in the support forum. Those requests decide what gets built next.

Yes. Turn on Track bookings under Calendly → Advanced. When a visitor completes a booking, a calendly_booking event is sent to the tags already on your site. In Google Tag Manager, use a Custom Event trigger for calendly_booking. Sites that use Google Analytics without Tag Manager receive the same event name. Meta Pixel receives CalendlyBooking as a custom event. The plugin adds no tags of its own, so your site needs one of these installed.

Yes. Enter the page's address under Thank-you page on Calendly → Advanced. After a completed booking the visitor is sent there.

Calendly already picks up utm_source and the other campaign tags from the page the booking page is on. To keep them when the visitor lands on one page and books on another, turn on Remember campaign tags under Calendly → Advanced. The values are kept in the visitor's browser until the tab closes, so check whether your cookie notice should mention it.

Yes, once you turn it on. It is off by default: go to Calendly → Advanced and turn on Let AI assistants use Skybee Booking for Calendly. On WordPress 6.9 or newer, the plugin then registers three WordPress Abilities that assistants connected to your site (for example through WordPress's MCP adapter) can use: get the embed code for a booking page, add a booking page to a post or page, and list the posts that contain one. They follow WordPress permissions: only users who can edit a post can add a booking page to it. Adding a booking page never changes existing content, and it is saved as a normal revision. If Elementor is active: recent Elementor versions switch the site's MCP server off until you turn MCP on under Elementor → Elementor MCP. Turn it on there if your assistant can't find the abilities.

1. Open your Calendly link in a private browser window. If Calendly says the page isn't available, the event is turned off or the link is wrong.
2. If a caching or speed plugin delays or combines JavaScript, exclude Calendly's script (assets.calendly.com) from it.
3. If a cookie consent tool blocks third-party content, the booking page may stay empty until the visitor accepts.
4. If Load the booking page on click is on, the calendar shows a short message and a button first. That's expected.

No. Calendly's script is only loaded on pages where a booking page is actually shown. If you turn on Remember campaign tags, a few lines of inline JavaScript are added to every page so the tags are kept from the page the visitor lands on; no extra file is loaded.

The block editor script in build/ is compiled from the files in src/, which are included in the plugin. To rebuild it, run npm install and then npm run build in the plugin folder. The build uses @wordpress/scripts, as listed in package.json.