Skip to main content

I am struggling to come up with a solution on this.

I created a booking page where a customer can choose topics they need help with, each topic has a set duration, so my first issues is I need to dynamically set the event duration. The second issue I have is I have a system knowing which agents are skilled on each topic, so some of the choices may require multiple agents to attend the meeting.

I can accomplish both of these issues by creating One-Off Event Types using the API and can do collective events when multiple agents are needed, which is great.

The issue I have now is I need to be able to set buffers on these event types, or my agents are going to be bombarded with bookings with no breaks potentially.

I really don’t like butting 2 events together as a lot of our sessions do take longer than expected as these are onboarding/support sessions, and we can run into issues if a customer only books a 15 minute topic, and we run into an unexpected issue, which does happen frequently.

I also don’t just want to add extra time to the duration as the customer may expect to get that extra time.

The only way I can do this without the api is create multiple event types, each with a 15, 30, 45, 60 minute duration, but then I have to create 4 types for each individual agent one for each duration, and then 8 more for each variation of multiple agents. In all I would have to build out and maintain over 60 event types, which is just going to be a nightmare to maintain with new agents coming on and turnover and whatnot.

Hoping I am just missing something with the API call and can just add buffers somehow when creating an event type via the api

Would love to add buffers via API. Would be a huge help to our workflow.

  1. We actually need to create event types with custom names like “Mike’s Review”.
  2. We can copy an existing event type and rename, but we cannot keep nor add back in the buffers.

 


Thank you both for taking the time to share your detailed use cases—these are incredibly thoughtful and clearly reflect the real-world complexity you’re navigating. I truly understand how important it is to have flexibility around event duration and agent availability, especially when dealing with onboarding and support sessions that often run over time.

At the moment, buffers cannot be set or retained via the Calendly API when creating or copying event types. I completely recognize how limiting this can be, especially in workflows like yours where time management and agent scheduling are critical. You're definitely not missing anything—this is currently a known gap in our API functionality.

 

That said, your feedback is incredibly valuable and aligns closely with what we’re hearing from other developers. I’ve logged this internally as a feature request for our Product team, and I’ll continue to advocate for more robust API support around buffers and flexible event creation.

 

In the meantime, I know workarounds like managing 60+ event types aren’t sustainable, and I sincerely wish I had a more seamless solution to offer today. If anything changes, or if this functionality becomes available, I’ll make sure to update the community.

Thanks again for sharing so openly. Please keep the ideas and feedback coming—we’re always listening and deeply appreciate the insight you bring from your real use cases.


Reply