Widget v1.0.0
Create appointments from chats
Save this plugin to Following and return to review observed changes. Follow up to 10 plugins free.
From the marketplace listing
Turn ideas into calendar events in seconds. Just describe what you want, and this app creates a calendar event you can view and download. No complicated forms. No confusing menus. Simply type in plain language, check the event details, and save the result as a calendar file you can use almost anywhere. Whether you are planning a meeting, a birthday, a lesson, a holiday, an appointment, or a reminder, this app helps you make a clear calendar event quickly. It understands everyday language, so you can say things like “Lunch with Sam next Tuesday at 12”, “Team meeting every Monday at 9”, or “Dentist on 15 August at 2 pm”. The app turns your request into a ready-to-use calendar event. Each event is displayed in a simple, easy-to-read format before you download it. You can check the title, date, time, location, notes, and other important details to make sure everything looks right. If something needs changing, update your request and create a new version in seconds. When you are happy with your event, download it as an ICS calendar file. ICS is the standard calendar format used by many popular calendar apps and services. This makes it easy to import your event into your favourite calendar without having to type everything again. The app is useful for work, school, home, travel, and everyday life. Create meeting invites, class schedules, family events, sports practice, dinner plans, medical appointments, holiday reminders, project deadlines, study sessions, and much more. If it belongs on a calendar, this app can help you create it faster. Recurring events are also easy to make. Ask for something that repeats every day, every week, every month, or on another schedule, and the app creates a matching calendar event. This saves time when you have regular activities that you do not want to enter one by one. You can also include extra details to keep everything organised. Add locations, descriptions, notes, attendees, or other useful information to make your calendar events more complete. Having everything in one place makes it easier to remember what you need to do. Because you create events using natural language, there is less clicking and typing. Instead of filling in lots of boxes, simply explain your plans the way you would tell another person. The app does the hard work of turning your words into a structured calendar event. The downloaded ICS file works well for sharing too. Send it to friends, family, classmates, or colleagues so they can add the same event to their own calendar. This is a simple way to keep everyone on the same schedule. People use this app for many different tasks. Plan business meetings, organise school projects, schedule fitness sessions, remember birthdays, prepare for trips, create conference schedules, manage appointments, arrange social events, or build a complete timetable from simple text. The app focuses on speed and simplicity. You do not need special knowledge to use it. Just describe your event, review the result, and download it. It is designed for anyone who wants to spend less time managing calendars and more time getting things done. If you already use Google Calendar, Apple Calendar, Outlook, Microsoft 365, or another calendar that supports ICS files, importing your downloaded event is quick and easy. The standard format helps your events work across many different devices and calendar apps. Whether you need one event or many, this app makes calendar creation simple. Turn plain text into organised calendar events, review every detail before downloading, and save time with a fast, easy workflow. Create calendar events, generate ICS files, download calendar invites, and keep your schedule organised with the power of ChatGPT.
Language: English · Automatically detected from descriptions.
Oct 27, 2026 · 1 saved observations
Metadata · Oct 27, 2026 · 00:47 UTC · Compared with Oct 24, 2026 · 13:33 UTC
Package or technical metadata updated
Observed in package metadata. These changes alone do not establish a new customer-facing feature.
Oct 24, 2026 · 13:33 UTC
Not present
Oct 27, 2026 · 00:47 UTC
false
From the developer’s listing and package; capabilities are not independently tested. Package observed Nov 3, 2026.
Create appointments from chats
Specific limitations have not been established. Missing information does not mean unrestricted capabilities.
Pricing and account requirements have not been established from the available package declarations. Unknown pricing does not mean free access.
Burning Man
From the developer.
---
name: event-from-message
description: Extract one calendar event from pasted or visible message text and create an editable Event Creator card. Use when the user asks to turn an email, chat, invitation, announcement, or copied notice into one event. Require the source text to be available in the conversation; do not retrieve mail or create multiple events.
---
# Event From Message
Turn one message into one accurate, editable event.
## Inputs
Use message text that is visible in the conversation and any corrections or
preferences the user provides. Accept copied email, chat, invitation,
announcement, or notice text.
## Workflow
1. Identify the single event the user wants.
- If the message contains several distinct events and the user did not choose
one, ask which event to create.
- Ignore signatures, quoted reply history, tracking text, and unrelated
promotional copy.
2. Extract only supported event facts:
- a concise title;
- the start and end, or a start plus an explicit duration;
- an IANA time zone when the source or conversation establishes one;
- an optional description, location, and HTTP(S) event URL.
3. Separate source facts from assumptions.
- Resolve relative dates against the conversation date.
- Ask one concise clarification when ambiguity could change the scheduled
date, time, duration, timing mode, or time zone.
- Do not ask about missing optional details.
- Do not invent a location, URL, end time, or time zone.
4. Choose the timing mode.
- Use timed timing when a time of day is intended.
- Use all-day timing only when the message describes a date-based event with
no intended time of day. Treat its end date as inclusive.
- For a timed event, include an explicit IANA time zone when known. Otherwise
allow `display-event` to use its client time-zone hint; if the tool cannot
resolve one, ask the user for it and retry.
5. Invoke `display-event` once with the normalized event. Include optional
fields only when supported by the source or the user's instructions.
6. Present the resulting editable card. Briefly disclose any non-obvious
interpretation that remained necessary.
## Output
Deliver one editable Event Creator card whose title, timing, time zone, and
optional details match the source.
## Boundaries
- Do not retrieve email, messages, or attachments from another service.
- Do not create multiple events from one invocation.
- Do not add attendees, recurrence, reminders, or calendar-account writes.
- Do not claim the event was added to a calendar. The user exports it from the
widget.
Referenced files: 1 — file references are metadata, not package contents.
---
name: flyer-to-calendar-event
description: Extract one calendar event from a visible flyer, poster, screenshot, or photographed notice and create an editable Event Creator card. Use when the user asks to turn event artwork or an image-based announcement into an event. Require the image to be visible and readable; do not invent text, decode an unreadable QR destination, or create multiple events.
---
# Flyer To Calendar Event
Turn one visible event flyer into one accurate, editable event.
## Inputs
Use the attached or otherwise visible flyer, poster, screenshot, or photographed
notice together with any corrections the user provides.
## Workflow
1. Confirm that the image is available and readable enough to identify an
event. If it is missing or unreadable, ask the user to attach a clearer image
or paste the relevant text.
2. Identify the single event the user wants.
- If the image advertises several sessions, dates, or performances and the
user did not choose one, ask which one to create.
- Distinguish event facts from decorative, sponsor, and promotional text.
3. Extract only supported event facts:
- a concise title;
- start and end information or an explicit duration;
- an IANA time zone when the flyer or conversation establishes one;
- an optional venue or address, description, and clearly readable HTTP(S)
event URL.
4. Check visually ambiguous details before scheduling.
- Ask one concise clarification when a numeric date, missing year, time,
duration, timing mode, or time zone has more than one material
interpretation.
- Do not infer a URL from a QR code whose destination is not visibly decoded.
- Do not invent obscured or cropped text.
5. Choose the timing mode.
- Use timed timing when the flyer specifies or clearly intends a time of day.
- Use all-day timing only for a genuinely date-based event, not merely
because the time is unreadable. Treat its end date as inclusive.
- For a timed event, include an explicit IANA time zone when known. Otherwise
allow `display-event` to use its client time-zone hint; if the tool cannot
resolve one, ask the user for it and retry.
6. Invoke `display-event` once with the normalized event and only supported
optional details.
7. Present the resulting editable card. Briefly disclose any non-obvious
interpretation that remained necessary.
## Output
Deliver one editable Event Creator card based on the readable event facts in
the image.
## Boundaries
- Do not claim to use an OCR, QR-decoding, browsing, or image-retrieval service
that is not available in the conversation.
- Do not create multiple events from one invocation.
- Do not add attendees, recurrence, reminders, or calendar-account writes.
- Do not claim the event was added to a calendar. The user exports it from the
widget.
Referenced files: 1 — file references are metadata, not package contents.
---
name: meeting-notes-to-focus-block
description: Turn one action item from visible meeting notes into a scheduled, editable Event Creator focus block. Use when the user asks to reserve time for a follow-up, deliverable, or preparation task identified in notes. Require one concrete action and an exact schedulable slot; do not create tasks, reminders, attendees, recurrence, or multiple blocks.
---
# Meeting Notes To Focus Block
Turn one meeting follow-up into one focused calendar block.
## Inputs
Use meeting notes visible in the conversation plus the user's chosen action,
duration, scheduling window, and time-zone context.
## Workflow
1. Identify the single follow-up to schedule.
- Prefer the action the user names or an action clearly assigned to the user.
- If several plausible actions remain, ask which one to schedule.
- Do not schedule actions owned by someone else without the user's explicit
request.
2. Define a concrete outcome for the block.
- Write a short action-oriented title.
- Distill two to five useful steps, acceptance criteria, or preparation notes
into the description.
- Include a relevant HTTP(S) source or meeting URL only when it is present in
the notes or supplied by the user.
3. Resolve an exact timed schedule.
- Use the start and end the user provides, or calculate the end from an
explicit duration.
- If only a broad window such as "Tuesday afternoon" is given, ask for an
exact start time rather than choosing one silently.
- Include an explicit IANA time zone when known. Otherwise allow
`display-event` to use its client time-zone hint; if the tool cannot resolve
one, ask the user for it and retry.
- Confirm that the end is after the start and that the chosen time is not a
nonexistent DST wall time.
4. Invoke `display-event` once with timed timing and the focused title,
description, and any supported URL or location.
5. Present the resulting editable card. Keep the response centered on the
scheduled block rather than re-summarizing the entire meeting.
## Output
Deliver one editable Event Creator card for a concrete follow-up focus block,
with a concise outcome and actionable description.
## Boundaries
- Do not create a task-system entry or mark an action item complete.
- Do not create multiple focus blocks from one invocation.
- Do not add attendees, recurrence, reminders, or calendar-account writes.
- Do not claim the block was added to a calendar. The user exports it from the
widget.
Referenced files: 1 — file references are metadata, not package contents.
---
name: travel-reservation-event
description: Turn one visible flight, train, bus, ferry, hotel, or other travel reservation into an editable Event Creator card. Use when the user provides itinerary or booking details for one segment or stay. Normalize cross-zone timing into the app's single event time zone; do not retrieve bookings, check live status, expose unnecessary sensitive data, or batch-create an itinerary.
---
# Travel Reservation Event
Turn one supplied travel reservation into one accurate, editable event.
## Inputs
Use reservation or itinerary details visible in the conversation and any
preferences the user provides. Handle one transportation segment or one lodging
stay at a time.
## Workflow
1. Select the single reservation to create.
- If the source contains several segments or stays and the user did not
choose one, ask which one to use.
- Do not silently merge connections, return journeys, or separate bookings.
2. Extract the supported facts.
- Build a concise title that identifies the journey or stay.
- Capture the scheduled start, scheduled end or explicit duration, and the
relevant IANA zones.
- Use the departure, boarding, or check-in place as the event location unless
the user prefers another location.
- Put useful terminal, platform, destination, check-in, or checkout context
in the description.
- Include a valid HTTP(S) booking or information URL only when it is visible
in the source.
3. Protect sensitive information.
- Include a confirmation or booking reference only when the user asks for it
or clearly expects it in the calendar entry.
- Omit payment data, ticket barcodes, loyalty numbers, passport details, and
other unnecessary credentials.
4. Normalize timing into one event time zone.
- For transportation, normally use the departure location's IANA zone.
Interpret the departure in that zone, interpret the arrival in its local
destination zone, then convert the arrival instant into the chosen event
zone for `endLocal`.
- Preserve the original arrival local time and destination zone in the
description when that context helps the traveler.
- For lodging, use the property's IANA zone. Use timed timing when explicit
check-in and checkout times are intended; otherwise use inclusive all-day
dates.
- Resolve date-line crossings, overnight arrivals, and DST before invoking
the tool. Confirm that the end instant is after the start instant.
5. Ask one concise clarification when an ambiguous date, airport or station,
local time, time zone, or missing arrival date could change the event.
Do not ask about missing optional details.
6. Invoke `display-event` once with the normalized event.
7. Present the resulting editable card and briefly note any important zone
conversion used.
## Output
Deliver one editable Event Creator card for one travel segment or lodging stay,
with timing represented accurately in one IANA zone.
## Boundaries
- Do not retrieve reservations from email, airline, hotel, or booking services.
- Do not look up live delays, gates, platforms, cancellations, or check-in
status.
- Do not create several itinerary events in one invocation.
- Do not add attendees, recurrence, reminders, or calendar-account writes.
- Do not claim the reservation was changed or added to a calendar. The user
exports the event from the widget.
Referenced files: 1 — file references are metadata, not package contents.
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 3, 2026.
plugin_asdk_app_6a6a03d6ef6c819189d3c338a3e97e8c
Download plugin data (JSON)