> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/dcal/events/create-an-event.md).

# Create an event

Create and edit a dCal booking link. Set its duration, hours and calendar text, add questions and reminders, preview your changes, then save.

Create an event to give people a link where they can book a meeting with you. Start with its title and timing, then add the questions and reminders you need.

This page creates a bookable event type. To put a meeting or a block of focus time directly on your calendar through an assistant, use [create\_event](https://docs.dapta.ai/dcal/developers/mcp-tools.md#create_event).

***

**Step 1:** Sign in at [app.dcal.ai](https://app.dcal.ai), open **Events** and click **New event**.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-6e6eb5aad53a684be75b2c1aa9648e8845b1082e%2Fdcal-create-an-event-01-new-event-button.png?alt=media" alt="The Events page with the New event button at the top right"><figcaption><p><strong>New event</strong> opens the editor.</p></figcaption></figure>

The editor has these tabs. Your changes stay in the draft when you switch tabs.

| Tab                | What you set                                                                                                          |
| ------------------ | --------------------------------------------------------------------------------------------------------------------- |
| **General**        | Title, event link, description, duration, location, calendar text, hours, hosts, booking options and advanced timing. |
| **Booking form**   | The questions your guests answer.                                                                                     |
| **Reminders**      | Reminder and follow-up emails, their timing and previews.                                                             |
| **CRM Connection** | Answer mapping and tracking tools, when available for your workspace and role.                                        |
| **AI Agents**      | The event ID after saving, an example request and the MCP address, with a link to connect an assistant.               |

***

**Step 2:** In **General**, enter a **Title**, such as `Intro call`. **Event link** fills in from the title, for example `intro-call`. It stops following the title once you edit it yourself. Use lowercase letters, numbers and hyphens, up to 80 characters; the link must be unique among your events. The title can have up to 200 characters.

Add a **Description** for your booking page if you need one, up to 2,000 characters. Choose **Duration**: **15 min**, **30 min**, **45 min**, **60 min**, or **Custom** for another whole number from 1 to 1,440 minutes. Guests do not choose the duration; create separate events to offer different lengths.

Pick a **Location**. For **In person**, **Phone call** or **Custom**, fill in the detail the editor asks for. Online meetings use the calendar that receives your bookings to create the meeting link. See [Length, location and timing](https://docs.dapta.ai/dcal/events/event-settings.md#location).

***

**Step 3:** Set **In the calendar** if you want the calendar invite and booking emails to identify the guest or their answers. Leave **Calendar event title** empty to keep the event title; leave **Calendar event description** empty for no description.

Click or drag a variable into the field, or type it as `{{attendee_name}}`. For example, `{{event_title}} with {{attendee_name}}` makes the meeting easy to recognize. Add questions in **Booking form** before using their answer variables, such as `{{form.company}}`. Each field shows an **Example** with sample values. See [Calendar event text](https://docs.dapta.ai/dcal/events/event-settings.md#calendar-event-text) for restrictions, including group events.

***

**Step 4:** Under **Bookable hours**, choose **My working hours**, **A saved schedule**, or **Custom hours for this event**. Custom hours belong only to this personal event: choose the days, start and end times, and time zone, and use **Add hours** for another range. They do not create a schedule on your **Availability** page. A team event uses each host's own working hours instead.

Choose **Minimum notice**: **1 hour**, **2 hours**, **6 hours**, **12 hours**, or **1 day** through **5 days**. A new event starts at **2 hours**. An existing value outside those choices stays available when you edit it.

For personal events, **Calendars for this event** chooses which calendars to **Check for conflicts** and which one to **Add events here**. To share bookings with a team, use the **Hosts** card's team-event shortcuts. See [Set your hours](https://docs.dapta.ai/dcal/calendars-and-availability/set-your-hours.md) and [Round-robin, collective and fixed hosts](https://docs.dapta.ai/dcal/teams/scheduling-methods.md).

***

**Step 5:** In **General**, review the booking options:

* **After booking** holds **Requires confirmation**, **One booking per person** and **Redirect after booking**. Requests wait for you to accept or decline. One booking per person counts upcoming bookings made through the public page; bookings you make yourself or with your API keys are not limited by it.
* **Visibility and sharing** holds **Hidden** and **One-off invite links**. A hidden event is absent from your profile and its normal link shows **Page not found**; only a one-off invite link can book it. Save a new event before making those links.
* **Advanced settings** holds buffers, group seats, the slot interval and the booking window. The interval follows the duration while the two match; once you choose a different interval it stays independent. See [Length, location and timing](https://docs.dapta.ai/dcal/events/event-settings.md).

***

**Step 6:** Open the other tabs as needed:

* In **Booking form**, add your questions. Name, email and notes are built in. See [Booking questions](https://docs.dapta.ai/dcal/events/booking-questions.md).
* In **Reminders**, set reminders before the meeting and a follow-up after it. A new event starts with reminders 24 hours and 1 hour before, and its follow-up off. Use **Preview email** to check the sample guest email without sending it. See [Reminders and follow-ups](https://docs.dapta.ai/dcal/emails/reminders-and-follow-ups.md).
* In **CRM Connection**, map answers to HubSpot and set tracking IDs if your role and workspace offer them. See [HubSpot](https://docs.dapta.ai/dcal/integrations/hubspot.md) and [Tracking and pixels](https://docs.dapta.ai/dcal/events/event-settings.md#tracking-and-pixels).
* In **AI Agents**, copy an example request or open the connection guide. The event ID appears after the first save. See [Connect an AI assistant](https://docs.dapta.ai/dcal/developers/mcp-server.md).

***

**Step 7:** Click the eye button, **Preview booking page**, in the header. It opens your unsaved title, description, duration, location and questions at `https://app.dcal.ai/preview/event` in a new tab.

For a new event or a team event, the times are examples. For an existing personal event, they are your real availability as last saved, so unsaved changes to hours or timing do not change those times. You can pick a time and try the form, but the preview holds no time and creates no booking. Close it and reopen it from the editor after making further changes.

***

**Step 8:** Click **Create event** in the header. If a field needs attention, the editor opens its tab and focuses the first error. A summary at the top links to the fields to fix, and tabs show error counts. Fix the fields and save again.

dCal shows **Saved successfully.** and returns to the Events list. Unless the event is hidden, people can book it immediately. Use **Copy link** on its row to share it.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-c0f8b1b6a87bafdad0dc10fecf40425124711a3c%2Fdcal-create-an-event-08-saved.png?alt=media" alt="The Events list with the new event and a Saved successfully message"><figcaption><p>Your new event is ready to share.</p></figcaption></figure>

***

## Edit an event

Click **Edit** on the event's row. The form opens with the event title as its heading and a **Save changes** button. The header also carries the **Open booking page**, **Copy link** and **Embed on your site** icons. Make your changes and click **Save changes**: dCal shows **Saved successfully.** and keeps you on the page.

Changes apply to bookings made from then on. Bookings already made keep their time and location.

***

## Hide or show an event

You can hide an event in two ways:

* Flip the switch on its row in the Events list. This saves at once.
* Tick **Hidden** in **General** > **Visibility and sharing** and click **Save changes**.

While an event is hidden:

* It is not listed on your profile page.
* Its own link, and any embed of it, show **Page not found**.
* You cannot pick it when you create a booking yourself in **Bookings**.
* Only [one-off invite links](https://docs.dapta.ai/dcal/events/one-off-links.md) can book it.

> **⚠️ Note:** If you hide or delete your only visible event, dCal shows the **Create your first event** screen the next time you open the dashboard. Pick a starting point to create one, or click **Skip for now** to continue without it.

***

## Change the slug

Edit **Event link** in **General** and click **Save changes**. The new link works at once.

The old link stops working right away: it shows **Page not found** and does not forward people to the new address. Before you change the slug of an event you already shared:

1. Note every place the link lives: emails and templates, your email signature, social profiles, website buttons, QR codes, and messages your Dapta agents send.
2. Change the slug and save.
3. Copy the new link with **Copy link** and update each of those places.
4. If the event is embedded on a website, open **Embed on your site** again and replace the old code: the embed code contains the slug.

Your profile page link, `book.dcal.ai/{account code}/{handle}`, does not change.

***

## Delete an event

On the Events list, click **Delete** on the event's row. The button turns into **Delete** and **Cancel**: click **Delete** again to confirm. dCal removes the event and shows **Event deleted.** There is no undo.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-f0b1c75242e1eaf64ef0d45c59662338ba784073%2Fdcal-create-an-event-10-delete-confirm.png?alt=media" alt="The row of an event named Test event where the Delete button has turned into Delete and Cancel buttons"><figcaption><p>The second click on <strong>Delete</strong> confirms.</p></figcaption></figure>

What deleting does:

* The event's link and its one-off invite links show **Page not found**.
* Bookings already made on the event are **not** cancelled. If those meetings should not happen, cancel them from **Bookings** before you delete the event. See [Reschedule and cancel](https://docs.dapta.ai/dcal/bookings/reschedule-and-cancel.md).

Team events cannot be deleted from the Events page. To stop offering one, switch it off.

## Related

* [Length, location and timing](https://docs.dapta.ai/dcal/events/event-settings.md): every timing field in detail, with a reference table.
* [Booking questions](https://docs.dapta.ai/dcal/events/booking-questions.md): ask guests your own questions.
* [Events (booking links)](https://docs.dapta.ai/dcal/events.md): the Events page and its quick actions.
* [Embed on your website](https://docs.dapta.ai/dcal/share/embed.md): put an event on your site.
* [See your bookings](https://docs.dapta.ai/dcal/bookings/see-your-bookings.md): where new bookings show up.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dapta.ai/dcal/events/create-an-event.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
