Glossary

Explore Meshline

Products Pricing Blog Support Log In

Start with your goals.

Book a call
Autonomous Operations

Embed the Scheduling Widget or Add the Meetings Module? Decide Before You Build

Booking time on a page you already publish outside HubSpot? See when the embed-code path fits and when the meetings module on a HubSpot page is the better choice.

A calendar icon beside a webpage icon.

You have a page where prospects should be able to book time with your team.

HubSpot gives you two ways to add scheduling, and they are not interchangeable.

You can paste the scheduling widget's embed code into an external page, or add the meetings module to a HubSpot-hosted page.

The right choice depends on where the page lives, what your subscription includes, and who on your team can even reach the embed code.

This article walks that decision in order, so you can rule out one path before you spend any build time on it.

First check: where does the page live?

The two options map directly onto two kinds of pages.

If your page is hosted outside HubSpot—on your WordPress site, a custom-built site, or any other content management system—the embed-code path is the one designed for it.

If the page is a HubSpot website page or landing page, the meetings module is the native option.

That sounds simple, but teams often have both.

A marketing site on WordPress plus HubSpot landing pages for campaigns is a common setup.

In that case you may end up maintaining both approaches, so it is worth understanding what each one involves before you start.

Second check: does your subscription and access cover the path?

HubSpot documents different requirements for each path, and a mismatch here can end the decision before it starts.

For the embed-code path, the scheduling widget is available across all products and plans, except where noted.

However, accessing the embed code requires Sales Access or Service Access permissions.

If the person building the page does not hold one of those permissions, they cannot copy the code themselves—they will need a colleague who can.

For the meetings module on a HubSpot-hosted page, a Marketing Hub or Content Hub subscription is required.

If your account does not include one of those subscriptions, the hosted-page path is not available to you, regardless of how convenient it would be.

So the practical order is: confirm where the page lives, then confirm your subscription and permissions.

If only one path survives those checks, your decision is made.

How the external embed path works

If you are embedding on an external page, the procedure documented by HubSpot is straightforward:

  • In your HubSpot account, navigate to Sales > Meetings Scheduler (via the More menu if your account shows one).
  • Hover over the meeting, click the Actions dropdown, and select Embed.
  • Click Copy code.
  • Paste the embed code into the code of your external page.

One caveat deserves special attention.

HubSpot notes that some rich text editors may modify the HTML comments used in the embed code, and that you may need to correct the content after pasting.

In practice, this means you should not assume the widget renders correctly just because the paste succeeded.

After inserting the code, load the page and confirm the scheduling widget actually appears and behaves as expected.

If it does not, check whether your editor altered the code.

This check matters most when non-developers publish pages through a visual editor.

How the HubSpot-hosted meetings module path works

On a HubSpot website page or landing page, you do not touch embed code at all.

The documented procedure is:

  • Navigate to Content > Website Pages or Content > Landing Pages, depending on the page type.
  • Open the page where you want scheduling to appear.
  • In the content editor, click + Add in the left sidebar.
  • Search for the meetings module and drag it into position on the page.
  • Click the module, then use the Select a meeting dropdown in the sidebar editor to choose a meeting link.
  • Click Publish.

The scheduling page for the selected meeting link then appears in the widget on the published page.

Because the module is native to the page editor, there is no embed code for a rich text editor to mangle—that class of problem simply does not apply here.

The tradeoff is the subscription requirement already mentioned, plus the fact that this path only works on pages HubSpot hosts.

You cannot drag the meetings module onto a WordPress page.

Third check: is the meeting link itself ready to book?

Whichever path you choose, the widget or module displays a scheduling page tied to a meeting link.

A meeting link that shows real availability and accepts online or automatic bookings requires a connected calendar, per HubSpot's meetings documentation.

Supported calendars are Google, Office 365, or Exchange.

Without a connected calendar, the scheduling page runs in offline mode: visitors can still request meetings, but those meetings are not automatically added to the calendar.

That may be acceptable for some workflows.

But if your goal is self-service booking that lands on the organizer's calendar without manual steps, the calendar connection is a prerequisite for both paths.

Check this before you publish either version of the page.

A beautifully embedded widget backed by an offline scheduling page will not deliver the booking experience you intended.

An illustrative example of the decision

Consider a team—call it illustrative, not a real customer—running a WordPress marketing site and HubSpot landing pages.

A revenue operations lead wants booking on both.

Here is how the checks play out:

  • Where does the page live? The WordPress blog is external; the campaign landing pages are HubSpot-hosted. Both paths will be needed.
  • Does the subscription cover the hosted path? The team checks and confirms a Content Hub subscription is in place, so the meetings module is available for landing pages.
  • Does the builder have access to the embed code? The marketing coordinator publishing the WordPress post does not hold Sales Access or Service Access permissions, so a sales operations colleague copies the embed code for her.
  • Does the editor preserve the code? After pasting into the WordPress editor, the coordinator loads the page and finds the widget renders correctly. Had it not, she would have checked whether the editor altered the HTML comments.
  • Is the meeting link ready? The team confirms a connected Office 365 calendar, so the scheduling page shows live availability rather than offline mode.

Each check had its own consequence.

A failed subscription check would have forced the embed path everywhere.

A failed permission check would have added a handoff step.

A failed editor check would have required correcting the pasted code.

Which path should you prefer when both are available?

When your page is HubSpot-hosted and your subscription includes Marketing Hub or Content Hub, the meetings module is usually the lower-maintenance choice.

There is no code to paste, no editor-compatibility question, and you select the meeting link inside the page editor.

When your page lives elsewhere, the embed code is the documented route, and the verification step after pasting becomes your main quality check.

When you maintain both kinds of pages, using the native module on HubSpot pages and the embed code on external pages keeps each surface on its documented path.

That is a suggestion based on how the two procedures differ, not a rule—your team's editing workflow and permission structure may make a different split more practical.

A short decision summary

  • External page? Use the embed code from Meetings Scheduler (Actions > Embed > Copy code), and verify the widget after pasting because some rich text editors may modify the HTML comments.
  • HubSpot-hosted page with Marketing Hub or Content Hub? Add the meetings module from the content editor sidebar, select a meeting link, and publish.
  • No Marketing Hub or Content Hub subscription? The hosted-module path is not available; the embed path remains, subject to its own noted exceptions.
  • No Sales Access or Service Access permissions? You cannot retrieve the embed code yourself; arrange access or a colleague's help.
  • No connected Google, Office 365, or Exchange calendar? The scheduling page will be in offline mode—meetings can be requested but are not automatically added to the calendar—on either path.

Running these checks in order takes the guesswork out of the choice.

It reduces the risk of building a page around a scheduling option your account or page surface cannot support.

For related decisions in your automation stack, these guides cover neighboring choices:

Source references: knowledge.hubspot.com; knowledge.hubspot.com.

How Meshline can help. Connect automation, Organic Marketing (demand generation), and customer lifecycle management (Revenue Intelligence).

Bring topic planning, content publishing and performance feedback into the conversation about your workflow. Book a Meshline demo.

Revenue Intel

Ask us about this workflow.

Tell us what you want to fix or automate. We'll reply with the most useful next step.

See how we can help

Implementation decisions

Put this into practice

Before choosing a solution, define the problem, the available data and who will review the outcome.