> For the complete documentation index, see [llms.txt](https://jared-gibb.gitbook.io/fullcalendar-plugin-suite/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jared-gibb.gitbook.io/fullcalendar-plugin-suite/elements/calendar/actions/advanced-use/create-single-event.md).

# Create Single Event

## Creating an event

### Notes:

* The use case for this would be a super duper smooth calendar experience. 
* When you make a change in the backend, the calendar will rerender. This is fine ina  lot of cases but can cause issue. If you find that to be the case use this action.

### How to use:

* The most common way to use this would be to load a static list of events to the calendar and then when you need to add an event

1. Create an event in the DB
2. Using the results of step 1, populate the fields of this workflow action and the event will appear on the calendar. Be sure to make changes to the event in the db when they are changed using the corresponding [Calendar Events](broken://pages/-Mds3rVQRwq-uy4el4iu)

![](/files/-Mds40pzY4G58_OIe5OF)

* You can choose to either use the defaults or fill out all available fields. 
* You ***MUST*** fill out the first 4 fields using the DB event info.