Create calendar event
well_create_calendar_eventCreate an event on one of the user's own Google calendars.
Use this tool when the user asks to schedule, book, add or set up a meeting or an event. When the user names no calendar, use calendar_id "primary" and do not look calendars up. Call well_list_calendars first only when the user names a calendar other than their main one, and well_list_calendar_events first when the user may already have the event.
REQUIRED: calendar_id (a calendar id from well_list_calendars, or "primary" for the user's main calendar; never guess a default), title, start_at, end_at, notify_attendees. OPTIONAL: timezone (send it on every create), is_all_day, description, location, attendees (email addresses), recurrence (RRULE lines), visibility, task_id.
task_id: the job this event is the slot for. When the event books a job (a visit, an intervention, a delivery), create or find the task first and send its id here: the member's day then lists that job at this time, and a later move of the event moves the slot with it. The time lives on the event only, so never also write it into the task. Leave task_id out for a plain meeting.
notify_attendees: the guests of a new event get the invitation, so send true. Send false only when the user's own words say the guests are not told ("don't send the invite", "just block the slot"). Do not ask about it before the call. person_order: set it only when the user's own latest message orders this event whole (the guest, the day and the time). Put in its guests the address of each guest the message names: an address it types, a person it names, or the one contact of the client it names. List in its doubts anything the message leaves open. Times: start_at and end_at are timestamps with an offset, such as 2026-10-12T10:00:00+02:00. Send timezone, the IANA name of the zone those times are in (such as Europe/Paris), on every create. For an all-day event send dates (2026-10-12) and set is_all_day to true; end_at is the day AFTER the last day. Sending the same create again within ten minutes returns the event it already made instead of a second one; to book a second identical meeting, change something in it, such as the title. Only the user's own calendars can be changed. If the user has not granted calendar access, the call fails with calendar_scope_not_granted and a link: give that link to the user as it is.
Returns { success: true, event_id, title, start_at, end_at } on success, or { success: false, error } on failure.
Write to the user own Google calendar. Compute no UTC offset yourself. The turn states the user time zone: read a time the user gives in that zone, and pass it to well_convert_time (from_timezone and to_timezone both that zone) to get the local_time with its offset. On an update, never look an event up only to read its zone.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes | ||
| end_at | Yes | ||
| task_id | No | The job this event is the slot for, from a task read or a task you just created. The event then carries the job, so the member's day lists the job with this time and a later move of the event moves the job's slot with it. | |
| location | No | ||
| start_at | Yes | ||
| timezone | No | ||
| attendees | No | ||
| is_all_day | No | ||
| recurrence | No | ||
| visibility | No | ||
| calendar_id | Yes | ||
| description | No | ||
| workspace_id | No | Target workspace. Omit when the token authorizes one workspace. Required when it authorizes several — a write lands in exactly one workspace and this call would not say which. | |
| conversation_id | No | The conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation. | |
| idempotency_key | No | Optional client-supplied key. A retried write with the same key returns the original result instead of re-applying the operation. | |
| workspace_scope | No | Restrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace. | |
| notify_attendees | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| code | No | ||
| error | No | ||
| title | No | ||
| end_at | No | ||
| success | Yes | ||
| event_id | No | ||
| start_at | No | ||
| html_link | No | ||
| calendar_id | No | ||
| reply_lines | No | ||
| conversation_id | No | The conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation. | |
| near_candidates | No | ||
| newly_connected | No | Tools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later. | |
| conversation_id_note | No | Present only when the server opened a fresh lane, stating that no choice recorded earlier was read. | |
| conversation_id_source | No | Where the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened. | |
| near_candidates_truncated | No |