Skip to main content
The Create Schedule atom provides a simple dialog interface for users to create new availability schedules. Fully customizable with callback support for handling successful schedule creation. Below code snippet can be used to render the Create schedule atom
For a demonstration of the Create schedule atom, please refer to the video below.

For developers who don’t want the dialog-based interface, we provide a CreateScheduleForm atom to integrate the schedule creation form directly into your own UI. This headless approach gives you full flexibility to handle layout, styling, and user flow exactly how you need it. Below code snippet can be used to render the Create schedule form atom
For a demonstration of the Create schedule form, please refer to the video below.

We offer all kinds of customizations to the Create schedule atom via props. Below is a list of props that can be passed to the atom.

Along with the props, create schedule atom accepts custom styles via the customClassNames prop. Below is a list of props that fall under this customClassNames prop.

Similar to the create schedule atom, the create schedule form also offer all kinds of customizations via props. Below is a list of props that can be passed to the atom.

| customClassNames | No | To pass in custom classnames from outside for styling the atom | | onSuccess | No | Callback function that handles successful creation of schedule | | onError | No | Callback function to handles errors at the time of schedule creation | | disableToasts | No | Boolean value that determines whether the toasts are displayed or not | Along with the props, create schedule form also accepts custom styles via the customClassNames prop. Below is a list of props that fall under this customClassNames prop.
Please ensure all custom classnames are valid Tailwind CSS classnames. Note that sometimes the custom classnames may fail to override the styling with the classnames that you might have passed via props. That is because the clsx utility function that we use to override classnames inside our components has some limitations. A simple get around to solve this issue is to just prefix your classnames with ! property just before passing in any classname.