Can I schedule a meeting on a record without adding the contact as a guest? (Attendees can't be left

Smart CRM & Sales Hub
,
1

■ Workarounds we’ve already checked

The closest existing discussion is “Can I create a meeting without inviting the contact?” (2019):

Both suggestions there fail for our use case:

  • “Create the event in Google Calendar with the contact as an attendee, but don’t send the email invitation.”
    Suppressing the email doesn’t remove the contact from the guest list, and guests can open the event details — so the description is still exposed. The customer also sees the event if they ever do open a calendar. This is the one thing we need to prevent.

  • “Just log the meeting in the CRM.”
    A logged meeting creates no calendar event at all, so there’s nothing for our team to read in Google Calendar or the Meet side panel, and it only happens after the call.

That thread is seven years old and has no response from HubSpot, so I’d like to check whether the situation has changed.

■ Questions

  1. Is there any supported way to create a meeting associated with a record without adding the contact as a guest (i.e. without sending an invite)?
  2. If not, is the “at least one contact attendee” requirement intentional, or just how it currently works?
2

Great question. Has HubSpot introduced a way to associate a meeting with a contact record without adding the contact as a guest or exposing the calendar event details?

It would also be helpful to know whether the attendee requirement is intentional or a current limitation.

3

Hi @Hiroki_Igeta

Could you please elaborate on the main requirement? A more detailed explanation of the use case, expected outcome, and any specific challenges you’re facing will help us research the issue more effectively and provide the most suitable solution.

Thanks!

4

Hi @Hiroki_Igeta ,
I think you’ve already tested the two obvious workarounds, and the key issue here is that HubSpot treats the calendar event and the CRM meeting activity a little differently.

For the exact scenario you’re describing — having a meeting appear on your team’s Google/Outlook calendar, associating it with the CRM record, but not making the customer a calendar guest — I don’t believe there’s currently a native HubSpot scheduling option that does all three.

The “don’t send the invitation” approach doesn’t really solve it because the contact is still an attendee/guest. They can still potentially see the calendar event and its details. And simply logging the meeting in HubSpot goes in the other direction: it gives you the CRM activity, but it doesn’t create the calendar event your team needs.

One thing I would check, though, is whether you’re actually trying to schedule a synced calendar meeting or just create a meeting activity associated with the record. Those behave differently.

If you need the calendar event to exist before the meeting and be visible to your internal team, while keeping the external contact completely out of the guest list, the practical workaround is usually to separate the two actions:

  • Create an internal-only event in Google/Outlook with only your internal attendees.
  • Separately create/associate the meeting activity with the relevant HubSpot contact, company, or deal.
  • If this needs to happen automatically, an integration/workflow can potentially handle the two pieces separately.

The Meetings API is another option if you’re comfortable with some automation. It can create a meeting record and associate it with CRM records, but I wouldn’t treat that as a direct replacement for the synced calendar meeting — you’d still need to handle the calendar event separately.

So, based on the current behavior, I’d say the limitation is less about whether HubSpot can have a meeting associated with a record and more about the requirement that a calendar-synced meeting has a contact attendee.

If your exact requirement is “associate with the CRM record, create an internal calendar event, but never expose the event to the customer”, I’d separate the CRM activity from the calendar event rather than trying to suppress the invitation after adding the contact.