# Create Event

**Introduction**

The "Create Event" step facilitates the creation of scheduled events within a Discord guild.&#x20;

**Configuration**

* **Guild**: Specify the guild in which the event will be created. This field is required.
* **Name**: Set the name of the event. The name must be between 1 and 100 characters long.
* **Description**: Provide a description for the event. This is optional and can be between 1 and 1000 characters. Empty values will be treated as null.
* **Type**: Choose the type of event. Options include voice, stage, and external. This selection dictates additional configuration requirements.
* **Location**: For external events, specify the location. This field is required for external events and can be up to 100 characters.
* **Voice Channel**: Select the voice channel for voice events. This field is shown and required if the event type is voice.
* **Stage Channel**: Select the stage channel for stage events. This field is shown and required if the event type is stage.
* **Starts At**: Set the start time for the event. This field is required.
* **Ends At**: For external events, set the end time. This field is shown and required for external events.

**Permissions**

* **Manage Events**: The bot must have this permission to create events in the guild.

**Outputs**

* **Event**: Outputs the created event object. This variable can be used in subsequent steps to reference the event, such as updating details or sending reminders.

**Usage**

This step is crucial for automations related to event management within Discord communities, such as automatically scheduling events based on certain triggers.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.flexy.bot/modules/discord/steps/create-event.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
