Qualified sales demos
Ask about company size and use case first and only offer the Meet step to visitors who fit. Follow it with a HubSpot or Salesforce step so the lead and the meeting link reach the CRM together.
The Google Meet step offers the visitor the times you are genuinely free, books the one they pick on your Google Calendar with a Meet link attached, and saves that link so the bot can share it straight away.
Build on the Free plan. The Google Meet step runs on Pro ($39/month) and above.
Most video calls that start on a website still go through three tools: a form, a scheduling link and a separate email with the meeting URL. The Google Meet step does all of it inside the conversation. The visitor answers a few questions, sees the slots you have free, taps one, and gets a confirmed meeting with a Meet link before the chat ends.
It works the same way as the Google Calendar booking step, with one difference: every event it creates carries a Google Meet conference. Use the Calendar step when a booking happens in person or over the phone, and the Meet step when the appointment is a video call, such as a sales demo, a consultation or an onboarding session.
Slots are built from the weekly hours you set in the step. Busy times on the calendar you choose are read through Google's free/busy lookup and any slot that overlaps them is dropped, so a time that filled up an hour ago is not offered again.
When the visitor picks a time, the step creates the event on your calendar and asks Google to attach a Google Meet conference to it. The Meet link, the meeting code and the event link come back to the flow.
With attendee email collection on, which is the default, the visitor's email is added to the event as a guest and Google sends them the invitation, so the call lands in their own calendar with the link inside it.
The result is saved to a variable as a readable line, for example 2026-11-12 at 3:00 PM (30 min) - https://meet.google.com/.... Put it in the confirmation message, a CRM step or an email.
Each weekday can be on or off with its own time windows, including more than one window in a day. If you set no hours at all, the step falls back to Monday to Friday, 9:00 to 17:00.
Meetings can last from 15 minutes to 2 hours, with a buffer of up to 30 minutes between them, bookable from 1 to 365 days ahead.
| Setting | What it does |
|---|---|
| Google account | The connected account whose calendar the meeting is booked on. |
| Calendar | The calendar busy times are read from and the meeting is added to. |
| Meeting title and description | What the event is called. Variables are allowed, such as Demo with ${name}. |
| Duration | 15, 30 or 45 minutes, or 1, 1.5 or 2 hours. |
| Buffer time | No buffer, or 5, 10, 15 or 30 minutes between meetings. |
| Days in advance | How far ahead visitors can book, from 1 to 365 days. The default is 14. |
| Time zone | The zone your hours are in and the event is created in. Without one the step uses UTC. |
| Weekly availability | On or off per weekday, with one or more time windows. |
| Collect attendee email | On by default. Adds the visitor as a guest so Google emails them the invitation. |
| Save result | The variable that receives the date, time, duration and Meet link. |
About ten minutes, most of it spent on your hours. You need a Pro or higher workspace and the Google account whose calendar holds your meetings.
Before the Meet step, ask for the name, email and the reason for the call, each saved to a variable. A booking template already has these questions.
Drag the step into the flow where the visitor is ready to book.
Choose Connect and approve calendar access in Google's window. The Meet step books through Google Calendar, so calendar permission is what it asks for. If the account is already connected it appears in the list.
Select the calendar that holds your meetings and set the time zone your working hours are in. Without a time zone the step uses UTC, which is rarely what you want.
A typical demo is 30 minutes with a 10-minute buffer and two weeks of availability. Keep the window short if your diary changes often.
Turn on the days you take calls and set the hours for each. Name the event with a variable, such as Intro call with ${name}, so it is clear in your calendar.
Name the result variable, for example meet_data, and reply with it after the step: "You're booked: ${meet_data}". Then preview the bot, book a slot with your own email and check the event, the Meet link and the invitation.
Ask about company size and use case first and only offer the Meet step to visitors who fit. Follow it with a HubSpot or Salesforce step so the lead and the meeting link reach the CRM together.
Coaches, consultants and agencies can run intake questions and book the first call in one go. Add a Stripe step before the Meet step if the session is paid up front.
When a support conversation needs a screen share, offer a short Meet slot instead of a long back-and-forth. The agent sees the booking on their calendar with the visitor's question in the description.
Google already sends the invitation. To add context, such as an agenda or what to prepare, send it from a Gmail step that includes the saved meeting line.
The Meet step creates its meetings as Google Calendar events with a Meet conference attached, so it asks for calendar access: reading busy times, listing your calendars and adding events. Your email address and basic profile label the account in the dashboard.
Meetings are created on the calendar you pick, as the connected account, and the Meet link belongs to that account. For a team, connect each person's Google account and use one step per person, or route visitors to the right step first.
Remove the account on the Integrations page, or revoke Conferbot in your Google Account under third-party connections. Steps that used it stop offering slots until you reconnect.
Choosing a slot is an interactive step, so it runs where the visitor can tap a time, such as the website widget. On messaging channels that only carry text the Meet step is not run; collect the request there and confirm the call another way.
The step checks the calendar you select. If your commitments live on another calendar, book on that one or share it into the one you use.
When the free/busy lookup fails, the step still offers slots from your weekly hours so the visitor is not stuck. If creating the meeting fails, the chat carries on and the result variable stays empty, so add a fallback message that tells the visitor you will email them.
Google attaches the Meet conference when the account can create Meet calls. Personal Google accounts and Google Workspace accounts with Meet turned on can; a Workspace admin can switch Meet off for a domain, and then the event is created without a link.
| What you see | Why, and the fix |
|---|---|
| No slots are offered | No weekday is on, today's windows have passed, or the calendar is full for the whole Days in advance range. Widen the hours or the range and check the time zone. |
| The booking has no Meet link | Meet is turned off for the Google Workspace account, or the account cannot create Meet calls. Check Meet settings in the Google Admin console, then reconnect. |
| Times are shifted by a few hours | The step has no time zone, so it used UTC, or the zone does not match where your hours apply. Set your business time zone in the step. |
| The visitor got no invitation | Attendee email collection was off or no valid email was captured before the step. Ask for the email first and keep collection on. |
| The step shows "Google access expired" | The connection lost its token, for example after a password change. Reconnect the account from the step or the Integrations page. |
| Nothing happens on WhatsApp | Slot picking only runs on interactive surfaces such as the website widget. Offer a contact request on text-only channels instead. |
Yes. When the visitor picks a slot, the step creates a Google Calendar event and asks Google to attach a Meet conference. The Meet link, meeting code and event link are returned to the flow.
Both offer real open slots and book them on your calendar. The Google Meet step also attaches a Meet video conference to every booking and saves the link, so use it when the appointment is a video call.
Yes, when attendee email collection is on, which is the default. The visitor is added as a guest and Google emails the invitation with the Meet link.
Yes. It builds slots from the weekly hours set in the step and removes any slot that overlaps a busy time on the selected calendar, using Google's free/busy lookup.
15, 30 or 45 minutes, or 1, 1.5 or 2 hours, with an optional buffer of 5 to 30 minutes between meetings and a booking window of 1 to 365 days.
Yes. Name a result variable in the step and use it in the next message. It holds the date, time, duration and Meet link as one line.
Picking a slot needs a screen where the visitor can tap a time, such as the website widget. On text-only channels the Meet step is not run.
Google Meet is a native integration, included on Pro and above. You can build and preview the flow on any plan.
Each Meet step books on one connected account's calendar. Connect each person's Google account and route visitors to the right step, or use a shared calendar the team watches.
Start free with Conferbot - the free plan includes 600 conversations a month and needs no credit card, so you can build the booking flow today. The Google Meet step switches on with Pro.
Checked against Conferbot's product and Google Meet's documentation on November 3, 2026: Google Calendar API: adding video conferencing to events, Google Calendar API: free/busy, Google Workspace Admin: turning Meet on or off.
Explore features, connect third-party tools, and browse ready-made templates.
Deep-dive pillar guides, real use cases, and the chatbot & AI glossary.
Guides on booking calls and handing off to a person.